Issue: Install/Upgrade Issue

If you have already tried confirming the presence of vault/core/controller/install,
and placing XenForo in debug mode doesn't reveal any useful error message,
then it sounds like you may have a corrupt installation from trying to use the 4.0.5 uninstaller to remove a different installed version 4.0.4.

In this case, your database may need to be repaired, and you need to submit a ticket here in order to start that process: https://www.vaultwiki.org/members/?d...e&productid=20

Thanks, I'm also having my tech guy look into it. If this doesnt work then I'll fill out the request. One question, does the installer/upgrade scripts modify anything in existing xenforo tables?

C.

I believe it adds a column vw_options to the xf_forum table. It also adds entries to the content_type and content_type_field tables.

Thanks. I dropped all the tables starting with 'vw_' and removed all the existing files, then re-uploaded and re-ran installer and everything looks correct, including the vw_options column in xf_forum and the content_type and content_type_field tables.

One suggestion--might add on your install instructions a mention that if you run multiple VaultWikin instances backed by a single memcache instance that you'll want to chance the prefix in config.php.xf - I didn't realize you cache to memcache (great feature!) and only stumbled across the prefix setting by accident while reading through the config options. I run multiple forums on a single VPS, a scenario that's fairly common in my experience, and all are backed by a single memcache instance for simplicity... it would have been horribly frustrating trying to debug this if we ended up running multiple VW instances.

Great news, I was beginning to worry.

While a cache prefix is created by config.php, VaultWiki currently has no specific implementation for Memcache. It is one of those features we started and never got around to finishing. Currently VaultWiki will just use whatever cache your forum uses, which for XenForo is typically the xf_data_registry table.

Now vBulletin does offer an option to use Memcache for vBulletin things, and I believe if that is turned on then it will just offload VaultWiki caches there. I'm not sure if XenForo has something similar or if there is an add-on. There is a known bug we discovered early on in vBulletin's Memcache implementation where it is impossible to remove entire keys from the cache without circumventing the forum. This did cause problems when a reinstall was performed or when VaultWiki was upgraded from a Lite version. However, VaultWiki's own cache prefix is never used for this case, because the main Memcache instance is controlled by vBulletin which has its own cache key.

Changing this to a bug and marking this as fixed in the next release. When uninstalling on vBulletin, VaultWiki will now workaround the vBulletin bug and delete the Memcache entries directly. Again I don't know that XenForo offers Memcache support at this time, so this fix only applies to vBulletin.

Thanks for the heads up.

Xenforo supports memcache via the Zend framework, which supports multiple cache backends: https://xenforo.com/help/cache/
Xenforo software allows each Xenforo instance to use a different cache prefix, so I just set it as unique for each forum.

I'm not familiar with what they actually cache, but I suspect it's just user sessions from the xf_user_session and xf_admin_session tables (I think those are the right names)... I don't think they automatically cache addon data out to memcache, but I could be wrong, you'd have to ask in their forums.

Anyway, maybe just add (for now) a comment in Vaultwiki's config.php next to the memcache setting that says 'only applies to vBulletin, not Xenforo'