First, if your recent vBulletin "update" was a major upgrade from vBulletin 3.x to vBulletin 4.2.x, then you need to run VaultWiki's upgrade script anyway in order to install the vBulletin 4-compatible version of the product. The upgrade between vBulletin 3 and 4 automatically disabled all plugins and products because vBulletin 3 products are generally not compatible with vBulletin 4.
Otherwise, according to the source code, there are 3 conditions that might trigger this message. Source code:
Code:
if (
!$vbulletin->products['ces_nwsp_spec'] OR
(
!$vbulletin->options['vault_enabled'] AND
!is_member_of($vbulletin->userinfo, 6)
) OR
!defined('CES_VAULT_VERSION')
)
{
eval(standard_error(fetch_error('vault_wiki_disabled')));
}
Basically, if any one of the following is true, the disabled message appears:
- The product VaultWiki is disabled in vBulletin's AdminCP, under Manage Products.
- The setting VaultWiki: Server Settings > Turn on the Wiki? is set to "No", and the viewing user is not an administrator.
- The constant CES_VAULT_VERSION was not defined.
If the first 2 are ruled out, you might be wondering about the CES_VAULT_VERSION constant. This is defined in the file
vault/wiki.php. This file is included by a plugin that uses hook location
init_startup by the name "General - VaultWiki Init". Thus, if CES_VAULT_VERSION is not defined, these are the possible causes:
- The plugin "General - VaultWiki Init" is disabled in vBulletin's AdminCP > Plugins & Products > Plugin Manager.
- All plugins are disabled by the setting Plugin/Hook System > Enable Plugin/Hook System = No.
- All plugins are disabled by includes/config.php (DISABLE_HOOKS would be defined).
No matter what the issue is, note that VaultWiki 3.0.16 was released in 2011 and is no longer supported at this time. As mentioned in the email reminders we send out from time to time, 3.0.16 contains an accrual of at least 3 security vulnerabilities and you should have migrated to a newer version by now to avoid vandalism to your site.
https://www.vaultwiki.org/articles/117/
https://www.vaultwiki.org/articles/134/
https://www.vaultwiki.org/articles/158/
The last link suggests that VaultWiki staff will patch affected VaultWiki 3.x sites running unsupported versions for a fee.
Note that if you need to run VaultWiki's upgrade script in order to update the installation for a change from vBulletin 3 to vBulletin 4, and you no longer have a copy of VaultWiki's install/upgrade folder on your server, and you don't have a backup, you will not be able to update VaultWiki. We do not provide downloads of software that contain security vulnerabilities. In this case, your only recourse will be to install VaultWiki 4.x and import your VaultWiki 3.x data into it. Since your installation would be in limbo currently, I strongly recommend purchasing an Import Service in case any conflicts arise related to your VaultWiki installation not being correct for your vBulletin version.
If there are any bugs in the 3.x series of VaultWiki they are no longer going to be addressed, and VaultWiki 3.x is no longer being updated for compatibility with new versions of vBulletin, since VaultWiki 3.x reached its end-of-life in January 2014. If you plan to continue using VaultWiki, you should start planning your migration to VaultWiki 4.x.
January 12, 2015 7:36 AM
Junior MemberWiki broken after vb update
It is all showing enabled in my admincp, but when I go to the URL for the wiki: http://alphaflight.net/showwiki/Main_Page it's states that it is disabled. My vaultwiki version is 3.0.16. Am I looking at an upgrade issue? Is it balking a the updated PHP?
Please Wait