Conflict with PHP 7

@shazzalive,

Did you contact your web host? This error occurs when your server runs out of memory to complete the task at hand. Increasing the memory allotted or decreasing the number of tasks will fix the issue.

Alternatively, there are some other workarounds to resolve this issue as outlined on this guide.

Ivan Atanasov from SiteGround here.

@suascat_wp, indeed the application exhausted the allocated limit and tried to allocate another 7311100810172247704 bytes. Clearly, there is an issue here, possibly a memory leak.

@shazzalive, I would also recommend that you post a ticket from your SiteGround User Area -> Support. You can also share your ticket ID here, so that I can review the situation.

@suascat_wp

@ivanatanasov

Yes I have contacted my web host. Their reply was: –

“I had problems logging in the dashboard, which were caused by PHP 7.0. I had to switch to PHP *.*. so I can get in (otherwise I was getting a 500 Internal Server Error).

I think this resolved the original issue with Yoast as well, as I do not see the error in the Yoast SEO section any more.

Most probably, there is some kind of a conflict that is created by using PHP 7.0 with one or more elements of your website. I am not able to tell which one, and if you would like to investigate the issue further it is recommended that you contact a professional WordPress developer.

Please verify results on your end and let us know if you require further assistance.”

I verified that the move back to PHP *.* had resolved the issue… All this happened prior to posting here.

Ticket 2347313 for account buggerallon.tv
Using WP 4.8 with TwentyFifteenPlus theme ( My own hack of the TwentyFifteen theme by the WordPress Team.)

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

@shazzalive We confirm that Yoast SEO is compatible with PHP 7.0. In fact, we recommend our users have an updated PHP version (preferably PHP 7).

Sometimes strange behavior may be caused by a plugin or theme conflict. The fastest way to rule out conflicts is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Seventeen. If this resolves the issue, you have a conflict and should activate one plugin at a time until you locate the conflict. Finally, after all plugins are active, switch to your theme. This will narrow down the conflict to a specific plugin or a theme conflict.

If you are unfamiliar with checking for conflicts, we wrote a small guide that will walk you through the steps. You can find it here: How to Check For Plugin Conflicts

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

@monbauza I’m hoping it’s the memory-leak scenario that @ivanatanasov suggested. – Because my TwentyFifteenPlus theme has a number of specialised customisations (None of which should in any way affect the Yoast plugin.) that I spent most of 2015 coding in to it and debugging. The site simply won’t work properly if I simply switch to TwentySeventeen without one heck of a lot of development and debugging.

As for deactivating the plugins and reactivating them one-by-one: I’ve already done that, and issues with Yoast plugin hiding itself at times continued regardless, followed a number of days later by the fatal error as described above.

Since I’ve been using Yoast SEO since early in 2016, haven’t made any major adjustments to my theme since then, and have only had these issues since moving to PHP 7.0 in late may or early June this year – the fact that a tech reverted my install to an earlier PHP version and the issues with the Yoast plugin vanished totally is rather telling, evidentially speaking.

There’s obviously some kind of issue here, which is triggered only under PHP 7.0. What it is I have no idea whatsoever, nor do I have the technical abilities to be able to debug it single-handed – so I hope someone else can identify the issue for me.

Hi,

We understand there may be an issue on your site with Yoast and PHP 7. Can you confirm that the fatal error memory exhausted appears when your WordPress is v4.8, Yoast SEO 5.1 (if it is not that version, please update via the plugins menu), your PHP is 7, and your theme is Twenty Seventeen?

You may also wish to try this on a staging site. Some staging sites may be provided by your host provider. We ask that you please speak with them. Additionally, if needed, this guide explains more about creating a staging site:?https://www.wpbeginner.com/wp-tutorials/how-to-create-staging-environment-for-a-wordpress-site/.

We ask that as it appears from the prior response only plugins were deactivated. We want to make sure that nothing in custom theme is somehow affecting Yoast and the site resulting in that error.

Let us know.

@pcosta88 The error occurred under the Yoast SEO version previous to 5.1. – I updated to 5.1 yesterday when it was offered to me as an update. The WordPress version was 4.8 under PHP 7.0 when the issue occurred.

I have never used the TwentySeventeen theme. The error occurred under my TwentyFifteenPlus theme. – It is a derivation of and based upon the TwentyFifteen theme by the WordPress Team. I manually update the unchanged files & folders and make any necessary adjustments when there is a theme update published by WordPress. The only changes that I made were to the existing template PHP files. Also several new templates were added by myself, (Extra page templates and a couple of sidebars.) along with a layered chronological post listing structure which divides the standard WordPress default listing into indexed pages

The site is at buggerallon dot tv.

Thank you for the link to the guide on creating a staging site. I wasn’t aware that SiteGround, who I have as my hosts, offer a staging environment as part of their Go-Geek package. I’m on the Grow-Big package currently. – It’s something to bear in mind when considering a future upgrade.

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

Hi,

Were you able to confirm that the “Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 7311100810172247704 bytes) in /home/********/public_html/wp-content/plugins/wordpress-seo/inc/class-wpseo-shortlinker.php on line 31 happens when your PHP is 7, your WordPress is 4.8, your theme is 2017 (unmodified) and your Yoast SEO plugin is 5.1?

@pcosta88 I was/am not. – I am only able to confirm that the “Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 7311100810172247704 bytes) in /home/********/public_html/wp-content/plugins/wordpress-seo/inc/class-wpseo-shortlinker.php on line 31 happens when my PHP is 7, my WordPress is 4.8, and my theme and Yoast SEO plugin are as stated above.

I can confirm that the change of PHP version under the conditions specified by myself to a previous PHP version remedied the issue.

I am unable to find the time to set up a staging area and to perform tests to confirm what you appear to be asking me to confirm by doing so.

If you would like a copy of my site’s backup files from my computers so that you can attempt to replicate the error then I can make said download available to you.

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

Thanks for your offer but we are unable to receive files or log in to users’ sites through this support forum.

If you are able to replicate the problem in the scenario described above (PHP 7, WordPress 4.8, 2017 theme and Yoast SEO 5.1), please contact us again and we’ll be more than happy to look further into this issue.

Closed due to inactivity.