Upgraded to WP 2.6 and can’t access wp-admin area

Thanks CK,

But in all honesty, I would rather wait for
the developers/coders of WordPress to
make a statement and see what they
suggest is the best course.

I can’t find any “official” statement
from WordPress on this site that acknowledges
this issue, so I can only hope that whoever
runs this joint is pouring over lines of code
as I write this, trying to isolate and resolve
the problem.

Kaufmannn, I think you will find Otto42 is a moderator and “runs this joint”

As for problems with upgrading, well simply check and double that you have uploaded everything – do something for youself by creating a separte install directory (clean 2.6) and switch over to that if it works (which is what I always do when doing upgrades)

I have uploaded everything clean. I can’t get into the admin interface any more and blog site is empty. I really don’t want to roll this back to 2.5 if I can help it. How can I provide information to help the diagnosis of this problem?

Whats your site url doc?

In fact another person with the same problem as you had an issue with a plugin in the end – you might try removing all your plugins from the plugins folder and trying then to login.

https://donovanpalmer.com

I have removed all of my plugins.

Well doc you url is actually

https://www.donovanpalmer.com

or

https://www.donovanpalmer.com/wp-admin

with the www.

And it seems you have errors in your upgrade – so its not clean.

Sorry about the Cookie madness earlier…. forgot to mention that it was at home on a clean install.

Well, I didn’t have errors until I started trouble shooting. The interesting thing about this whole thing is that I don’t upload my wordpress files one at a time. I upload the whole zip archive and then unzip them on the server. This in theory should prevent errors with uploading.

Now that I have done this a third time, everything is mysteriously working. Could it be my hosting provider has some new problem with unzipping files on the server? This would be a first!

Anyhow problem solved. I’m still not sure what went wrong.

I deleted the whole of WP folder except for content/uploads. Re-re-re-uploaded the new version. Took my backed-up config and added the new keys to it and uploaded it. Ran the upgrade.php and got a bunch of PHP script at the top, but it said the database was fine. Click the “ok” button on that page and went to home page and now it’s just displaying PHP code at the top of the page:

of * the taxonomies with links to the taxonomy and name. * * @since 2.6 * * @param int $post Optional. Post ID or will use Global Post ID (in loop). * @return array */ function get_the_taxonomies($post = 0) { if ( is_int($post) ) $post =& get_post($post); elseif ( !is_object($post) ) $post =& $GLOBALS['post']; $taxonomies = array(); if ( !$post ) return $taxonomies; $template = apply_filters('taxonomy_template', '%s: %l.'); foreach ( get_object_taxonomies($post) as $taxonomy ) { $t = (array) get_taxonomy($taxonomy); if ( empty($t['label']) ) $t['label'] = $taxonomy; if ( empty($t['args']) ) $t['args'] = array(); if ( empty($t['template']) ) $t['template'] = $template; $terms = get_object_term_cache($post->ID, $taxonomy); if ( empty($terms) ) $terms = wp_get_object_terms($post->ID, $taxonomy, $t['args']); $links = array(); foreach ( $terms as $term ) $links[] = "$term->name"; if ( $links ) $taxonomies[$taxonomy] = wp_sprintf($t['template'], $t['label'], $links, $terms); } return $taxonomies; } /** * Retrieve all taxonomies of a post with just the names. * * @since 2.6 * @uses get_object_taxonomies() * * @param int $post Optional. Post ID * @return array */ function get_post_taxonomies($post = 0) { $post =& get_post($post); return get_object_taxonomies($post); } ?>

Not much better than just getting a blank page. The URL is https://www.thedailybizarre.com and I’m open to any suggestions to help diagnose this =/
[Edit – Forget to mention I cleared all cookies and removed all plugin files before I went to the upgrade.php script].

I have the same problem, that I cannot log in. It just keeps taking me back to the log in page. I’m going to try to downgrade back to 2.5.1 now.
I hope this bug is solved, to me it is pretty certain it is one, seeing as so many people seem to be experiencing the same issue.
I have been using WP for three years now, I have done many upgrades since, and never had problems like this.

I already tried that, couldn’t get that to work either. Just kept sending me to the upgrade.php page (which was blank) no matter what script I tried to run in the wp-admin.

I’m out of ideas at this point short of creating a brand new clean install and attempting to restore just the posts table back into the SQL file.

Okay, I just tried it again, I re-uploaded wp-admin and wp-includes and deleted all cookies for my site as well as the cache and that worked. I can now log in. Hooray. Now I hope I don’t run into any more issues after I post for the first time on 2.6.
The wp-upgrade.php had already worked before though (it had said that the upgrade was successful), all it did for me was keep sending me to the login page.

The most common cause of a blank screen at any stage in the process, if your source view shows empty, is that PHP aborted during its run without dumping buffers. During software upgrades, this is usually due to one of two reasons:

1) An incomplete transfer of the requisite files. Don’t insist that you’re certain that didn’t happen, even if it’s from a command like svn or cp that shouldn’t fail; you’re not certain until you’ve checked.

2) PHP has run out of some resource, typically RAM.

In both cases, you can figure out which by checking your apache logs. On windows, go to the Windows Event Viewer. On unix, this may live in a variety of places; most common is shared hosting by cpanel/plesk, where you can get it in your control panel, or to just look in /var/logs/ .

If it’s #1, you’re likely to see something like this in logs (this is from my site, which just suffered this problem and was quickly fixed) :

[Tue Jul 15 18:45:28 2008] [error] [client 24.117...] PHP Fatal error: Call to undefined function force_ssl_admin() in /var/www/html/wp-settings.php on line 390, referer: https://.../wp-admin/post.php?action=edit&post=55

Don’t worry if that undefined function has a different name or a different referrer, or whatever; that’s how you track down missing code, and missing code means some file didn’t get updated.

This can also be found at its home on my blog.

Oh, it can also be a broken install of mod_security, by the way.

Actually, I am thinking that you might want to look at the code that decides if someone is actually logged in or not. I think the cookie duplication may in fact come from other pages setting or adding older style cookies on the way around… or some other similar problem.

otto, just because you cannot entirely reproduce a problem does not make it disappear. The issue is clearly common to many upgraded blogs, so let’s not just say “nothing to see”. I think the programmer types need to start looking at that code and seeing what the differences are from the previous version, I am sure that they will see something. Waiting for someone else to run through it all and point out the problem could take a while, none of the rest of us are intimately involved in the creation of the code, now are we?