[Marco van Herwaarden]

Ok i have found what is causing this. You say you try to create an alias for some default settings, well you don't really. What you are doing is move some default settings to a new settinggroup. The setting will disappear from teh default location and is moved to your own setting page. Instead of grouping everything together, you are splitting things up by moving settings that belong to the default Tagging Options to your own option group. You also change the settings from belonging to the "vBulletin product" to your own modification. With an upgrade of vBulletin the upgrade process tries to re-insert these settings as they appear to be missing, and this will fail as the setting does exist but not in the location vBulletin expects.

Solution to this is not to mess with default settings.

To make things even worse, when your product is uninstalled it doesn't recognize the setting as a default vBulletin setting anymore but as belonging to your modification, and the setting will be deleted from the installation. This will leave vBulletin running but you can expect problems as settings that are expected to exist have now been removed.

The easiest way to repair your vBulletin installation is to follow these steps:
- Uninstall this product.
- Make sure the install directory with all files, except install.php, are on your server.
- Upload tools.php, found in the do_not_upload directory of your vBulletin distribution, to your admincp directory.
- Point your browser to www.myforum.com/admincp/tools.php
- Import Settings & Language
- Remove tools.php from your admincp directory.