Upgraded to 2.6 & login.php not working

Make sure you have uploaded all the relevant files. It looks like your css files have not been uploaded.

After uploading everything, delete cookies + cache before logging in.

The Css files are all there. The blog looks fine before I log in – original posts and everything is still there.

https://scubadiving-blog.com/

It’s a different set of files for your main blog to the admin area.

Sorry, I didn’t realise you meant that mrmist. I checked the css files in the admin directory. I looked at them side by side, to compare, and they are all there. I also checked all the other files within “includes” directory and “admin” directory. Everything is there.

This is the third time I’ve gone through the upgrade process, deleting all files first, in admin and includes, the copying everything over again.

Each time I do the upgrade, I still get the same problem with the log in.

I haven’t been able to post on the blog for weeks.

Ok well the missing CSS should not prevent a log in anyway, so what actually happens when you attempt to log in?

i’ve seen this alot lately with several sites

people cant login with firefox, they have to use IE instead.. no idea why

same problem here.
Upgraded from 2.5 to 2.6.1.
IE6 works fine…
any idea why?

Found the solution:

https://your.url/wp-login.php?action=logout

and you can login again
??

I can’t log in from any of these browsers:

IE, Firefox, Flock, Netscape (I know it’s obsolete).

Logging out didn’t help isnochys, thanks.

I tried all the methods listed at this thread here:
https://www.ads-software.com/support/topic/189172?replies=43

I updated to 2.6.1 also.

My problem seems a little different from the others.

The actual wp_login.php is strange.

Here’s what happens for me when I attempt to log in.:

This URL is Not the same as the normal log in screen:
https://scubadiving-blog.com/wp-login.php

When I fill in my username and psswd, the URL displays like this:

https://scubadiving-blog.com/index.php/wp-login.php

and, because the “index.php” shows up as a directory which is impossible to have, I get an ERROR 404

Can someone please tell me which file causes that redirection and how I should fix it?

I have deleted .htaccess so it can’t be that which is redirecting.

Thanks very much in advance.

Julieanne

It has something to do with the index.php file – when I delete that file, the blog can’t be seen. I’m sure it also has something to do with the .htaccess file, but I can’t work out exactly what.

I’m writing this here, hoping that something triggers with someone else:-)

Thanks for all your messages:-)

Maybe you already tried all this, but anyway, just some ideas.

“Deactivate” all your plugins. Since you can’t access the Admin, just move your plugins to a different folder, temporarily. Then try it.

Were you running some plugin like Branded-Login, before?

Also you said you have reinstalled WP 2.6.1, already three times. From the same files? Maybe download WP again, and upload. Maybe a file got corrupted or something last time.

Also: After you upgraded, did you run the “yoursite/upgrade.php”?

Also: I agree it might have something to do with htaccess, you said you removed it? Maybe try putting a blank .htaccess in the folder?

IF you had access to your Admin, another thing to try is re-save the permalinks.

Thanks for your suggestions Dgold.

I don’t have any plugins in the plug in folder, so it’s not that.

The WP2.6.1 files can’t be corrupt because yesterday I uploaded the same files for a client, and her blog works perfectly.

I will try to put a blank .htaccess in the folder.

Regarding the permalinks, I think I can access the option to save them, from the database. So, that’s an idea.

Thanks to everyone who made suggestions.

I finally found the solution – it’s right here on the forums, I just had to hunt a lot to find it.

Here’s the thread
https://www.ads-software.com/support/topic/194159?replies=6

And, here’s the site that has the instructions:
https://www.tamba2.org.uk/wordpress/site-url/

The name of the URL and the siteurl in the wp_options table in the database was my problem

@julieannevz Thanks! I’ll give that a go, because it does sound like you and I seem to be having the same issue.