WordPress.org

Ready to get started?Download WordPress

Forums

Change from wp 1.2.2 to 1. 5 beta breaks (31 posts)

  1. ibn2deep
    Member
    Posted 9 years ago #

    Previous install was 1.2.2. It went in without a hiccup. Pulled its strings for a few days same result... worked flawlessly.

    Decided to up to the 1.5...snatched it for nightlys then dumped into dirs and hit the "upgrade.php" page and:

    Fatal error: Call to undefined function: __() in /www/xxx/xxxx/htdocs/blog/wp-admin/admin-functions.php on line 857

    I killed the dirs and database tables and did a fresh install of 1.5 and it installed without a hitch.

    Have no idea what happened just wanted to throw that seed out there incase it reared its head for others.

  2. BAKSHI
    Member
    Posted 9 years ago #

    the same happened with me. how can this be fixed?

  3. tcloer
    Member
    Posted 9 years ago #

    I'm getting the same error. No solution yet, as it seems. I will try to find a newer (or maybe older) version of the file in the CVS and see if i can get that one to work...

  4. TechGnome
    Moderator
    Posted 9 years ago #

    When I upgraded this is how I did it and it seems to have worked:
    1) Made a backup of the database.
    2) Backed up the files from off of the web server
    3) Deleted all files & folders from the web site -left now with an empty web site
    4) Uploaded all the new files from the install.
    5) Ran wp-admin/upgrade.php
    6) Uploaded new template files
    7) browsed to the website, and verified the new site comes up.
    8) Made sure I could login to the admin area
    9) Double checked all my settings & made sure all was OK

    Tg

  5. NuclearMoose
    Member
    Posted 9 years ago #

    It's recommended that you DELETE your files on your server, not just copy over them using FTP. It is a known issue that on occasion, files do not get replaced properly, so it's always better to clean out the files first.

  6. tcloer
    Member
    Posted 9 years ago #

    Well, i have just deleted everything from my server except for wp-config.php, uploaded the 1.5b1 stuff, called /wp-admin/upgrade.php -- et voila, still the same fatal error. So thanks for your tips, but this was NOT it.

  7. Anavy
    Member
    Posted 9 years ago #

    I'm having the same problem with upgrading from WP122 to WP15b1.

  8. tcloer
    Member
    Posted 9 years ago #

    I have reported the bug to the Mosquito bugtracker and they're working on it already...

  9. danweasel
    Member
    Posted 9 years ago #

    I had this problem but it dissappeared with the latest nightly.

  10. tcloer
    Member
    Posted 9 years ago #

    What's the "latest" - 01-07 or 01-06? I tried it four times with 01-06 yesterday and don't wanna do it again wih that one...

  11. struan
    Member
    Posted 9 years ago #

    1.2->nightly (2005-01-07) on Fedora Core 2.
    All I get for upgrade.php is a blank page. Something is working, since install.php tells me wp is already installed. I tried googling, found that the default had display_errors in /etc/php.ini turned off. Turned it on, but still no output. Any hints?

  12. scooter
    Member
    Posted 9 years ago #

    I'm having the same error. I deleted all of my 1.2.1 install, and then put all of the nightly. blank upgrade.php, and same fatal error.

    any ideas?

  13. Mark (podz)
    Support Maven
    Posted 9 years ago #

    Scooter: details, details ...... what ftp client are you using ? Is your name linked to the wp location ? Was everything working before you tried the upgrade ? Have you deleted and re-tried ?

  14. NuclearMoose
    Member
    Posted 9 years ago #

    I suppose this is proof-positive that one wants to be careful moving from a stable version to a beta. It's something that people should consider when wanting to move their production sites to a beta version. It's often been said that it's best to try this on a test site first, and then do the move.

  15. danweasel
    Member
    Posted 9 years ago #

    It gave me the error with admin-functions on 1-05, so I mowed through several older nightlies before trying 1-06 again. (Each time deleting the various wp files.) 1-06 worked for me.

    I was very careful to backup everything before all that though.

  16. _Javier_
    Member
    Posted 9 years ago #

    My procedure to restore my database from Mingus (1.2.2) to the latest available version:

    1) Mingus is working fine
    2) Backup and another recommended stuff ;)
    3) Download nightile 1-04 and install it
    4) run the upgrade.php
    5) erase the 1-04 wordpress directory
    6) checkout the latest beta version

    Running the upgrade.php from 1-04 upgrade the database. In that way beta-1 don't crash.

    That's all!

  17. tcloer
    Member
    Posted 9 years ago #

    Great - this worked for me. So http://www.teezeh.info is now running WP 1.5b1 as well. Thanks a lot...

  18. scooter
    Member
    Posted 9 years ago #

    I deleted all my files, and installed the Jan 4th daily. Had to go grab the kubrick image files from another daily (they were missing) and it worked fine. :D

  19. jowe
    Member
    Posted 9 years ago #

    I'm having this problem with 1-07 from 1.2.2, same error, "Fatal error: Call to undefined function: __() in /xxx/wordpress/wp-admin/admin-functions.php on line 857" I suppose I'll try the 1-04 build and see if it will work for me, since that's what seems to be the latest working one for upgrading from 1.2.2.

    EDIT:This worked, though I recieved an error "Warning: Invalid argument supplied for foreach() in /home/b2l0740/public_html/wordpress/wp-settings.php on line 97" which I'll probably figure out how to fix and hopefully be fine with the upgrade.

  20. aregon23
    Member
    Posted 9 years ago #

    Faced the same problem, with the upgrade failing on line 857 in te admin-functions.php. I tried using nightly builds '2005-01-18', '2005-01-17' & '2005-01-14'. Then gave up searched the forums and found scooter's post who got build '2005-01-04' to work on the upgrade. So gave it a shot, the Kubrik images were missing so uploaded those and another theme, and it worked after changing the presentation.

  21. 7milesdown
    Member
    Posted 9 years ago #

    I just backed up my database using phpmyadmin, deleted the database after the backup, deleted all the files on my server, and uploaded a fresh beta. Then deleted the new database and plugged in the old one in. Worked great! :)

  22. NuclearMoose
    Member
    Posted 9 years ago #

    Just a sidebar comment here...but I don't think that moving from a stable release to a beta should be described as "upgrading".

  23. 7milesdown
    Member
    Posted 9 years ago #

    I agree NM. haha. Good Stuff. I love the new system though. I dont think I could go back to the stable release.

  24. limeshurbet
    Member
    Posted 9 years ago #

    7Mile - thanks! followed your steps and was finally able to get something past 2005.01.04 running. 2005.01.18 running quite nicely!

  25. JPigford
    Member
    Posted 9 years ago #

    I noticed 7miles down just deleted the new database and then used his old one. I thought that 1.5 uses a new database setup...maybe I'm wrong though.

    And, I to am getting the error on line 857. I deleted ALL the files except for wp-config.php. Meaning the the only things left over from the previous version would be wp-config.php and the database. I then uploaded the new version, minus wp-config.php, and am getting this error: Fatal error: Call to undefined function: __() in /home/**********/public_html/dev/wp-admin/admin-functions.php on line 857

  26. Ryan Boren
    WordPress Dev
    Posted 9 years ago #

    This is a bug that should now be fixed in the latest nightlies.

    If you still have problems, please add a note to this bug.

  27. JPigford
    Member
    Posted 9 years ago #

    Yeah, I'm getting the problem from the most recent build (1-20-2005)

  28. Ryan Boren
    WordPress Dev
    Posted 9 years ago #

    Does your copy of upgrade-functions.php have this line:

    require_once(dirname(__FILE__) . '/admin-functions.php');

    That line should no longer be there in the newest version.

  29. JPigford
    Member
    Posted 9 years ago #

    It did have that line and I removed it...but that should be the problem as I get the error no matter what file I try to access...index.php, upgrade.php...any and all pages give me that error.

    http://dev.theappleblog.com/

  30. JPigford
    Member
    Posted 9 years ago #

    Anybody have any update on this issue?

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.