500 Error on wp-admin after upgrade
This happened with one of our individual installs and it’s happened before (but I forgot the solution) so I’m writing it down.
After the upgrade to 4.7.1, the front of the sight still worked but attempts to get to wp-admin failed with a 500 error and the URL was redirecting to something with upgrade.php? in the URL.
Change the name of the plugin folder (I just prepend an underscore).
Revisit your login URL.
Run the database upgrade as prompted.
You should now be in the admin zone.
Fix your plugin folder name.
Easy but also easy to forget.
So here’s the proof of concept page for those who just want the idea and know how to change things already. It’s a great way to let students quickly and easily build an interactive online comic book story or display their art work. I really like the potential. I’m documenting some process here in hopes of giving people who care how I end up where I end up an idea of the path I traveled. I saw a tweet and ended up at the site below. I liked the way it looked so I noted the reference to the theme at the bottom right. That URL led me to the designer’s homepage but I was either too impatient or too lazy to find the theme there. I backed out and did a search via google for ipseity theme and end up where I want (which is here). However it looked like this when I installed it- which is fine and good but not what I wanted. I liked the clean, white version that had started me on this journey. I’ve now have two options. Option One One, I download the css from the other page and replace it. To do that I go back to the original site. I click view page source (in firefox) I search for cssand find […]
If you’ve got a site running on HTTPS and you try to throw in some HTTP content, the browser gets nervous. If you’ve recently made a shift to HTTPS you might notice content that was successfully embedded disappearing. If you look in the browser (right click>inspect element in Chrome), you’ll see an error like the one above. What you want in this scenario is protocol relative URLS . . . essentially a URL without the leading http/https. That lets the page load via the one protocol that matches (assuming it exists- some sites won’t supply HTTPS options).Reading more about it, it seems forcing the HTTPS connection where available is encouraged. I’ll think about that more later. I ran into this problem with files we uploaded via Gravity Forms prior to the switch to HTTPS. There are a number of ways to deal with this (including search/replace at the database level) but we’re under a very heavy load at the moment and I just needed a quick fix. This solution will also allow people to do whatever they want on an ongoing basis better than a database response. This tiny little filter plugin is the result. All it does is use PHP’s preg_replace (regex) function to find any instances of HTTP or HTTPS (capital or lowercase) and remove them. I’m still […]