you didnt get all the files upgraded, specifically wp-includes/wp-db.php
Thanks, but after reuploading, I simply got another error:
Warning: require(/home/somethin/public_html/zonkered/wp-includes/shortcodes.php) [function.require]: failed to open stream: No such file or directory in /home/somethin/public_html/zonkered/wp-settings.php on line 277
Fatal error: require() [function.require]: Failed opening required ‘/home/somethin/public_html/zonkered/wp-includes/shortcodes.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/somethin/public_html/zonkered/wp-settings.php on line 277
I’ve uplooaded everything – twice.
nope, sorry. that ‘other’ error means that wp-includes/shortcodes.php hasnt been upgraded.
Delete everything inside wp-includes/
Upload all the new stuff.
I’ve uplooaded everything – twice.
Ive spent 4 years on this forum. You have no idea how many times Ive handled this question, and seen that answer?? I would be rich if I had a dollar for every …
—
and fwiw, you probably want to do the same thing for wp-admin/
if one directory is screwed up, chances are other stuff is, as well.
Okay, thanks for your help. I reuploaded wp-admin and wp-includes, and am no longer getting error messages, but I’m getting a repeat of the problem I had prior to upgrading – when I try to login, it just loops back to the login page. Doesn’t say the password is wrong, doesn’t give me any kind of error, just goes back to the login page and refuses to go to the wp-admin directory. Any ideas what this might be? I’ve cleared cache and I’m accepting cookies.
Sounds a bell 🙁 and it might even be worse.
Similar problem with only ONE of my blogs after upgrading from 2.2.3 to 2.6.3. The only way to get in was requesting a new password and use that.
problems arose with changing this generated passwordt to what I use normally: That fails because the response is said to be non-CGI-compliant:
...
profile.php (cgi_exe:phpwasd.exe) TRACKS:[WP-ADMIN]profile.php
-NOTICED-I-CGI, 5374617475733A203330320D0A582D506F77657265642D42 (2048 bytes) Status: 302..X-Powered-B
...
Status: 302..X-Powered-B – the dots stand for <CR><LF>. Since this is the only place where the problem occurs (other locations for Status 302 have no problem whatsoever) I guess there is something wrong in the PHP code, that “X-powered-B….” is added.
The server is set to NOT allow that.
I bypassed it by entering – as a string – the encrypted password I use in another WP blog, and I could login as ususal.
I guess this is caused by an error somewhere in the PHP code. Mine is a “non-standard” environment (no Linux or Windows), so it’s easiest to point to the environment that causes the problem. But since this is the only location in the whole package that I run into this problem, it’s not very likely to be the server to be in error.
