Would love to see In MODS section
 

List of database tables used in a mod.

So that we can actively see what needs removing !

Also it should be pre-requisite that mod authors supply removal instructions.

I like this idea, it's a pain when we get a ton of SQL syntax errors after the install of a mod and it don't remove all of the table rows in the db.

Making this a requirement is not likely to happen. We want our members to share as much as possible and putting up artificial limitations would work against that objective.

Whenever you get errors installing modifications, it is that you haven't uploaded all files, or put them in the correct directory. Seems to be a an easy answer for most mod install problems. Also when your forum crashes, easy disable all hooks via config.php and them remove the modification.......

This information is available to you in the product file from the download. Just open it up with a text editor and it's right near the top.

Most of the time, you will get some removal instructions if it requires something specifically different then just running the uninstall link in the ACP and deleting the pertinent files. I don't think I've run into one yet that fails to mention extra steps if they are needed. What have you run into that did that?

I had the idea of adding a ref directory to one of my mods which contained some technical information. Its something i'd like to expand on doing and add it to all my mods, however documents even as simple as the ones I provided there take time to produce; time which could be spent adding new features or fixing bugs.

I know that the OP had problems when it came to removing one of my mods; this was my fault for not testing the installation/uninstallation code properly. (Ironically, the code itself was covered by unit tests; but they had not been extended to the install/uninstall code :s) This is something i've learnt from and have now setup a dedicated development board specially for testing install/uninstallation of mods.

Whereas I agree that making a requirement is a bad idea, how about a 'good practice' guide?

Another thing that kinda bugs me is the variation in the way different authors lay out their mod threads. When vborg moves to vb4; I assume there will be a custom coded content type for mods - might I suggest that this contains fields for useful things like installation instructions, uninstallation instructions, feature list, description, change log etc. Maybe even something to elaborate on files that are included and database changes that the mod makes.

Without pointing fingers ( as he waves his finger ) have any of you ever installed evos chatbox ?

Then removed it, using all the documentation provided, and uninstalling as per the steps suggested ?

If so, check out your phrase manager !

It annoys me that the uninstallation of a mod, leaves behind debris within phrase manager. In the case of evo_chat , over 1000 phrases floating around in your db !

--------------- Added [DATE]1267733928[/DATE] at [TIME]1267733928[/TIME] ---------------

I agree

Hrm, you know, since MGC requires you to import and overwrite your existing language file, I don't think that's something you could remove any other way. The phrases are not part of the product for some reason.

Infuriating, and I bet hundreds of vb4 upgraders havent even checked their phrase manager and seen the remnants of mods removed of days gone by !

We removed via phpmyadmin, but that is usually above and beyond the ability of most forum owners, hence a complete removal tool for products such as mcb etc.

To add:

goto phrase manager and search for mcb_

If you ever installed and uninstalled you may well be surprised as what remains