Upgraded to 2.5; Dashboard Sez: “WordPress 2.3.3 is out of date!”

  • Resolved tulippad

    (@tulippad)


    16 years, 8 months ago

    So I upgraded to 2.5 tonight, or at least I thought I had… I followed the instructions, deleting things and not deleting things and uploading and then running upgrade.php. Everything went just fine, and, like the last seventeen times I upgraded WordPress, nothing seemed out of place…

    Until I logged in. The admin interface looked the same, and across the top of the dashboard was the notice that, and I quote, “A new version of WordPress is available! Please update now.”. At the bottom was:
    “Your WordPress 2.3.3 is out of date. Please update.”

    …Did I not just INSTALL the new one? I was pretty sure I had, because it was the only WordPress version I had downloaded to this machine.

    (Weirdly enough, when I went to the write-post page, I suddenly had an ‘Add tags here!’ text-entry box where I’d never had one before.)

    Has anyone else encountered this? What should/can I do to fix it?

    Things I have tried:
    – Deleting/overwriting EVERYTHING except the config file (I have backups/new versions of plugins/no extra super-duper customized files)
    – Deleting .htaccess (which took up a whopping 0K!)
    – Shift-reload

    Things I have NOT tried (yet):
    – clearing my browser’s cache (since I see the old dashboard and the software itself says I need to upgrade, I don’t think it would help)
    – making a new DB and doing a fresh install somewhere else to see what happens

    Thanks for reading this far!

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter tulippad

    (@tulippad)

    Okay, so I just tried doing a fresh install of WP 2.5 in a new directory. Aside from getting

    Warning: Cannot modify header information – headers already sent by (output started at /home/[redacted]/public_html/testobloggo/wp-config.php:1) in /home/[redacted]/public_html/testobloggo/wp-login.php on line 12

    Warning: Cannot modify header information – headers already sent by (output started at /home/[redacted]/public_html/testobloggo/wp-config.php:1) in /home/[redacted]/public_html/testobloggo/wp-login.php on line 24
    This Is Only A Test

    during the installation process, everything seemed to work just fine. Then I tried to login. I get those errors again, with the additional message that

    ERROR: WordPress requires Cookies but your browser does not support them or they are blocked.

    and my browser (the latest, non-beta version of FireFox) is set to accept ALL cookies! Off to try clearing the cache…

    And I don’t get that error when I log in to my main blog (the one that’s telling me I’m using 2.3.3, above).

    UPDATE:
    I just cleared out all of my ‘private data’ and tried to login to my fresh install — still no joy. It insists that cookies need to be enabled, despite the fact that no only do I have FireFox set to accept all cookies, I turned off AdBlock Plus and NoScript just in case.

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    Okay. Two problems, two answers.

    First problem: Double check and be sure that you uploaded ALL of the WordPress files when you upgraded. A lot of people use “Overwrite if newer” or something similar in their FTP client, and that’s not guaranteed to work. Don’t overwrite, delete the wp-admin and wp-includes directories entirely and then upload the new ones in their place.

    Second problem: Your wp-config.php file has a blank line or space or something at the top of the file (line 1). Can’t have that. Make sure the first thing in the file is <?php. If you used a text editor to edit the file, make sure that it saved it as ascii/plain text only, and not as a Unicode file. Saving as unicode puts in a little bit of text at the beginning of the file that you might not be able to see in the editor.

    Thread Starter tulippad

    (@tulippad)

    Otto — First Problem: Yes, yes, a thousand times YES, I deleted those two folders. I will try again, though, because Lord knows what’ll happen.

    Second: Weird! I’ll double-check on the file type.

    Thanks so much for the ideas, I really appreciate it.

    I noticed some hiccups when I tried using FF 1.0.7 in my admin panels, but they went away when I switched to FF 2.0.0.11

    And no, this isn’t an april fools joke.

    Thread Starter tulippad

    (@tulippad)

    Sam — Since I’ve got FF 2.0.0.13, it shouldn’t be a problem. Theoretically, anyhow.

    Thanks for the thought…

    UPDATE:
    – Once again deleted both wp-admin and wp-includes for my main installation; once more uploaded both files; once more logged in to see the same info.

    – fixed the login problem for the new install. File had been inadvertantly saved as UTF-8; saving as ANSI fixed it quickly and easily.

    However… When I logged in to the new, fresh, never-before-used install of 2.5, I had the SAME dashboard as 2.3.3, and the SAME messages that my copy of 2.3.3 is outta date and I need to upgrade. I am going to try reinstalling WP 2.5 from a freshly-downloaded .zip.

    Considering today’s date, I have wondered if this is all an elaborate joke. If it is, oh ha ha, you got me! I can has upgrade nao plz?

    If it isn’t, well… Gah! What am I doing wrong?

    have you made double sure to clear your browser cache? thats the only thing left i can think of…
    https://icanhascheezburger.com/2007/06/24/donut-worry/

    you’re welcome.

    I have both versions of FF in different folders. So I was able to go back and forth, the hiccupsare still there in 1.0.7.

    Have you tried looking at your dashboard in a different browser ?

    Hmm. Does your ISP cache web sites for ‘faster loading’ ?

    My former ISP, one reason I switched to cable modem, is they said a web site we went to often would be cached on the ISP’s server.

    Thread Starter tulippad

    (@tulippad)

    Sam —

    Hee! I love that picture.
    As for clearing the cache, I did try that — and I figured out part of what was wrong, at least with my fresh install. It turns out that when I unzipped the archive the first time around, the unzipping process got interrupted, so I had three copies of some of the WP files in the destination folder (i.e. index.php, index_1.php, index_2.php, etc)! After tossing the previous messy copy of WP into the recycle bin and uploading the index and other files to my testobloggo directory, my fresh install looks exactly right and works like a charm.

    Now, of course, since I deleted and reuploaded those same files for my main install, I have a new error:

    Fatal error: Unknown function: require_wp_db() in /home/[redacted]/public_html/blogstuff/wp-settings.php on line 204

    So, I did make progress… Kinda. Maybe it’s time to call in the kittens.

    Thread Starter tulippad

    (@tulippad)

    Woo-hoo! I FIXED IT!

    What I did:
    – deleted the wp-admin and wp-includes folders AGAIN
    – uploaded the same folders from my fresh d/l of WP2.5
    – Checked my main install again, got a different error
    – uploaded my old wp-settings file; checked; a different error!
    – deleted old wp-settings file; uploaded NEW wp-settings file
    – checked… Got a ‘You need to upgrade! Wanna do that now?’ message
    – upgraded…checked…
    – it worked! Woot!

    Thanks so much to everyone that suggested things to try! Have a great day!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Upgraded to 2.5; Dashboard Sez: “WordPress 2.3.3 is out of date!”’ is closed to new replies.