• Resolved Halo Diehard

    (@halo-diehard)


    My Simple:Press forums stopped working, so I deactivated all plugins then reactivated them one at a time. I should have known by the fatal error which plugin it was having a conflict with by the error, but now it’s confirmed, as the forum displays fine when Yoast SEO is deactivated. Any ideas what might be causing this? The error is:

    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 32768 bytes) in …/wp-content/plugins/wordpress-seo/inc/class-wpseo-replace-vars.php on line 1227

    I first noticed the error today. I hadn’t visited the forums for a week or so, so I’m not sure when it started.

    Everything is up to date:

    Wordpress version: 5.0.3
    Yoast SEO version: 9.4
    Simple Press version: 6.0.6

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Halo Diehard

    (@halo-diehard)

    I just found info about the Health Check plugin, installed it and went through the plugins. Yoast SEO and Simple Press get along fine until Wordfence Security is activated, then I get two fatal errors:

    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 65536 bytes) in …/wp-content/plugins/simplepress/forum/content/classes/sp-view-class-spcgroupview.php on line 82

    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 65536 bytes) in …/wp-content/plugins/wordpress-seo/admin/class-yoast-notification-center.php on line 497

    Any and all help appreciated!

    It’s an issue because default PHP memory_limit 64MB (67108864 bytes) is too small if you have activated more “complex plugins”.

    You need to increase memory_limit in php.ini or edit wp-config.phpIncreasing memory allocated to PHP. If you don’t know how please contact your host.

    Thread Starter Halo Diehard

    (@halo-diehard)

    If this were the case, I would have had problems previously to whatever updates has caused the conflict. Also, I don’t believe my PHP memory limit is 64MB, regardless of what the fatal error says. It’s already 128 in my wp-config, and I’m fairly certain I’ve double checked with my host in the past. Strangely enough, after a day of trying to problem solve this, I found if I swapped out a Simple Press forum theme with another theme, the issue resolved. The theme is called CSS-Only (if anyone else runs into this problem), so it’s confusing why it would cause a fatal error, but with the theme activated I could not run Yoast SEO at the same time as Wordfence, and then other fatal errors were showing up in my sidebar widgets for other plugins and files, but only on that forum page.

    Thread Starter Halo Diehard

    (@halo-diehard)

    For anyone else who runs into this issue and finds this thread:

    It turns out that for some reason, my WordPress site was no longer paying attention to my php.ini and wp-config.php files, which I had used to increase my memory years ago, and which had been working fine up until the fatal errors started a few days ago.

    The fatal errors were solved by placing additional php.ini files in both the root and wp-content folders of my site, as well as in wp-admin (where WordPress users are instructed to place the php.ini, and where my existing file was).

    For anyone not familiar with this code, a php.ini file is not included when you install WordPress, and you can create the file using a text editor, saving it as php.ini I have the following code pasted into all three php.ini files in the locations described above. It fixed all of my fatal errors, which were occurring on my forum page as well as in widgets, depending on what page I was on.

    memory_limit = 512M;
    max_input_vars = 5000;
    post_max_size =256M;
    max_file_uploads = 300M;
    max_execution_time = 180;
    max_input_time =120;
    upload_max_filesize = 128M;

    Hope this helps someone like it helped me!

    • This reply was modified 5 years, 10 months ago by Halo Diehard.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal Error in Forums when Yoast SEO is activated’ is closed to new replies.