ERROR 2: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
0 Error occurred on in function preg_replace
1 called from line 1483 of file functions_print.php in function print_text
2 called from line 159 of file login.php
Warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home/oswale7reunion/oswaldreunion/family/includes/functions/functions_print.php on line 1483
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You need to upgrade PhpGedView to the version available as an SVN snapshot. This is currently version 4.3.1, but is not yet available as an "official" donwload. That will happen sometime in the new year, as I find time to build the release files.
At the top of this page, click on "SVN" and follow the links. You want the "trunk" branch.
There are lots of posts in the Help forum that deal with the upgrade procedure.
On the other hand, if you're just starting out (a new PhpGedView installation), you might be better served if you use Webtrees instead of PhpGedView. Webtrees was created from PhpGedView over 10 years ago, when almost all of the original developers left the project. Webtrees has better support. I have stuck around because PhpGedView does exactly what I want it to do, and I see no reason to switch.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
From: Gerry Kroll [mailto:canajun2eh@users.sourceforge.net]
Sent: Friday, December 27, 2019 6:36 PM
To: [phpgedview:discussion]
Subject: [phpgedview:discussion] error message when I log in
You need to upgrade PhpGedView to the version available as an SVN snapshot.
This is currently version 4.3.1, but is not yet available as an "official"
donwload. That will happen sometime in the new year, as I find time to build
the release files.
At the top of this page, click on "SVN" and follow the links. You want the
"trunk" branch.
There are lots of posts in the Help forum that deal with the upgrade
procedure.
On the other hand, if you're just starting out (a new PhpGedView
installation), you might be better served if you use Webtrees instead of
PhpGedView. Webtrees was created from PhpGedView over 10 years ago, when
almost all of the original developers left the project. Webtrees has better
support. I have stuck around because PhpGedView does exactly what I want it
to do, and I see no reason to switch.
If you already have a lot of work and time invested in PhpGedView, you are obviously NOT a new user, just starting out. Therefore, switching to Webtrees in favour of PhpGedView is not a good option.
As already stated, you need to upgrade your PhpGedView installation to the latest-and-greatest version 4.3.1, available as an SVN snapshot. This is because older versions are not compatible with the current version of PHP. Version 4.3.1 of PhpGedView has been run successfully on all PHP versions from 5.3 right up to 7.3. It should be OK with PHP 7.4 as well, but I don't know of anyone who has tried that. If PhpGedView 4.3.1 has problems with PHP 7.4, those errors can be fixed as long as I'm told about them.
Upgrading PhpGedView is as simple as replacing all of the program code, but retaining the config.php file as well as the index and media directories, launching the new-and-improved PhpGedView, immediately accessing the Manage Gedcoms menu to export the database to a GEDCOM file and then importing that same just-exported GEDCOM file, replacing all of the database data. If your site has media, DO NOT keep existing media links during the Import.
The import of the just-exported GEDCOM is essential. That's the only way to ensure that the database indexes are properly populated. The Export of the database mentioned above does not involve any of the indexes -- just the raw data is exported.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ERROR 2: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
0 Error occurred on in function preg_replace
1 called from line 1483 of file functions_print.php in function print_text
2 called from line 159 of file login.php
Warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home/oswale7reunion/oswaldreunion/family/includes/functions/functions_print.php on line 1483
You need to upgrade PhpGedView to the version available as an SVN snapshot. This is currently version 4.3.1, but is not yet available as an "official" donwload. That will happen sometime in the new year, as I find time to build the release files.
At the top of this page, click on "SVN" and follow the links. You want the "trunk" branch.
There are lots of posts in the Help forum that deal with the upgrade procedure.
On the other hand, if you're just starting out (a new PhpGedView installation), you might be better served if you use Webtrees instead of PhpGedView. Webtrees was created from PhpGedView over 10 years ago, when almost all of the original developers left the project. Webtrees has better support. I have stuck around because PhpGedView does exactly what I want it to do, and I see no reason to switch.
Thanks so much for the response.
We have a lot of work in the current version of PhpGedView but I am starting
to get errors.
Not sure I am comfortable switching to a whole new program.
Art Oswald
Learntitle.com, LLC
551 404 5341
https://www.linkedin.com/in/artoswald/ 120px-LinkedIn_Logo_svg
https://www.facebook.com/Learntitlecom-278155759495/ facebook sig
https://twitter.com/Title_Ed twitte-sig
http://learntitle.com/titletalk/ blog sig
https://www.pinterest.com/artlearntitleco/pins/ Pinterest sig
From: Gerry Kroll [mailto:canajun2eh@users.sourceforge.net]
Sent: Friday, December 27, 2019 6:36 PM
To: [phpgedview:discussion]
Subject: [phpgedview:discussion] error message when I log in
You need to upgrade PhpGedView to the version available as an SVN snapshot.
This is currently version 4.3.1, but is not yet available as an "official"
donwload. That will happen sometime in the new year, as I find time to build
the release files.
At the top of this page, click on "SVN" and follow the links. You want the
"trunk" branch.
There are lots of posts in the Help forum that deal with the upgrade
procedure.
On the other hand, if you're just starting out (a new PhpGedView
installation), you might be better served if you use Webtrees instead of
PhpGedView. Webtrees was created from PhpGedView over 10 years ago, when
almost all of the original developers left the project. Webtrees has better
support. I have stuck around because PhpGedView does exactly what I want it
to do, and I see no reason to switch.
error message when I log in
https://sourceforge.net/p/phpgedview/discussion/185166/thread/a1c420b678/?l imit=25#d566
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/phpgedview/discussion/185166/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
If you already have a lot of work and time invested in PhpGedView, you are obviously NOT a new user, just starting out. Therefore, switching to Webtrees in favour of PhpGedView is not a good option.
As already stated, you need to upgrade your PhpGedView installation to the latest-and-greatest version 4.3.1, available as an SVN snapshot. This is because older versions are not compatible with the current version of PHP. Version 4.3.1 of PhpGedView has been run successfully on all PHP versions from 5.3 right up to 7.3. It should be OK with PHP 7.4 as well, but I don't know of anyone who has tried that. If PhpGedView 4.3.1 has problems with PHP 7.4, those errors can be fixed as long as I'm told about them.
Upgrading PhpGedView is as simple as replacing all of the program code, but retaining the config.php file as well as the index and media directories, launching the new-and-improved PhpGedView, immediately accessing the Manage Gedcoms menu to export the database to a GEDCOM file and then importing that same just-exported GEDCOM file, replacing all of the database data. If your site has media, DO NOT keep existing media links during the Import.
The import of the just-exported GEDCOM is essential. That's the only way to ensure that the database indexes are properly populated. The Export of the database mentioned above does not involve any of the indexes -- just the raw data is exported.