Manual update RC5 -> Gold

[HunterP]

Hi there,

I have lots of mods running and have done some manual theme edits. There's no way that I'm going to overwrite all my files
So I will perform the update manually, using a file comparison tool and apply the changes between RC5 and Gold manually for each file.
But what about the database, can I run the upgrade.php without losing any data?

Also, what are the best steps for the least downtime and errors?

1. DB
2. Source files
3. Theme files

Or edit the corresponding source and theme files together? Like first Display.php and Display.template.php ?

[NanoSector]

upgrade.php only takes care of the database as far as I know.

And you can do the file editing by taking the online files to your computer and editing them there.

[HunterP]

And you can do the file editing by taking the online files to your computer and editing them there.

That's what I was about to do

[Adish - (F.L.A.M.E.R)]

I haven't performed something which are about to perform, however, I would suggest that it will be better option to do the custom edits again instead of comparing the SMF files from RC5 to Gold. It will be far less time consuming and it will avoid things getting broken in the process.

About the database, yes, upgrade.php should be enough.

[HunterP]

I haven't performed something which are about to perform, however, I would suggest that it will be better option to do the custom edits again instead of comparing the SMF files from RC5 to Gold. It will be far less time consuming and it will avoid things getting broken in the process.

Impossible, I don't know all changes by heart...

[Adish - (F.L.A.M.E.R)]

For the custom theme edits, just download the theme again and compare the theme files.

As of the other edits, you can simply add them again by reinstalling the modifications. That way you will save quite some time unless you have touched the files within the "Source" folder.

[NanoSector]

What will help later is to package the edits into a modification for easy reinstallation

[HunterP]

Thanks for the suggestion, but I have enough time, so that shouldn't be the problem.
Are there any real objections not to update manually?

[Illori]

well every file has been edited due to the copyright/license change in the header of each file, so you might be better off to diff the files and find out your changes and go from there editing them into each file.

[HunterP]

well every file has been edited due to the copyright/license change in the header of each file, so you might be better off to diff the files and find out your changes and go from there editing them into each file.

Thanks for the advice, but I am going to upgrade manually, no matter if it takes me 27 years.
I was just wondering if there are any real objections. That I need to edit allmost all files (not all, some can be overwritten since only the header has changed) is really no problem for me. There are worse things in life

[Norv]

There aren't really reasons why you cannot, we just think it's easier the other way around, because if you count file headers, there are more changes from RC5 to 2.0 than have (most likely, I mean practically ALL the files are changed from RC5 to 2.0).
Either way you go, you might want to take a look at a specialized tool for diff-ing files, for example winmerge on Windows, Meld or diffuse on linux (from the graphical tools), they may make even manually editing files much easier.

The best option (again, either way you go), is probably to make a .diff file either from RC5 to your customized installation files (and apply it back after normal upgrade), or from 2.0 RC5 to 2.0, and apply it on your files. Working directly with .diff files may be less user-friendly though, than using graphical tools to see each step you make.

[HunterP]

Ok, I've locally modified all files. Now I need to know the exact DB-changes for in case I've made some mistakes and I have to revert back to RC5..?

[Norv]

There aren't many database changes, between RC5 and 2.0 final, but in order to have them run, you can simply upload upgrade.php and upgrade_2-0_mysql.sql files (only these, since your database is 2.0 RC5) to your SMF folder and run upgrade.php.

Please consider backing up your database before running it, though.

Please note that the upgrade script however, will check some files to see if they're the proper version it needs to run on. That requires the edits done for files headers as well, not sure if you did those? The same goes for language files, it will check their versions.

[HunterP]

There aren't many database changes, between RC5 and 2.0 final

I see some minor changes in the mysql.sql file, but they don't seem to apply to the database itself.
So can anyone tell for sure if there are any??

[HunterP]

Have updated manually, 0 downtime. All working fine 

[watchhorse]

Have updated manually, 0 downtime. All working fine 

How many files you have to adapt (except the language files)?
Do you have a list?

[Dzonny]

Have updated manually, 0 downtime. All working fine 

Wow, great
Can you tell how much time it takes to finish update manually?

[HunterP]

I had to update all files, since all headers have changed. I've made folders for "sources", "core" and "default", and in all three folders I've put the RC5 files, Gold and my current files from the server. Where the RC5 and current files where the same (date and size), I've copied the Gold file to the current file. Where there were differences, I compared the files and applied the differences manually in the 'current' file. Afterwards I uploaded all files and changed the version number in the DB.

All seems to be working fine now...