afogerty

We currently have a CentOS 6.8 machine running Jigoshop 1.18, PHP 5.6.25 and WordPress 4.9.6. According to my notes I originally installed it with PHP 5.2.17, which was the latest at the time. It looks like it has either automatically updated or the web developer has done this.

That version of the website is live and in production, so we are in a good place, but when I make a copy of the WWW folder & SQL database, and put it onto the new CentOS 7.2 machine I’ve just built with PHP 7.2.7, all I see are white pages for the products. When I migrate to Jigoshop eCommerce it just gives me white pages for everything.

• This reply was modified 6 years, 5 months ago by afogerty.

Interesting.

HTTP Response Headers X-Powered-By PHP/5.3.3

Core = PHP Version 5.3.3

So for some reason it is still choosing the older version. Using php -v still gives me version 5.6.25. What am I missing?

Just tried the update again and it resulted in most of the website being blank. I can’t tell now if this is specifically a PHP issue or something else that Jigoshop needs but doesn’t have.

Now that there are two versions on the same machine, is there a way to easily find out what version of PHP Jigoshop and WordPress are using?

With CentOS it is “sudo service httpd restart”, but yes, I have ??

I will try updating Jigoshop again tomorrow morning and will let you know how it goes.

Hi Paul,

Thanks for your reply.

I’m a MCSE with a strong background in Microsoft products and network infrastructure, specifically virtualisation technologies (VMware, Hyper-V); Linux is relatively new to me (1.5 years) so I thank you for your patience.

– As I understand it, there is no upgrade path from CentOS 6 to CentOS 7; according to the CentOS forum it was removed after too many failed upgrades, something about CentOS 6 having “newer” files than CentOS 7 and this caused the upgrade to fail leaving a bricked OS.

– Since your suggestion about Software Collections I have installed PHP 5.6 but I can’t seem to get WordPress / Jigoshop to use that version. I’m probably missing something obvious. When I do a PHP -v in terminal it says PHP 5.6 but when I attempt to update Jigoshop it says I’m only using PHP 5.3.3.

I followed this page to install it:

https://www.softwarecollections.org/en/scls/rhscl/rh-php56/

Perhaps you can tell me how to direct Jigoshop to only use the PHP 5.6 in the OPT directory?

– In 10 days when the company has finished their summer sale I will uninstall PHP 5.3.3 and install PHP 7.1 unless I can get the software collection to work.

– If I can’t get the first two options to work then I might look at doing a clean install of CentOS 7. I have avoided CentOS 7 because I’m told that systemd is difficult to use and when things go wrong it becomes a nightmare for young players (like myself).

Hi Paul,

The latest supported version of PHP for CentOS 6 (currently v6.8) is PHP v5.3.3. PHP v5.4 and onwards removes backwards compatibility and so as I understand it there is no upgrade path from v5.3.3 to v5.4 for CentOS 6 without a complete uninstall and reinstall of PHP.

I was today alerted to the fact that the latest Jigoshop requires PHP 5.6 but this could end up breaking other parts of our webserver if we upgrade. I too want to know if it is “essential”.

• This reply was modified 7 years, 10 months ago by afogerty.

Just a note, the official solution to add the line (below) still kills the backend (white screen) but keeps the frontend (website) running:

remove_action(‘wp_enqueue_scripts’, ‘wordfence::enqueueAJAXWatcher’);

I’m having the same problem, definitely a Wordfence issue. Blank white page after updating from Wordfence 6.1.8 to Wordfence 6.1.9.

My solution below:

1) Edit wp-config.php to stop automatic plugin updates, comment out this line:

add_filter( ‘auto_update_plugin’, ‘__return_true’ );

2) Rename or delete the Wordfence folder under /wp-content/plugins/

3) Disable Wordfence plugin in WordPress backend (it should do this automatically)

4) Restore Wordfence folder from 24 hours ago from backups

5) Activate Wordfence plugin in WordPress backend

All fixed!

I will now wait for Wordfence 6.2.0 ??

Yes, as I suspected there are bits in the front page of the website that are “hard coded” to use the ‘Post Name’ format and they are all broken.

I went to Settings -> Permalinks and it is set to ‘Post name’. On the live, working website it is also set to ‘Post name’.

I selected ‘Default’, saved it, and it now works perfectly.

I then selected ‘Post name’ and strangely it doesn’t work using the original ‘Post name’!

Any ideas why this might be? Ideally I would prefer to use the original ‘Post name’ if it is possible so that I’m not potentially messing up something else?

Thank you for your prompt reply Vasili. The only thing I can see that refers directly to Jigoshop is this error message in error_log under httpd:

[Tues Oct 13 10:39:24 2015] [error] [client 192.168.0.225] File does not exist: /var/www/html/product-category, referer: https://www.mywebsite.co.nz/

Accessing the FTP for the live, working website tells me that that folder doesn’t exist there either so I’m a little confused as to the mechanism that your plugin uses. I assume that the folder “product-category” is made using a Javascript of some sort?