[tomrogersParticipant]

Greetings!
The am in discussions with a client to develop a new online store using WooCommerce. Meanwhile, I’m working on a new store with a different theme, but when I reviewed the WooCommmerce System Status, it warned that my server is using PHP version “5.4.45 – We recommend a minimum PHP version of 5.6”

I could not readily find the X theme requirements (and requirements for related X plugins).

My hosting company is willing to upgrade my VPS account to 5.6, but warned that there may be compatibility issues with other plugins. I have 5 other WordPress websites running on my server account and I don’t want to find out later that things aren’t working as a result of the change to a more advanced version of PHP.

This led me on a time consuming mission to determine if it was safe to change it. But it’s hard to find the specs for plugins.

I installed a plugin called WP Engine PHP Compatibility Checker on another website (not X based) which looks to the installed plugins and themes to see if there are any issues. But unfortunately it checks only 5.3, 5.4, 5.5, and then skips to 7.0. It also can’t check larger plugins and themes, so it’s not the best tool. I’m sure it would be the same issue with X.

The author wrote back to my forum posting and said “PHP 7 is a major project release with substantial performance improvements, new features, and has a lengthy official support life through 2017. WP Engine is putting our focus on the future and encouraging our customers to move directly to PHP 7.”

I can go with version 5.6, or 7, but am fearful of complications.

Will X, and all X related plugins work with 5.6, and how about PHP 7?

Is there a minimum spec for MySQL? I am currently running 5.1.73.

Do you happen to know if some of the major plugins will work with PHP 7? These are the ones I typically use:

Category Order and Taxonomy Terms Order
Limit Login Attempts
Password Protected
UpdraftPlus – Backup/Restore
WooCommerce
Anti-Malware Security and Brute-Force Firewall
Global Content Blocks
Simple 301 Redirects
Post Types Order
Toast SEO
WordPress SEO (Yoast)

Or do you know of an easy way to find out if they will work?

Thanks in advance,
Tom

[Rue NelModerator]

Hello Tom,

Thanks for writing in and the very detailed post. Here at Theme.co we always abides the WordPress standards. We have tested over and over that the X theme and Cornerstone will work smoothly with whatever is the minimum requirements of WordPress. WordPress 4.5 requires at least 5.6 (https://wordpress.org/about/requirements/). If you have PHP7, it X and Cornerstone plugin should work fine as well.

Hope this explain it briefly.

[Thomas KParticipant]

Hi, there seem to be some compatability challenges. I will have to switch to either 5.6 or 7 this week. PHP Compatibility Checker (see above) tells me that Cornerstone, Slider Revolution and WPBakery Visual Composer are not compatible with either of these PHP versions.
Here are the results:

Cornerstone
FILE: /www/htdocs/w00edda6/cms/wp-content/plugins/cornerstone/includes/utility/jsqueeze.php
——————————————————————————————-
FOUND 3 ERRORS AFFECTING 3 LINES
——————————————————————————————-
387 | ERROR | preg_replace() – /e modifier is forbidden since PHP 7.0
465 | ERROR | preg_replace() – /e modifier is forbidden since PHP 7.0
480 | ERROR | preg_replace() – /e modifier is forbidden since PHP 7.0
——————————————————————————————-

Slider Revolution

FILE: /www/htdocs/w00edda6/cms/wp-content/plugins/cornerstone/includes/utility/jsqueeze.php
——————————————————————————————-
FOUND 3 ERRORS AFFECTING 3 LINES
——————————————————————————————-
387 | ERROR | preg_replace() – /e modifier is forbidden since PHP 7.0
465 | ERROR | preg_replace() – /e modifier is forbidden since PHP 7.0
480 | ERROR | preg_replace() – /e modifier is forbidden since PHP 7.0
——————————————————————————————-

Visual Composer

FILE: /www/htdocs/w00edda6/cms/wp-content/plugins/js_composer/include/templates/teaser.html.php
————————————————————————————————————————————————————
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————————————————————————————
83 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%= id %>” src=”<%= url %>”…
————————————————————————————————————————————————————

FILE: /www/htdocs/w00edda6/cms/wp-content/plugins/js_composer/include/templates/editors/partials/backend-shortcodes-templates.tpl.php
————————————————————————————————————————————————–
FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 3 LINES
————————————————————————————————————————————————–
43 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%= type %>”>
44 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%= heading %></div>
46 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%= form_element %>
————————————————————————————————————————————————–

FILE: /www/htdocs/w00edda6/cms/wp-content/plugins/js_composer/js_composer.php
———————————————————————————-
FOUND 1 ERROR AFFECTING 1 LINE
———————————————————————————-
211 | ERROR | Visibility for magic method __sleep must be public. Found: private
———————————————————————————-

Are these false positives or will I really have problems running X including the standard plugins on php 7?

[DarshanaModerator]

Hi there,

Better to stick with PHP v5.6.x as it has lesser known issues and also WordPress recommends it.

Thanks!

[Thomas KParticipant]

Thank you, Darshana. Good to know.

But again: Are Cornerstone, Slider Revolution and Visual Composer compatible with 5.6.X? Will they work despite the errors?

Cornerstone:
FILE: /www/htdocs/w00edda6/cms/wp-content/plugins/cornerstone/includes/utility/jsqueeze.php
——————————————————————————————-
FOUND 3 ERRORS AFFECTING 3 LINES
——————————————————————————————-
387 | ERROR | preg_replace() – /e modifier is deprecated since PHP 5.5
465 | ERROR | preg_replace() – /e modifier is deprecated since PHP 5.5
480 | ERROR | preg_replace() – /e modifier is deprecated since PHP 5.5
——————————————————————————————-

Slider Revolution:
FILE: /www/htdocs/w00edda6/cms/wp-content/plugins/revslider/includes/slider.class.php
————————————————————————————————————————–
FOUND 1 ERROR AFFECTING 1 LINE
————————————————————————————————————————–
2345 | ERROR | ‘clone’ is a reserved keyword introduced in PHP version 5.0 and cannot be invoked as a function (T_CLONE)
————————————————————————————————————————–

FILE: /www/htdocs/w00edda6/cms/wp-content/plugins/revslider/includes/output.class.php
————————————————————————————————————————-
FOUND 1 ERROR AFFECTING 1 LINE
————————————————————————————————————————-
458 | ERROR | ‘clone’ is a reserved keyword introduced in PHP version 5.0 and cannot be invoked as a function (T_CLONE)
————————————————————————————————————————-

Visual Composer:
FILE: /www/htdocs/w00edda6/cms/wp-content/plugins/cornerstone/includes/utility/jsqueeze.php
——————————————————————————————-
FOUND 3 ERRORS AFFECTING 3 LINES
——————————————————————————————-
387 | ERROR | preg_replace() – /e modifier is deprecated since PHP 5.5
465 | ERROR | preg_replace() – /e modifier is deprecated since PHP 5.5
480 | ERROR | preg_replace() – /e modifier is deprecated since PHP 5.5
——————————————————————————————-

Thank you for your help!

[Paul RModerator]

Hi Thomas,

Yes, everything should work with php 5.6

I need to check why you are getting these errors.

Would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:

– Link to your site
– WordPress Admin username / password
– FTP credentials

Don’t forget to select Set as private reply. This ensures your information is only visible to our staff.

[Thomas KParticipant]

This reply has been marked as private.

[ChristianModerator]

Hey Thomas,

Are the errors affecting your site or cause a malfunction? If not, those are negligible. They are not false positives either but developers could not replace them without extensive compatibility testing which takes a considerable amount of time so there’s nothing we could do with it currently. But eventually, the functions will be replaced with the newest version. Please stay tuned.

Thanks.

[Thomas KParticipant]

Thank you for your help! :o))

[Rue NelModerator]

You are most welcome!

[Author]

Posts