An error of type E_ERROR

  • Resolved IainPurdie

    (@iainpurdie)


    2 months, 4 weeks ago

    Hi! Running the latest version and twice since the last update I’ve had a site failure after saving / publishing a post which has triggered a scary “your site is broken / fatal error” error message. Fortunately on both occasions a page refresh has cleared it, so it’s temporary if panicky!

    I received an email on both occasions pointing at this plug-in as the culprit. The relevant text is as follows:

    WordPress caught an error with one of your plugins, Admin Menu Editor.
    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 6.9.1
    Active theme: Colinear Child (version 1.0.0)
    Current plugin: Admin Menu Editor (version 1.15)
    PHP version 8.3.30 Error Details

    An error of type E_ERROR was caused in line 2538 of the file [path redacted]/wordpress/wp-content/plugins/admin-menu-editor/includes/menu-editor-core.php. Error message: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes)

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Janis Elsts

    (@whiteshadow)

    2 months, 4 weeks ago

    That error usually means PHP ran out of memory. While Admin Menu Editor on its own shouldn’t use a lot of memory, if you already have a number of other active plugins, adding this one can be enough to push the site over the limit.

    I would recommend increasing the PHP memory limit as described here or here. Based on the error message, the current setting on your site is 128 MB, so try setting it to something higher than that, e.g. 256M.

    Thread Starter IainPurdie

    (@iainpurdie)

    2 months, 4 weeks ago

    Thanks, I’ll give that a blast. It just seems odd that it’s always (well… both times!) blaming this plugin, but I guess it could be that this is the last one in the list so the one which pushes the limit over the edge.

    Plugin Author Janis Elsts

    (@whiteshadow)

    2 months, 4 weeks ago

    Yes, in principle, this type of error could be triggered anywhere, so it is a bit suspicious that it’s the same plugin in both cases. But with only two examples, it could easily be a coincidence.

    Still, if it keeps happening, repeatedly, and especially if the file name/line number in the error message is always the same, that could indicate that there’s some kind of a bug.

    Thread Starter IainPurdie

    (@iainpurdie)

    2 months, 4 weeks ago

    Thanks, I’ve tried changing the ini file to bump me up to 256Mb. Let’s see what happens!

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.