Indeed I find a wget script i used in 2.5.1 to login to admin area first then execute directly wp-o-matic, does not work anymore.
I do receive the cookie, yet when i load that cookie in wget to access other admin areas i get redirected to the login page.
Update doesn’t even work with me. I tried updateding 2.5.1 to 2.6, and I only got blank page, nothing happens. I had to revert all files to older 2.5.1 version.
same problem here. login problem.
yup, cleared my cookies for my particular site and now can login via FF 301
The new plugin system is great!!!!!
After the upgrade I was also unable to login with Firefox (my usual browser) but could get in fine with IE. I deleted all the WP cookies for the domain in question in Firefox and was then able to login. I wonder if the new security keys have anything to do with this?
define(‘AUTH_KEY’, ‘…’);
define(‘SECURE_AUTH_KEY’, ‘…’);
define(‘LOGGED_IN_KEY’, ‘…’);
749718
I’m wondering the same thing, although I’m using the latest version of the wp-config.php file with all these set up and nothing’s working for me. What a pain in the ass…
Have tried three different browsers to FireFox, cleared all caches and still can’t get logged in!
I have the same problem. Cant log in with any browser. Apparently it was released ahead of schedule because it wasn’t ready 🙁 Like I have nothing better to do with my time then to beta test a unworking upgrade
I am in the same boat. Blog works, password reset works, ADMIN-SSL works, I cannot login. It takes the password but then drops me back to the login screen. 🙁
CLEAR YOUR BROWSER COOKIES.
This is the first step. It will likely fix any cookie related issues you may be having.
Yes, cookie handling changed in 2.6. The “Please log in again.” message is it telling you that your cookies are expired and it’s trying to reset them. But, if that is not working for whatever reason, then you will get the message repeatedly.
Clearing your cookies and logging in to your CORRECT site (www vs. non-www, for example) will probably fix the issue.
I am wondering if the ADMIN-SSL plugin is killing things as well. I have cleared cookies and verified the site name and still have no luck.
Any plugin that screws with the SSL may be broken as of 2.6, which now supports SSL in the admin section natively.
Remove the plugin. You can force admin SSL in 2.6 by adding this code to the wp-config.php:
define('FORCE_SSL_ADMIN', true);
You can also force SSL for the login with this:
define('FORCE_SSL_LOGIN', true);
See this post for more info:
http://boren.nu/archives/2008/07/14/ssl-and-cookies-in-wordpress-26/
Otto42, it’s not just cookies either.
It’s a real problem within the 2.6 changes.
@_ck_: Unless you can tell me where this “real problem” is, then I’m really not interested in speculation.
The truth of the matter is that people with unusual setups will have issues with some of these changes. The problem is not with the changes, the problem is with the setups. Some setups may need to be altered slightly. Especially with people using older methods like the “admin ssl” thing.
Otto42 – Can I just remove the plugin by deleting it from the plugins directory? I cannot do it the “normal” way as I cannot login to my admin panels. Thanks for the help.
