There will be no resolution until:
a) The fact that it's actually an issue is verified.
b) The cause is determined.
c) A patch is created for it.
None of these has occurred yet.
Upgraded to WP 2.6 and can't access wp-admin area (192 posts)
-
-
Anonymous
Posted 1 year ago #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)
-
doc_holiday
Posted 1 year ago #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.
-
Posted 1 year ago #I have removed all of my plugins.
-
Well doc you url is actually
or
http://www.donovanpalmer.com/wp-admin
with the www.
And it seems you have errors in your upgrade - so its not clean.
-
schajee
Posted 1 year ago #Sorry about the Cookie madness earlier.... forgot to mention that it was at home on a clean install.
-
Posted 1 year ago #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.
-
Anonymous
Posted 1 year ago #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 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]. -
bevived
Posted 1 year ago #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. -
Posted 1 year ago #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.
-
Posted 1 year ago #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. -
Anonymous
Posted 1 year ago #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: http://.../wp-admin/post.php?action=edit&post=55Don'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.
-
Posted 1 year ago #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?
-
Posted 1 year ago #Followed bevive's advice and uploaded yet again; now I can view the site once more, but I'm back to the blank login page again.
Going to call it a day for now, I have a bottle of Glenfiddich calling my name.
-
_ck_
Posted 1 year ago #rawalex, no the browser is doing what it's told: it's being told to create a cookie with the same name but another path. To the browser that is a separate cookie and doesn't overwrite the old one, though maybe some browsers handle it differently.
I don't see how anyone successfully logs in without manually deleting the old cookie. Recycling the old cookie name for a new use was not the greatest idea. I bet thousands of people are having this problem after upgrade.
-
gremlinchief
Posted 1 year ago #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.
Exact same thing happened here, downloaded the latest files of WordPress onto my server and unzipped them straight into the wordpress directory - blank pages all over. Once I redownloaded the package and unzipped it a second time it worked. The file size on the first download (even though its from the EXACT SAME location) is actually a few kilobytes bigger.
Discrepancies in the wordpress download server? Not sure, but I'm not having any more issues.
-
I've upgraded to 2.6 several times and never encountered this. Still trying to figure out why...
Not sure if somebody already mentioned that, but all newer browsers have something like "Clear private data" that opens a list of places to clean.
In Firefox, Opera and IE7 it's on the Tools menu, in Safari - on the Edit menu. Cookies, cache, etc. can easily be deleted from there.
-
azaozz, it could be any number of things, from the method used to install the upgrade to the server config, version of php, apache, etc... it could also be how long people keep cookies for, example, or if they actually log out of the wordpress admin area as opposed to just surfing away, etc. Some people may be using saved passwords, others might be typing them in... different browser plugins, etc.
Gremlinchief, that is interesting, you may have gotten a different build that has minor changes in it the second time around, fixing something small and obvous, example. I don't know the build schedual. if you kept both, you could always do a comparison to see.
-
Seems like most of the issues come back to cookies which was my problem, not really a problem since it was so simple.
Thanks a ton Otto42! I don't know how you put up with this stuff regularly, but you are doing a fantastic job. This community is so much better for having you around.
-
Anonymous
Posted 1 year ago #thank you bunches!
-
Anonymous
Posted 1 year ago #guys!
how do i figure out what my blog's PATH is?
that's my site. can someone PLEASE let me know, because i've fucked up my .php thing trying to fix this:
@define('ADMIN_COOKIE_PATH', '/');
that, my friends, is the one hitter quitter that has made my K2 sidebar manager useless. like chris webber in the last few seasons.
somebody help me. modi@dctobc.com. i appreciate it greatly.
-
Rori
Posted 1 year ago #Well, I think I will wait to upgrade for now since I just did a MAJOR redesign and I am afraid *makes chicken noises*, but I just wanted to give kudos to Otto42 for all the help he gives.
-
Well, I think I will wait to upgrade for now since I just did a MAJOR redesign and I am afraid *makes chicken noises*, but I just wanted to give kudos to Otto42 for all the help he gives.
There is no need to be fearful. If you take a backup of your database (e.g. through PhPMysqlAdmin or whatever) and take a copy of your web files, then if your upgrade doesn't work for some reason that you cannot fix, all you need to do is restore your backup, and replace the files.
-
laowaichinese
Posted 1 year ago #I have the same problem and, yes, my blog is on a subdomain. I tried re-uploading all the files as per Otto42's instructions. But alas, I still can't log in as admin through the wp-admin page.
It's broken in FireFox 3.0 and IE7.
But in IE7 at least it remembers that I'm logged in and I can go in by some of these "back doors" that have been mentioned (like clicking on the name "Admin" in a comment).
-
If you are able to get in via IE and not FF, then it suggests you have not cleared your cookies completely in firefox.
-
Anonymous
Posted 1 year ago #Hi,
I have the same problem. It is not resolved by erasing all the cookies.
After multiple re-installation, I figure out how to access to my admin.
Access to http://myblog.co/wp-admin/ does not allow to log in. It is redirected to :
http://myblog.com/wp-login.php?redirect_to=http://myblog.com/myfolder/wp-admin/"myfolder" is where all my blog/wordpress files are on my server root.
In order to log in, I have to go here :
http://myblog.com/wp-login.phpAnd now, I can log in !!
Anyway, it is just another way to access to my admin. I'd like to have the possibility to log in via /wp-admin/ again. For now, it is not working. For me, it's a wordpress 2.6 bug.
-
Posted 1 year ago #Ok, back at it today with the same results.
1) Downloaded and extracted a new copy of the 2.6 zip file (no errors).
2) Re-uploaded files again - transfer log shows no errors. Removed all plugins from the content folder.
3) Cleared all IE cash (cookies, passwords, etc.).
4) Can view site, try to log in, goes to blank wp-login after entering login and password.
5) Try forget password, receive conf. e-mail, click link goes to blank wp-login page.
6) Tried replacing the wp-login.php with the one from 2.5.1, same result.I've made sure my siteurl is correct vs. the url I'm using to log in. I enter an invalid user name it tells me. If I enter a valid or invalid password it just goes to the blank wp-login page.
Any other suggestions?
Topic Closed
This topic has been closed to new replies.
