Change from wp 1.2.2 to 1. 5 beta breaks

ibn2deep
(@ibn2deep)

19 years, 3 months 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.

Viewing 15 replies - 16 through 30 (of 30 total)

← 1 2

tcloer
(@tcloer)

19 years, 3 months ago

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

scooter
(@scooter)

19 years, 3 months 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. 😀

jowe
(@jowe)

19 years, 3 months 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.

aregon23
(@aregon23)

19 years, 3 months 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.

7milesdown
(@7milesdown)

19 years, 3 months 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! 🙂

NuclearMoose
(@nuclearmoose)

19 years, 3 months 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”.

7milesdown
(@7milesdown)

19 years, 3 months ago

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

limeshurbet
(@limeshurbet)

19 years, 3 months ago

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

jpigford
(@jpigford)

19 years, 3 months 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

Ryan Boren
(@ryan)

19 years, 3 months 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.

jpigford
(@jpigford)

19 years, 3 months ago

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

Ryan Boren
(@ryan)

19 years, 3 months 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.

jpigford
(@jpigford)

19 years, 3 months 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/

jpigford
(@jpigford)

19 years, 2 months ago

Anybody have any update on this issue?

Ryan Boren
(@ryan)

19 years, 2 months ago

The reports I’ve received indicate the problem is fixed. I’ve done several upgrades from 1.2.2 without incident. If you’re getting the error on every page, something is out-of-whack. Since your upgrade-functions.php wasn’t up-to-date, perhaps other files aren’t up-to-date.