[ChristianModerator]

If it works, there’s no need to downgrade.

[Jonathan FParticipant]

Any updates to this? This is extremely important!

[ChristianModerator]

Hey Jonathan,

If Cornerstone breaks in PHP 7 for you, the solution would be to downgrade to 5.6.

I have PHP 7 in my test site and there is no issue with Cornerstone though.

You might have enabled some settings that is not compatible with Cornerstone. Please disable PHP features one by one and check if the issue persists each time.

Thanks.

[Austin AbellParticipant]

Hi there! I host on wpengine and they have a plugin that checks the compatability of my site with php 7. I ran a test and got the following cornerstone error. Just wanted to pass along to you guys!

https://wordpress.org/plugins/php-compatibility-checker/?hsCtaTracking=45a3492d-241a-45db-a386-c2bfac1ebd8f%7C45cc88e9-2e65-4b92-b465-f3bb1b2c21ef&utm_campaign=php7&utm_medium=email&_hsenc=p2ANqtz-9AhLUuGuK6gtYEELYRk1ga3NLBwdlwuRtjTIs6NEf3MGpQyJys9RON6c4EvSeggZWLpH2V9CCfOhyI2OS1t8QlhecAbrmwB5p6ExzldOiS0uycmX8&_hsmi=43053269&utm_source=hubspot

[powerboardParticipant]

I would also like to see a fix here. I get the same error. WPengine is my host

[RadModerator]

Hi there,

A deprecated feature usually triggers notices or warnings, and not the error since they are not actually errors. In some case, it can affect the functionality of a software (eg. plugin) but I don’t see any issue from my end. According to the screenshots, those /e exist on line 387, 465, and 480 but I don’t see them

387 :

$code = preg_replace("'(?<![\$.a-zA-Z0-9_])while\('", '3#(', $code);

465 :

$f = preg_replace("'(?<![\$.a-zA-Z0-9_])else\n'", "\n", $f);

480 :

$f = preg_replace("'(?<![a-zA-Z0-9_\$])for\neach\('", 'for each(', $f);

You’ll notice, they all have just letter e and not actually /e. I’m not sure how their scanner works but if the plugin will recognize the preg_replace as faulty because of letter e then it’s wrong. And that also means preg_replace("'Hello_World'") is wrong as well.

But I understand what’s the error means and it shouldn’t use /e modifier.

http://php.net/manual/en/function.preg-replace.php
Support for the /e modifier has been removed. Use preg_replace_callback() instead.

Thanks!

[Austin AbellParticipant]

Ok, so it sounds like cornerstone is compatible and will work with php 7.0?

I know very little about these things. All I know is WP engine told me to check the compatibility of my site with WP Engine and Cornerstone came up with these errors. Thanks for the clarification!

[JoaoModerator]

Hi There,

Although we do not officially support php 7 yet on most installations it is working fine.

Thanks

[Austin AbellParticipant]

Ok thanks!

[RadModerator]

You’re welcome!

[Launch48Participant]

Hey there!

This thread is now the number one Google result for ‘Cornerstone PHP7’! We have quite a few sites running X-Theme and using Cornerstone – do you have an official update on this? Unfortunately with this many we can’t test them one by one, we’d love to have this officially supported.

[Austin AbellParticipant]

As an update on my comment, I switched my site and it’s working great 🙂 No issues at all!

[JadeModerator]

You’re welcome Austin.

[Launch48Participant]

Hi Jade, any answer to my request for an update above?

[RadModerator]

Hi there,

We don’t have any updates yet, but cornerstone should be working fine with PHP 7.0. Plus, cornerstone and X theme is only using the resources provide by WordPress. If there is any issue with version then it’s WordPress that’s going to fail first.

Thanks!

[Author]

Posts