Fatal Error: Memory Exhausted upgrading to WP 6.2

In order to fix the error, you’ll need to increase the maximum allowed memory by reaching out to your web hosting provider. If you’re familiar with server management, you can change the memory_limit value directly from the php.ini file

As I said above I changed my memory limit up to ‘256M’ in WP-config.php at my Siteground host site?from ‘128M’. This did not solve the problem. Are you saying I need to ask my host server for more?

I don’t know how to change the memory_limit value directly from the php.ini file. Is this any different?

I’m not really an expert here.

Thanks for getting back. I find losing my website with a WP upgrade or any other forced upgrade rather frightening.

Tony

I went to siteground and looked up their memory limit and changed it to 512M but with no success!

Tony

I’ve just fixed this with help from Siteground support. Go to WordPress > Autoupdate in your Site Tools and click on Last Backup – Restore. This will take your site back to 6.1.1 When the backup is restored click on Autoupdate again and select to skip next update so it won’t autoupdate again until there is another update that’s not 6.2.

Hope this helps.

If you’re on SiteGround also and know that it’s the 6.2 update causing the issue BUT don’t want to restore, they can roll it back with the core file updated. They’re back logged for good 30-60 minutes I’m assuming due to this 6.2 update causing issues for so many.

Otherwise, yes, you’ll need to restore from the Backup section to the previous save. Just make sure you disable the automatic update in wp-config.php file.

And add:

define( ‘WP_AUTO_UPDATE_CORE’, false );

After the “happy publishing”

Hi Thank you for the advice in the above two. I’m in Australia because of the time difference I’m just early morning. I’m sure it is 6.2 causing the problems and would like to roll it back to 6.1. I updated manually. I don’t have auto update on for WordPress turned on and when I go to Auto update on Siteground I can’t find any backup or restore. Is there another way around this?

I’m not sure what 30-60 minutes means as this has been going on for more than 13 hours.

I do have updraft plus which made a copy of the site not that long ago. Though I don’t know how to restore it. That is a possibility but I would prefer to go back to 6.1 through Siteground if at all possible.

Kind regards

Tony

Hi I just read through the updraft plus instructions for a manual upload (when you can’t access your WP admin) and it seems rather scary and final and I’m not sure that it is within my competency. So that I am hoping that there is some other solution that you can offer me to restore my site.

Kind regards Tony

Hi Tony,

In your Site Tools under Security you should have backups that are made by Siteground. Go back a few days and restore from the backup there.

Hi to you all

Thanks you very much for this help. I was all at sea!

I wish I had known that Siteground does daily auto back-ups of my site and how to access them. I am back on WP 6.1.1 and happy!

I’ll wait for a new 6.2.x upgrade before updating my site.

Now much wiser but also happier too.

Thanks again

All the best

Tony

Is this really a solution? Won’t 6.2.x be pushing the same updates thru and cause the same problem? I also cannot upgrade. Getting both memory and timeout errors (godaddy). Have already upped WP memory limit. also tried removing plugins to no avail. Is this happening to many sites? … and has anyone found the reason it’s happening to so many sites? Thanks in advance for any info.

• This reply was modified 1 year, 7 months ago by ramco5739.

A nice question ramco5739! I am always concerned when I upgrade to another version of WordPress or even a major plug-in that something will go wrong and even worse that I won’t find out about it initially.

For example, with a Jetpack upgrade I lost my Sitemaps and indexing on Google and didn’t find out about it for three weeks. This version of upgrade to WordPress 6.2 seems to have cause major problems to a lot of users but it would be nice to know how many.

One nice consequence of such scary failures, is that you learn more about what can go wrong. I don’t panic as much as I once would have.

The problem is still here with 6.3.x …