Issue: How to uninstall?

You're right. The new uninstall code in RC gives the permission denied message you noted in a vBulletin environment.

In the Product Manager, you will have to edit the uninstall code for version 1.0.0. Find the line that says:
Add this before that line:

Hi there,

Did that, now I get a blank grey page when doing uninstall.

In vault/core/controller/uninstall/vw.php, find:
Replace with:
As a side note, I've reopened this because the first change I gave you involved editing a value in the database, so an upgrade script needs to be written to do that on other existing installations.

I don't seem to have that line in my vw.php file anywhere.

Closest I can find is: Also I have tried editing that to both things you posted above and it had no effect.

There were a lot more issues with this version of the uninstaller. I am trying to bundle all the changes into a new build some time today. The directory location of the uninstaller was changed in RC 2, and it seems that caused a lot of issues that were not expected.

This issue has been marked as fixed again since the upgrade script to handle the changes above has been written, and the other issues I mentioned have been resolved.

Hey there,

We just noticed a new issue, even though vaultwiki is uninstalled we still have buttons appearing in the enhanced editor when making any kind of post on the forums.

If you ran the uninstaller between RC 2 build 001 and RC 2 build 002, and it somehow completed successfully, from what I understand absolutely nothing was removed from the database.

You can manually remove the buttons from vBulletin's Custom BB Codes section in the AdminCP.

Hey,

I managed to remove the bbcode and manually removed all the files. As you said I ran the uninstaller and it seems to of at most removed the template edits and its entry from the manage products page.

I have checked the database and can confirm that the VW tables are still there.

What is also interesting is that I did attempt to upgrade to the latest version but it never added back the entry under manage products so reverted to a backup.

What is the best way to get rid of the database changes made by vw? I don't mind doing it manually as long as I have a complete list.

Just to update:

I dropped all the tables starting with vw_

And looking though the alter folder manually checked each table and removed the vw colums from there, is there anything else I should check? I cannot see anything else to do with vw now.

That's basically it. If you want to be really thorough:

There are some entries in the datastore table that start with vw_
Make sure that the contenttype table doesn't contain vwpage or vwcomment.
Make sure that the package table doesn't contain a vaultwiki or vw entry.
There are also entries in the blocktype, block, cms_widgettype tables with vw in the name.

If you have to remove any of the above manually, change the following setting for a few minutes:
Settings > Options > Server Settings and Optimization Options > Disable Content Caching = Yes.
After visiting a few pages the entries you removed should be cleared from the cache and you can set it back to No.

Rebuild the search index.
Rebuild the activity stream.

Unfortunately, as you noticed, upgrading a version does not re-add the product entries. It just performs any steps between the current version and whatever version is logged in the database. If you had a partially removed product already, you would have to remove the vw_upgradelog table in order to work around that issue. If this table is missing, VaultWiki thinks it has not been installed yet and will recreate all the data.

Hey,

Thanks, looks like i got it all covered

So if i understand right, in future I could remove the vw_upgradelog table if I got in a similar situation and that would re-add the entry in the product manager?

Yes, in that case it should treat it as a fresh install. The install process is pretty smart also about not duplicating anything that is already installed, so really the only thing to worry about is the vw_upgradelog table.