Pawtucket 2.0.6 not working

atzemaej

Good Morning,

I just tried to update Providence and Pawtucket to 2.0.6 from a working 2.0.5 install. Providence seems to be working fine, but for Pawtucket I get a blank page. My browser's developers view complains that the body could not be loaded ("JQMIGRATE: Migrate is installed, version 3.4.0 ... Failed to load resource: the server responded with a status of 500 ()"). My 2.0.5 install of Pawtucket works perfectly fine with the 2.0.6 install of Providence. After unzipping pawtucket2-2.0.6.zip (which shows all files dated May 30, 11:26am), all I did to finish the install of Pawtucket 2.0.6 was to copy my setup.php from my 2.0.5 setup to my 2.0.6 directory and to link the media directory. Something must be different from 2.0.5 to 2.0.6. Could it be the format of setup.php? It goes back to 1.7 if not earlier. Any suggestions would be appreciated.
Thanks,
Eisso

atzemaej

Adding one more observation:

When I compare the HTML source for my working 2.0.5 Pawtucket install with that of the 2.0.6 Install (that does not work) it appears that the HTML for the head for the latter is generated fine---except for the "</head>" part. The HTML source code abruptly stops after

In the code for my 2.0.5 install this is followed by </head> and then "<body>...</body>" etc. I would say this means there is a problem with the php code right before "</head>" is to be printed. But then, I do not really know much about php programming. Also, I did composer up on both installs and the only potentially noteworthy message was that 2.0.5 apparently uses three abandoned packages: laminas/laminas-zendframework-bridge, maximebf/debugbar, and php-debugbar/php-debugbar. It appears 2.0.6 no longer uses these packages.
Thanks,
Eisso

seth

You need to strip any references to Debug functions from your header and footer. We removed those functions in 2.0.6 because the underlying javascript libraries are now abandoned and causing warnings. In retrospect this was not a great idea as it causes errors in old themes that have Debug calls in them. So perhaps it's time for a 2.0.7 with a restored Debug stub class to avoid causing errors in these older themes.

atzemaej

Hi Seth,
A version 2.0.7 might not be a bad idea, but commenting out the one reference to debug in each of pageFooter.php and pageHeader.php (right before printing "</head>"!) fixed the problem.
Thanks,
Eisso

seth

Yes. But 2.0.7, which is available now will save you that work.

behindicebergs

I believe this was the issues affecting my project as the Apache logs mentioned many calls to the Debug function, will try an update tomorrow. Thanks Seth and atzemaej!