WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Fatal error message after upgrading to 3.5 (6 posts)

  1. susie.Q
    Member
    Posted 1 year ago #

    I just updated to 3.5 and have gotten the following fatal error message:

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 384 bytes)

    I cannot access my site or the dashboard. Is it safe to try the downgrade via

    http://etuts.org/manually-downgrade-wordpress/

    without deactivating the plugins? The only other thing I can think of would be to copy the plugin folder to my desktop and them delete it from the directory and proceed.

    I have a practice site where I try things out before doing it on my main site. This upgrade worked fine on the practice site, but I don't have as many plugins installed and there are hardly any posts.

    It's not clear if this means I have a plugin conflict.

    Also, I backed up my entire site before I upgraded. Will restoring from this backup return me to 3.4.2?

  2. Dion Hulse
    WordPress Dev
    Posted 1 year ago #

    Also, I backed up my entire site before I upgraded. Will restoring from this backup return me to 3.4.2?

    Most likely, that would work fine, but as we don't know how you've backed it up, we can't tell you for sure.

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 384 bytes)

    That error message is telling us that WordPress is exceeding 128MB of memory, that's a LOT of memory usage, at least 5x the normal amount.. It sounds like you have a plugin which is coded very badly for you to get to that point, I'd suggest you consider disabling your plugins to find the culprit before throwing the towel in and going back to 3.4.

    To work out which plugin is causing the problem, you can open your wp-content/plugins/ folder in a FTP application, and rename the plugin directories until you find the problem one. For example, you'd rename 'plugin-name' to 'plugin-name-old' and then see if your site will load. Eventually you'll find the one causing the problems.

  3. imtideen
    Member
    Posted 1 year ago #

    I just updated to version 3.5 and got following error message. Any suggestions please?

    Warning: Missing argument 2 for wpdb::prepare(), called in /home/imtideen/public_html/passivemasters.com/wp-content/plugins/wp-super-edit/wp-super-edit.core.class.php on line 114 and defined in /home/imtideen/public_html/passivemasters.com/wp-includes/wp-db.php on line 990

  4. elvis1234
    Member
    Posted 1 year ago #

    Hi Susie,

    Maybe you could ask your hosting provider if they can see what processes are taking much memory?

  5. susie.Q
    Member
    Posted 1 year ago #

    I did what Dion above suggested and found the plugin that was causing the problem. I have gotten rid of that and everything seems to be working OK. The offending plugin was front end users but I fail to see why that would increase the memory.

    I am still antsy about keeping the 3.5 update in view of all the other bugs that are being reported.

    My host was going to install the back-up but I have but that on hold for the time being.

  6. susie.Q
    Member
    Posted 1 year ago #

    When I am working in WP to post and the like, my Cpanel shows that my memory usage is 462 KB. Assuming I am converting correctly, that would be equivalent to 0.462 MB which should be well within the 128MB. Is that correct and can I assume the problem was in fact the front end users plugin?

    I have no computer knowledge so I apologize for having to ask basic questions. Google has been my friend and I am making progress but I still find all of this daunting.

    Thank you to everyone for your patience and help. It is much appreciated.

Topic Closed

This topic has been closed to new replies.

About this Topic