Upgrade Error - Been at it for a week now...

[Novice]

Now the error is:

Notice: Undefined index: upgrade_upgrade_utility in /home/content/11/13951611/html/testsite/upgrade.php on line 3486

Simple Machines Forum

Notice: Undefined index: upgrade_progress in /home/content/11/13951611/html/testsite/upgrade.php on line 3498

•
Notice: Undefined index: upgrade_step in /home/content/11/13951611/html/testsite/upgrade.php on line 3503
1: Login
•
Notice: Undefined index: upgrade_step in /home/content/11/13951611/html/testsite/upgrade.php on line 3503
2: Upgrade Options
•
Notice: Undefined index: upgrade_step in /home/content/11/13951611/html/testsite/upgrade.php on line 3503
3: Backup
•
Notice: Undefined index: upgrade_step in /home/content/11/13951611/html/testsite/upgrade.php on line 3503
4: Database Changes
•
Notice: Undefined index: upgrade_step in /home/content/11/13951611/html/testsite/upgrade.php on line 3503
5: Delete Upgrade

0%

Notice: Undefined index: upgrade_overall_progress in /home/content/11/13951611/html/testsite/upgrade.php on line 3512

Notice: Undefined index: upgrade_time_elapsed in /home/content/11/13951611/html/testsite/upgrade.php on line 3537
: 0
Notice: Undefined index: upgrade_time_mins in /home/content/11/13951611/html/testsite/upgrade.php on line 3538
, 0
Notice: Undefined index: upgrade_time_secs in /home/content/11/13951611/html/testsite/upgrade.php on line 3538

Updating Your SMF Install!

The upgrader found some old or outdated language files, for the forum default language, english.

Please make certain you uploaded the new versions of all the files included in the package, even the theme and language files for the default theme.
   [SKIP] [Try English]

Click here to try again.

SMF ©2013, Simple Machines

[Novice]

I have another subdirectory with ver2.0.10 running fine with no errors. Do you think that if I drop those sql tables and upload the backup of the 1.1.21 into it and run the upgrade, that it will recognize everything new and just convert the tables?

[Antechinus]

Crap. So it's still not finding the languages file. That fix no good then.

You could try stripping and importing on the other 2.0.10 test site if you like. At the moment I have no idea if it will work, but if you're up for giving it a go then sure.

[Novice]

I'm going to backup the existing database - Dump the tables - Upload the backup - scream bloody murder

I shouldn't need all the folders uploaded in this one. They should all be up to date, right? Just upload all of the upgrade files?

[Antechinus]

In theory, yes.

[Novice]

We will test the theory this time. If it errors about old files this time SMF has the issues, not us. Everything about this version said it was up to date. So, the database conversion is the only thing this update has to do.

[Antechinus]

Ok, go for it.

[Novice]

Same thing.... I'm at a loss here.

[Illori]

since you moved the database, you need to run repair_settings.php first to correct the paths.

[Novice]

I thought the settings were located in the program hosting settings file? This never moved, only the tables in it's database.

I have dumped the backup files and restored the original 2.0.10 tables and it fired right up as if nothing happened.

I need to call it a day. Or should I say day #8

[Novice]

Couldn't walk away... But good news! The database is updated!
SMF ver2.0.10 is alive and well with data dating back to 2007. I had to go into MYSQL admin and manually edit the source paths in the settings, smiley & theme tables. Once this was done, it was all smooth sailing. Until these were corrected, repair_settings.php was only an informational tool. It repaired nothing. It should be written in the update.php script to first edit these files, especially if someone is trying to restore one to a new server.

Hats off and thanks to all! Especially Antechnius and Illori. Two helpers are always better than one!

Thanks again!!!!!

Novice

[Kindred]

just to be clear... your initial process was just plain wrong - which led to the confusion - and I would like to make sure that anyone who comes across this thread in the future understands it.

You should NOT install 2.0.10, drop tables and then try to import the 1.1.x tables.

instead, you take a copy of the 1.1.x files and database -- and place those files and database in a different location -- then run repair_settings.php (still on 1.1.x) and confirm that 1.1.x is running correctly.

THEN, and ONLY THEN, you upload the 2.0.x files, overwriting all of the 1.1.x stuff and run upgrade.php

[Novice]

Correct...If you have the other files. I know they can be downloaded from this site from archive but, I have yet to get any of these installs to get passed the very first install page. Once you put in your info, the install errors out from install.php beginning in my case at line 500 thru 520 with thirteen errors.

My only choice was to install the software that would install. Also, after the conversion of tables, the program ver2.0.10 stopped functioning correctly. No PM, email, registering of new members or replies to posts. It is now a view only forum. Members can log in, but this is all they can do beside view the boards.

I'm glad I didn't attempt to upgrade the original site. I would have likely killed it.

[Kindred]

WHY THE HECK ARE YOU EVEN TRYING TO DO AN INSTALL??

DON"T DO AN INSTALL!

copy the files from your existing site to your empty, brand new directory/server
copy the database from your existing site to your EMPTY, brand new, test database (on the new server)
run repair_settings.php to correct/update the database connection info to point to the new database.
run repair_settings.php AGAIN to update the URLs and PATHs to point to your new server location.

NOW you have 1,1,x installed, just like your live site.

THEN, and only then, start the upgrade process.

DO NOT *INSTALL* anything.

[Antechinus]

If you're going to do it that way, lock down your live site while you are messing with the test site. This is because until you get all the paths corrected, any changes on one forum will affect both.