SMF 2.0 Update Part Last

[Aleksi "Lex" Kilpinen]

lol... I still have files from YaBB on one server.

Yeah - That's why

[Arantor]

why would you uninstall mods before a large upgrade?   By doing the large upgrade, you remove all mod code, period, because you are replacing the forum files which had been modified.

the only thing you have to worry about is doing the installation of the mod into the new version after upgrade.

Wrong, actually. The packages table is not cleaned up during the upgrade, listing most if not all mods still installed, and making it somewhat more difficult to install since you have to fudge it through an uninstall first.

[Illori]

as far as i know 1.1.1* does not store the packages installed in the db so the above method would work fine for upgrading from 1.1.* to 2.0.

[Arantor]

Correct, but all 2.0 RCs do...

[Aleksi "Lex" Kilpinen]

That sounds like a bug to me, the large upgrade removes all the edits to files - it should remove the installed packages from the db too...

[jackregan]

I am using TinyPortal on RC5. Can anyone tell me if I'll need to uninstall TP to upgrade to SMF 2.0??

[Illori]

That sounds like a bug to me, the large upgrade removes all the edits to files - it should remove the installed packages from the db too...

but the database does not know if the files are removed

[Aleksi "Lex" Kilpinen]

That sounds like a bug to me, the large upgrade removes all the edits to files - it should remove the installed packages from the db too...

but the database does not know if the files are removed

Unless I'm missing something it doesn't have to, it only needs to know if the mods are still installed or not....

[Illori]

right and if you manually removed the files and did not touch the database, the database has no way to know. there is no check other then through the package uninstaller to tell the db the files are removed.

[Arantor]

No, but there is code in the upgrader for it...

[Antechinus]

Yup. If anyone gives a rat's, I do upgrades like this:

1/ Get the large upgrade for the version I'm currently using, and load all files except the upgrade php and sql files.

2/ Delete all mod zips.

3/ Uninstall and delete all custom themes.

4/ At this point you effectively have a new, vanilla installation. Then upload all the large upgrade files for the new version (including the actual php and sql upgrade scripts)

5/ Run upgrade.

6/ Install custom stuffs.

7/ Have beer.

Works perfectly every time.

[Arantor]

Step 2 - uninstall or delete? If you mean just delete, the database record of installation is still present and it will invariably show as installed if you replace the zip file (which means fudging an uninstall to have it handle installation properly)

[Antechinus]

I find that overwriting Packages/installed.list with a blank copy seems to sort it all out. Never gave me any problems doing it that way. But yes, I really should sort the db itself. Doesn't seem to matter if you don't though.

ETA: Mind you, it'd be rare for me to reload the exact same mod zip.

Oh yeah, I'll often uninstall the ones that will uninstall, but just delete the ones that wont.

[Farjo]

I'd suggest that someone write an upgrade document but it would delay the release for another year while the team argues about the grammar of one paragraph

[Illori]

we have a document already Upgrading SMF http://wiki.simplemachines.org/smf/Upgrading

[Antechinus]

Should note that my way of doing it is overkill in 99% of cases.

[Arantor]

ETA: Mind you, it'd be rare for me to reload the exact same mod zip.

Doesn't even have to be. It uses the package id to determine whether or not it's the same mod. That's why a bit back I had '2 copies of a mod installed' with only one entry in the log_packages table, because this was on Windows and the first mod was mod.zip, the second was mod (1).zip. Package manager is voodoo, mess with it at your peril

[Antechinus]

Ok, so in future I'll sort the db fields for any mods which wont uninstall. Easy.

ETA: Mind you if I'm going to do that, it'd be faster to just delete all the zips and then run one query to sort all the db entries.

[Arantor]

Or, you could just truncate smf_log_packages, which would be a whole lot quicker

[jackregan]

So what about TinyPortal?

When I upgrade my RC5 to 2.0 Gold will it just wipte out TinyPortal?

If so, will all my articles and stuff be there when I just reinstall TP?