Issue: Upgraded Vault Wiki from 3 to 4.6 Database errors

Thanks for reporting this. To fix this conflict, VaultWiki 4's package class should be changed from 'VaultWiki' to 'VW'. This is a somewhat massive change that will affect many files and all plugins.

Until this can be resolved, please continue using VaultWiki 3. I will add a free service to your account so that the changes can be applied to your installation as soon as they are available. This service should appear in about 12 hours. To avoid conflicts with PHP 5.4 until that time, please follow the instructions outlined in this post: http://www.vbulletin.com/forum/forum...66#post4000466

My apologies for this inconvenience.

Ok I have gone back to VW 3 followed the instructions in your link, but now I have new errors that I did not have before I have just disabled the wiki for now, however I am now showing two instances in plugins and products, which I guess I should expect, however one of them shows the following:

VaultWiki 0.0.0 A fully-functional wiki for vBulletin.

Here are the errors I get now that I am back on 3 when trying to access the wiki:

If that's the case, make sure the wiki file name is still set to "showwiki" in your VaultWiki 3 options called "Server Settings."

wiki_index.php is the VaultWiki 4 file and content.php is a default vBulletin file if you have the full vBulletin Suite. If you have the forum only, you need to change the appropriate directive in vault/config.php where the file's comments say to do so.

The showwiki is correct in the server settings, and the vault/config.php file is also correct(however it is showing that the config file is for vw 4.6 not 3, so I am sure that is causing issues as well.

In the next release, fixed the package conflict when installing VaultWiki 4 where VaultWiki 3 is currently installed. I will try to package the changes today in order to apply them to your install to get you back up and running.

Patch note: This change affects all active VaultWiki plugins on vBulletin, required a rename to the package directory and all the classes within that directory, updates to every other bit of code that uses those classes, changes to the database, and several cache rebuilds. So a patch cannot be posted here as it pretty much requires a full upgrade script.

I am in the process of upgrading my forum software from vBulletin 4.1.10 Patch Level 3 to 4.2.2.
I want to upgrade VaultWiki from 3.0.14 to 4.0.0 Beta 6 Build 002

Should I hold off? Reading this, I assume I'd be in the same mess. When will a new version be released to correct these problems?
Will WaultWiki 3.0.14 operate on vBulletin 4.2.2? What about VaultWiki 3.0.20?

I have a relatively large site that depends on the Wiki substantially, so having it go down is a no-go.

Perhaps I should just stick to VaultWiki 3.0.20 until a stable VaultWiki 4 is released. I don't really use VaultWiki as a true wiki so a lot of the features I don't need, but I'd rather not risk it.

The only VaultWiki version that is compatible with vBulletin 4.2.2 right now is VaultWiki 4 Beta 6. If you attempt to use VaultWiki 3.0.20, there will be compatibility messages at the top of site pages and the wiki editor will be distorted and difficult to submit. By the way, 3.0.14 which you are currently running has numerous security exploits which it sounds like you missed the patches for.

I would upgrade VaultWiki to 3.0.20, then wait on upgrading vBulletin to 4.2.2 until the VaultWiki 4 package conflict is fixed in Beta 7. Then you can install Beta 7, transfer your VaultWiki 3 data to the Beta, disable VaultWiki 3, and finally upgrade vBulletin.

Ok, sounds doable. Would you have a rough guesstimate on when to expect Beta 7? I'm looking to update vBulletin to 4.2.2 because of security exploits in 4.1 which have been giving me some troubles with hackers. But I believe I have done enough to prevent them from exploiting for the time being, potentially.