• Resolved Tim Nolte

    (@tnolte)


    When we have the Yoast SEO plugin active there is some odd interaction with the Revisions plugin that is causing a fatal error due to memory exhaustion.
    Allowed memory size of 536870912 bytes exhausted (tried to allocate 4096 bytes) web/wp-content/plugins/wordpress-seo/lib/orm.php:235
    I’ve opened up an issue with Yoast SEO as well.

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    Hi @tnolte

    The error says your memory limit is hit. Have you tried to increase your PHP memory limit? You can do that by give this constant on wp-config.php

    define( ‘WP_MEMORY_LIMIT’, ‘512M’ );

    If the error persist, try change “512M” to “1024M”

    Thread Starter Tim Nolte

    (@tnolte)

    The site runs on Pantheon so the ability to increase that limit is well restricted. The site is already on a plan that is set to use 512M. If you do the calculation you can already see that 536870912 bytes comes out to around 536 Mbytes.

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    As the error says, it’s all memory limit. If Pantheon is restrict it, nothing we can do on our side.

    However, please note that the free version of Revisions does not support Yoast SEO. It only supports in the Pro version. See: https://publishpress.com/knowledge-base/plugins-revisions-support/

    Thread Starter Tim Nolte

    (@tnolte)

    So the problem however is that there are not even any pending revisions. The fact that there aren’t even any Revisions and there is a memory problem points to some sort of code issue. We’ve been running the plugins, both of them, just fine for over a year on the same Pantheon hosting and this just started up.

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    Okay, Based on your last description, looks like it’s either there is other plugins that cause it, or a bug, or a custom script that cause memory limit.

    Could you confirm if you have the latest version for both PublishPress Revisions and Yoast SEO? Because I had no issue as you mentioned having both plugins activated.

    If it’s already in the latest version, try troubleshooting by deactivating all plugins except Yoast and PublishPress Revisions. On this step, check if you still see that error.

    If the error disappear, activate your plugins one by one to find out which plugin cause it.

    Let me know how it goes.

    Thread Starter Tim Nolte

    (@tnolte)

    Revisions: 3.1.6
    Yoast SEO: 19.7.1

    I attempted to deactivate all plugins and with only Revisions & Yoast active I still get the error. Additionally, as soon as I disable Yoast SEO things work just fine on the Revisions screen.

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    I’m afraid you will need to wait for the answer from the Yoast team on this. Maybe there is misconfiguration or else. Also the error says specific file on Yoast side. Maybe that will help their investigation.

    web/wp-content/plugins/wordpress-seo/lib/orm.php:235

    Plugin Author Kevin Behrens

    (@kevinb)

    @tnolte Did you ever resolve this Yoast SEO conflict? If not, I would be interested in seeing a backtrace from the error if it’s available. You could send it through our publishpress.com contact form.

    Thread Starter Tim Nolte

    (@tnolte)

    @kevinb no it’s still an issue. However, what I found is that it only occurs when there are no revisions to review. So I actually do think it’s a problem with the Revisions plugin not properly doing empty results handling, or if not that then it’s Yoast SEO also not doing proper value checking.

    Kevin J

    (@iamkevinjohnson)

    I have this same issue yet today (Mar 3, 2023) – also looking forward to a Yoast update to resolve this.

    Thread Starter Tim Nolte

    (@tnolte)

    @iamkevinjohnson one thing that I did discover is that this issue seems only to happen when there are no revisions that need to be reviewed. So either Yoast SEO is making the assumption that posts exists and is not handling an empty array or something, or PublishPress Revisions is returned an empty array when it should be returning null perhaps. I still feel like this is a Yoast SEO issue. I’m finding that Yoast SEO seems to be hooking into more and more things. We also have found an issue where Yoast SEO data optimization causes issues with FacetWP. If we manually re-optimize the data then FacetWP facets start working again, or if we disable Yoast SEO. I am starting to question whether it is wise to keep using Yoast SEO because of how many things it is hooking into by default and causing site stability issues where it seems like it has no business hooking into.

    Thread Starter Tim Nolte

    (@tnolte)

    BYW, this issue shouldn’t be marked resolved because the issue was never resolved.

    Plugin Author Steve Burge

    (@stevejburge)

    @tnolte Thanks for the feedback. One thing that was noted earlier: this Free version of the plugin does not actually integrate with Yoast SEO. That’s in the Pro version.

    We are happy to help track down a bug if means the Free version of Revisions and Yoast can co-exist on the same site together.

    Thread Starter Tim Nolte

    (@tnolte)

    @stevejburge thanks for the reminder about free vs pro. I’m wondering though if others are reporting this if it is in fact only with the Pro version.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Fatal Out of Memory Error on Revisions Screen When Yoast SEO Active on Site’ is closed to new replies.