[pmwiki-users] Problems with my PMWiki Site after Update to PHP7.2 (from PHP5.6)

Michael Lang miclang at arcor.de
Thu Mar 21 01:24:20 PDT 2019


Thanks, Kevin, I will check that! - Regards, Michael

Am 20.03.2019 um 17:30 schrieb Kevin R. Bulgrien:
> ----- Original Message -----
>> From: "Michael Lang" <miclang at arcor.de>
>> To: pmwiki-users at pmichaud.com
>> Sent: Wednesday, March 20, 2019 10:26:27 AM
>> Subject: Re: [pmwiki-users] Problems with my PMWiki Site after Update to PHP7.2 (from PHP5.6)
>>
>> There is no error.log file!
>>
>> Am 19.03.2019 um 17:04 schrieb Mikhail Ustinov:
>>> Usually it is in the root of the site (/public_html or may be
>>> /public_html/pmwiki).
>>>
>>> You need ssh or ftp access to the site.
>>>
>>> 19.03.2019 18:29, Michael Lang пишет:
>>>> Where do I find the file error.log?
>>>>
>>>> Am 19.03.2019 um 16:18 schrieb Mikhail Ustinov:
>>>>> Check your error.log
>>>>>
>>>>> May be you use some recipes that doesn't work under PHP7.2
>>>>> because
>>>>> uses obsoleted PHP functions.
>>>>>
>>>>> BR
>>>>> Mike Ustinov
>>>>>
>>>>> 19.03.2019 18:10, Michael Lang пишет:
>>>>>> Hi,
>>>>>> my provider did an update to PHP7.2 (from PHP5.6) - after this I
>>>>>> had severe problems with my PM Wiki site; all pages have been
>>>>>> empty; the sidebar wasn't visible.. I had a small window to go
>>>>>> back
>>>>>> to PHP5.6 and I did an PM Wiki update to 2.2.113 (from 2.2.14) -
>>>>>> under PHP5.6 everything was fine, but after my provider finaly
>>>>>> switched to PHP7.2 I had the same problem. Any advice?
>>>>>> Regards, Michael
> I had to resurrect a pmwiki when I updated from PHP 5.6 to PHP 7.2 on
> RHEL.  The problems were entirely related to plugins or skins.  Many
> required updating, but many of them in use were no longer currently
> maintained, so it ended up that they had to be fixed or removed.  It
> wasn't easy to remove them, so fixing became the best option, and the
> patched files were uploaded to the relevant plugin pages on the
> PMWiki project wiki.
>
> There is no information given about what plugins or skins might have
> been in use, etc.  It seems unlikely for help to be possible with so
> little effort given to providing information.
>
> Was a backup of the wiki made at any time?  Providers like Softaculous
> offer backups being made before updates.  Even if not made before an
> update, a backup made after would potentially allow for dropping
> the files on a local system or VM to debug if the web host does
> not allow shell access.  Did you ask for shell access?
>
> Here are brief notes about the site I fixed:
>
> 	KB: 2018/12:
> 	
> 	The pmwiki site broke completely after upgrading from PHP 5.6 to PHP 7.2.
>   	The breakage appeared to be exclusively due to “Warning: preg_replace(): The
> 	/e modifier is no longer supported” issues.
>   	
>   	To address the issues, first, the site was upgraded to: pmwiki-2.2.110
>   	
>   	The triad skin was updated to the newest available at the time of the repair.
>   	
>   	Numerous cookbook files were either upgraded from the pmwiki site, or were
>   	locally patched.  In most cases, locally patched files were uploaded to the
>   	pmwiki site (https://pmwiki.org/wiki/Cookbook/) pages pertinent to the files
>   	that were edits, though in two cases, the pmwiki recipe pages were themselves
>   	affected by the preg_replace error, and changes could not be shared at the
>   	time they were made.  The list of cookbook's modified:
>   	
>   	-rw-r--r--. 1 SDwiki apache  3395 Dec  7 15:19 includeurl.php
>   	-rw-r--r--. 1 SDwiki apache  2568 Dec  7 15:14 handytoc.php
>   	-rw-r--r--. 1 SDwiki apache 21858 Dec  7 15:03 zap.php
>   	-rw-r--r--. 1 SDwiki apache 33265 Dec  7 15:00 wikilog.php
>   	-rw-r--r--. 1 SDwiki apache 42757 Dec  7 14:32 pmcal.php
>   	-rw-r--r--. 1 SDwiki apache 36879 Dec  7 14:24 markup.php
>   	-rw-r--r--. 1 SDwiki apache  8822 Dec  7 14:02 emenu2.php
>   	-rw-r--r--. 1 SDwiki apache  1744 Dec  7 13:53 emenu.php
>   	-rw-r--r--. 1 SDwiki apache  6985 Dec  7 13:41 break_page.php
>   	-rw-r--r--. 1 SDwiki apache 10681 Dec  7 13:38 AdvancedTableDirectives.php
>   	-rw-r--r--. 1 SDwiki apache  5661 Dec  7 13:34 convert-html.php
>   	-rw-r--r--. 1 SDwiki apache 46369 Dec  7 13:14 zaptoolbox.php
>   	-rw-r--r--. 1 SDwiki apache 43836 Dec  7 11:43 totalcounter_1_9_2.php
>   	-rw-r--r--. 1 SDwiki apache  3706 Dec  7 11:24 menus.php
>   	-rw-r--r--. 1 SDwiki apache  3700 Dec  7 10:59 numtoc.php
>   	-rw-r--r--. 1 SDwiki apache  5391 Dec  7 10:33 feralsimplecalendar.php
>   	-rw-r--r--. 1 SDwiki apache  1248 Dec  7 10:31 treemenu.php
>
> Naturally, your site will not be identical, but if you have things in the
> cookbook folder, probably they should be checked first and upgraded or
> edited as needed.  When looking for upgrades, don't just download the
> plugin/skin tarball.  Many plugins have individual files posted when a
> maintainer is not actively maintaining them.
>
> Other places for files that needed fixing were pub/* folders associated
> with plugins or skins, though for me, only handytoc put files there
> that needed changing.
>
> You should probably enabled diagnostics by uncommenting a line in the
> local/config.php file:
>
>    # $EnableDiag = 1; # enable remote diagnostics
>
> There were only a few types of changes that had to be made.  Provided that
> they turn out to be relevant, you could also look at how I changed the
> aforementioned files by examining what was uploaded to the plugin page
> and comparing it to the original published file.
>
> Good luck.  Without more facts, actual help is hard to give.
>
> Kevin
>




More information about the pmwiki-users mailing list