4.5.3 Crashed My Admin
-
Just upgraded to 4.5.3 after resolving some major major issues with excessive unused plugin database tables and other things that had my admin at a crawl.
Unfortunately, I had update automatically activated and this morning I wake up and 4.5.3 was auto installed.
I got the email notification and thought, “oh no, this can either mean some bugs were fixed, or that I’m right back to a non-working admin”.
Guess what? It was the latter thought.
I got in VERY slowly initially, so I took it upon myself to optimize the database using RVG Optimize Database plugin and then using /wp-admin/maint/repair.php after as a safety precaution.
repair.php claimed all databases were already optimized and weren’t in need of repair.
Tried going back a few pages to get back to my dashboard, and boom 500 error.
Admin is fully crashed now and can’t get it up. Front end of the site works fine though.
I know I can disable plugins using FTP. Disable the .htaccess. Blah blah blah.
I’m actually not worried at all because I know I can fix it, and then downgrade if necessary back to 4.5.2.
My issue though is why would a simple wordpress upgrade with bug fixes unrelated to anything I had going on, suddenly bust up my admin?
I was having memory issues before alongside other things, so what, does that mean that 4.5.3 is requiring even MORE admin memory to operate smoothly?
If I set my Max over 4095M then it doesn’t register and kicks it to default 256M and that is no where NEAR enough. I will start getting fatal memory errors and that how I know part of this is a memory issue and throwing more memory at it isn’t the best way to resolve it – I know that too. However, why does WP continually release new versions that are requiring more and more and more and more memory to operate.
I can tell this is the case with 4.5.3 because why else would a super fast admin panel suddenly start crashing again like it was right back to where it was before I solved all the memory issues I found without throwing too much memory at it as a resolution, but instead fixing code and such to reduce the issues before adding more memory to the admin limit as a safety net. Guess it’s back to 4.5.2. Not sure what else to say about this…
- The topic ‘4.5.3 Crashed My Admin’ is closed to new replies.