• I receive the following error when activating WP SEO:

    FATAL ERROR: Allowed memory size of 805306368 bytes exhausted (tried to allocate 8319100054830872200 bytes) in /…/zarza/wp-admin/menu-header.php on line 96

Viewing 15 replies - 1 through 15 (of 23 total)
  • Which is PHP version? Yoast SEO and WP core are fully compatible with PHP 7.

    But it’s possible to you have installed some deprecated plugin or code. There are similar report https://github.com/Yoast/wordpress-seo/issues/5793 without any feedback.

    Can you provide more details about other plugins and versions? I can try to reproduce your issue on my test server.

    Thread Starter Kevin Mamaqi Kapllani

    (@kevinmamaqi)

    Hello @sa?a,

    PHP Version: 7.0.14.

    List of plugins:

    • Advanced Custom Fields
    • Advanced Custom Fields: Flexible Content Field
    • Advanced Custom Fields: Gallery Field
    • Advanced Custom Fields: Repeater Field
    • All-in-One WP Migration
    • Broken Link Checker
    • Contact Form 7
    • EWWW Image Optimizer
    • Ginger – EU Cookie Law
    • LayerSlider WP
    • Portfolio Post Type
    • Quick Bulk Post & Page Creator
    • Redirection
    • Slider Revolution
    • WooCommerce
    • Woocommerce Advanced Bulk Edit
    • WooCommerce Stripe Gateway
    • Wordfence Security
    • WordPress Importer
    • WP-Optimize
    • WPBakery Visual Composer

    I am using the premium Kalium Theme: https://themeforest.net/item/kalium-creative-theme-for-professionals/10860525

    I’ve installed many plugins from your list together with Yoast SEO on various websites. I didn’t use following plugins:

    https://www.ads-software.com/plugins/quick-bulk-post-page-creator/
    https://www.ads-software.com/plugins/portfolio-post-type/
    https://www.ads-software.com/plugins/ginger/

    Also, all of these plugins aren’t tested with newer WP versions. So, you can try to deactivate all of them first.

    Theme seems as compatible with latest versions. Is everything updated to the latest versions? I’ll try later to install fresh WP with these plugins.

    Thread Starter Kevin Mamaqi Kapllani

    (@kevinmamaqi)

    The problem must be with yoast. Tried to deactivate these plugins and installed Yoast. The plugin page worked (mysite.com/wp-admin/plugins.php), but the dashboard (mysite.com/wp-admin/index.php) still have the same message.

    Yoast SEO Error

    IMG URL: https://imgur.com/a/PNxVe

    I’ll try to reproduce your issue later. I’ve installed PHP 7.0.12. Also, PHP error is very weird because it’s echo function (WP 4.7). It needs millions TB ???

    Can you switch to PHP 5.6 for test if it’s easy for you? Is it shared hosting or something else? Can you install QM (Query monitor). It’ll show memory usage for each page (in admin top bar), so we can see how much memory uses each page.

    Does it affect only main page of WP dashboard? Can you open other pages? If so, can you see memory usage with QM?

    Possible issues in PHP:

    https://bugs.php.net/bug.php?id=71645
    https://bugs.php.net/bug.php?id=73728
    https://bugs.php.net/bug.php?id=73729

    Last two bugs are related to PHP 7.0.14 (remi RPM package) and it’s similar as your issue.

    I’ve installed Yoast SEO on many websites (with different PHP versions) and it works without any problems on PHP 7.0. I didn’t yet test PHP 7.0.14 (released 08 Dec 2016).

    Maybe you can post this issue on github – https://github.com/Yoast/wordpress-seo/issues
    Please provide exact PHP version (shared hosting or VPS with remi or other repository), WP version,… Can you provide result of phpinfo.php?

    Thread Starter Kevin Mamaqi Kapllani

    (@kevinmamaqi)

    I also use it on many sites in the same server (siteground shared hosting). For example https://www.kevinmamaqi.com/, the site is on this subdomain (linked to phpinfo): https://zarza.kevinmamaqi.com/phpinfo.php

    I will open an issue on Github, thanks for your help.

    @fandangointeractive Could you help us?

    It’s very weird. I can’t reproduce it on my test servers. I saw they you had same issues:
    https://www.ads-software.com/support/topic/yoast-3-6-not-working-on-php-7/
    https://www.ads-software.com/support/topic/breaks-admin-on-php7/

    Someone in the Advanced WordPress group on Facebook said a while ago that this is most likely a Siteground issue and not related to either WP or any of the plugins. I never even thought of that until this guy pointed it out but he is probably right. I still have the same issues on all of the web sites in question, and they’re all with Siteground (although on cloud hosting).

    So @kevinmamaqi, please open a ticket at Siteground. If more people report the issue then they hopefully will put some priority on it.

    Thank you very much @fandangointeractive

    Can you look https://github.com/Yoast/wordpress-seo/issues/6305 ?
    It seems that you just confirmed my suspicions that they aren’t properly tested their PHP 7.0 installation.

    I looked at the link but to be honest I haven’t much of a clue about the technical aspects of this – just trying to report issues and symptoms from a user/admin perspective.

    But here is the permalink to the Facebook post where someone mentioned Siteground as the most likely culprit. It’s in a closed group so I don’t know if you can see it, but I’m posting it anyway. Please remove if inappropriate.

    https://www.facebook.com/groups/advancedwp/permalink/1309688169093394/

    Thread Starter Kevin Mamaqi Kapllani

    (@kevinmamaqi)

    Thank you all. I just opened a support ticket on Siteground. Will be back with more information.

    Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    Hey, Hristo from SiteGround here. I will reply on your ticket too but wanted to shed some light on the issue for everyone because it may be useful for others.

    One important thing – we at SiteGround, do not modify the PHP service in any way. We use the official release and just configure the opcode caching. So there is no such thing as SiteGround’s PHP7 which I stated in the above mentioned AWP thread too by the way ??

    Now, this particular issue was caused by another plugin that does not yet work well with PHP7.0.x – Broken Link Checker. It uses some dpricated functions and generally has issues with PHP 7.0. I guess in following updates those issues will be addressed. However, it’s not Yoast or us, it’s just the error showing on random pages when the plugin is active.

    Hi @hristo-sg

    I tested again this issue in VirtualBOX with cusom PHP build (configured with opcache-file). When I enable this kind of opcache:

    
    extension_dir = "/usr/local/php70/lib/php/extensions/no-debug-non-zts-20151012/"
    zend_extension = opcache.so
    opcache.enable = 1
    opcache.file_cache=/home/user/.opcache
    

    After few requests, I see similar errors as described (500 errors in many posts here):

    Uncaught Error: Call to undefined function get_default_post_to_edit()
    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 9223378990237523968 bytes) in …/wp-includes/media-template.php on line 165

    Then I removed .opcache directory and I disabled opcache extension. Everything works as should.

    I tried to test it without plugin Broken Link Checker. It’s same. With opcache file, I’ve to disable Yoast SEO or other plugins to avoid strange fatal errors. Also, some Joomla users have reported similar behaviour.

    Other my installation (I can’t experiment there) uses FCGI+opcache (PHP 7.0) and I never noticed anything similar.

    It requires more testing from both sides. Also, many errors are after update. (which I reproduced)

    @fandangointeractive @kevinmamaqi Can you try to disable opcache and test everything again? I want to help you if you don’t know how to do it.

    Hi

    @stodorovic – I don’t know how to disable opcache so would need some help.

    @hristo-sg – I am not using Broken Link Checker but still get this kind of error on all web sites where Yoast is activated. I have an open ticket over at Siteground where your techs have access to a staging copy of a web site where the issue is present.

Viewing 15 replies - 1 through 15 (of 23 total)
  • The topic ‘FATAL ERROR: Allowed memory size of 805306368 bytes exhausted’ is closed to new replies.