How about a highly visible warning to people that failure to uninstall mods in the reverse of installation may/will lead to problems? Preferably associated with a 5,000 volt jolt when they then ignore the warning.
Since that probably still won't work since they already ignore the warnings provided by the package manager, how about designing the package manager so that mods have to be removed in reverse order?
I would love a dollar for all the support requests I have seen in these forums that arise from that very issue :)
I will happily drop some donation for such mod :p
Where's the problem? If uninstalling mods will create issues, it will warn you.
The problem is that people still carry on regardless, end up screwing up their site, and place countless support requests.
Most people do not know you must un-install in reverse sequence (before they do it).
best way to stay out of trouble? - don't install mods ;)
Lainaus käyttäjältä: Resourcez - helmikuu 17, 2008, 11:36:20 IP
..
I would love a dollar for all the support requests I have seen in these forums that arise from that very issue :)
Lainaus käyttäjältä: Ol' Wombat - helmikuu 18, 2008, 04:03:10 AP
best way to stay out of trouble? - don't install mods ;)
Lainaus käyttäjältä: Resourcez - helmikuu 17, 2008, 11:36:20 IP
..
I would love a dollar for all the support requests I have seen in these forums that arise from that very issue :)
agree but some time you really need it
Lainaus käyttäjältä: Resourcez - helmikuu 18, 2008, 02:52:33 AP
The problem is that people still carry on regardless, end up screwing up their site, and place countless support requests.
How does the fact that they ignore an uninstall warning makes you think they will follow any warning?
I would settle on just allowing the MODS to list in the package manager in the order they were installed. Or, a number sequense listed.
This is why I hand apply all mods so I know what changes what. I think that being able to sort the mod list by install order would solve the problem for most. Not all mods are going to conflict anyway so no reason to force them to uninstall in order. When displaying the warning it should suggest to try uninstalling in the order installed.
Lainaus käyttäjältä: Motoko-chan - helmikuu 19, 2008, 11:25:07 AP
Lainaus käyttäjältä: Resourcez - helmikuu 18, 2008, 02:52:33 AP
The problem is that people still carry on regardless, end up screwing up their site, and place countless support requests.
How does the fact that they ignore an uninstall warning makes you think they will follow any warning?
hmm, that was the intent of my original post, I agree they won't - the warnings don't work - make it so they have no choice.
If that is not preferable, then at least forewarn users about the importance of reverse order un-installs, because that is not obvious to people.
The mod, if created, should check which files are affected. A mod should pop up with a warning if another mod is using that file, but something that modifies the registration.template.php file doesn't need to be uninstalled before something that modifies the display.template.php file.
And, if created such mod it should check database table too. Just yester day I droped some junk table from my database with help of Kindred and SleePy. I installed some mod and unintalled it but uninstaller didn't drop those table they had created during installation and I was carrying those table here to there from last one year :(
In anticipation of no change, this is what I am adding to my uninstall process
Lainaa<readme type="inline"><![CDATA[
You must run Uninstall before upgrading so that all existing Treasury changes and files can be removed.
Note: for theme changes, Uninstall will only modify the default theme.
Any manual changes you made to other themes you must manually reverse yourself.
To avoid any warnings below, it is recommended that you first uninstall mods added after Treasury,
and uninstall them in the REVERSE ORDER that you installed them.
If you do have warnings below, continuing the uninstall process WILL create issues with your site.
Use the Package Parser and check the "Uninstall" option to provide guidelines to manual removal of Treasury.
Then determine what caused this issue and fix that.
NOTE: Uninstall will deliberately NOT remove the Treasury database tables.
For permanent Uninstall you will need to manually drop these tables from the database:
- smf_log_treasury
- smf_treas_config
- smf_treas_donations
- smf_treas_registry
- smf_treas_targets
(assumes you used smf_ for your prefix)
]]>
</readme>
At least users will be forewarned better than they are now :)
Lainaus käyttäjältä: sherpa - helmikuu 19, 2008, 07:04:16 IP
And, if created such mod it should check database table too. Just yester day I droped some junk table from my database with help of Kindred and SleePy. I installed some mod and unintalled it but uninstaller didn't drop those table they had created during installation and I was carrying those table here to there from last one year :(
Actually I disagree with this. The database tables most of the time contain the user data for that mod. If you were to uninstall to install the newer version you wouldn't want to loose this data. Maybe just a notice letting them know the database table still exists would be good.
ok just say you install tha chat mod and now you are not using chat any more then why you need those 10 tables?
If you don't need them you can drop them yourself, it's very easy to do.
Non of this is on-topic - please continue that discussion elsewhere.
Sorry Resourcez I mean not to out out focus your topic
please read this
http://www.simplemachines.org/community/index.php?topic=223444.msg1433402#msg1433402