I just tried to upgrade WordPress to 2.5, and the whole blog broke; when I got it half fixed, I couldn’t login as admin any more and instead got the following error – and here’s how to fix it:
\n<\/p>\n
The page isn’t redirecting properly
\nFirefox has detected that the server is redirecting the request for this address in a way that will never complete.
\n * This problem can sometimes be caused by disabling or refusing to accept
\n cookies.<\/p><\/blockquote>\nNote: Microsoft Internet Explorer 7 is still a truly crap web browser, and instead of giving a helpful error message, it just … crashes. So, if you’re using MSIE and your browser crashed trying to login to wordpress, you now know why…<\/p>\n
Anyway, on to the solution:<\/p>\n
“I use the admin-ssl plugin to secure my WordPress admin area, but unfortunately changes in WP 2.5 broke it.”<\/p>\n
Yes, folks, anyone sane enough to try and prevent hackers stealing their blog passwords, and who therefore installed admin-ssl, will now potentially find themselves locked out of their own blog. Fortunately, the lovely bengreen has also provided a fix (which WORKS!).<\/p>\n
Steps to fix (for the truly panicked \/ stressed \/ confused):<\/p>\n
\n
- SSH to your server, go to the wordpress directory, then
cd wp-content\/plugins<\/code><\/li>\n- delete the old, broken, admin-ssl:
rm admin-ssl.php<\/code><\/li>\n- download the new admin-ssl and save it to this directory (I prefer to do it direct from the commandline using lynx, if you have lynx installed): download is here<\/a> (that’s version 0.67, there may be a newer one by now, you can check on bengreen’s blog)<\/li>\n
- Go back to your admin pages and login – should Just Work (because wordpress is very good at instantly picking up admin changes)<\/li>\n
- Go to the “Plugins” page from the navbar, and check that you have the new Admin-SSL enabled, otherwise your blog is insecure once again<\/li>\n<\/ol>\n
And for the cause:<\/p>\n