This does NOT work with vBulletin 5.

The full version features a working MediaWiki importer from a live installation of MediaWiki (by pointing it to the MW database and images directory path).

Everything from a stock MediaWiki installation is imported and syntax is converted. There might be some quirks here and there, but for the most part it should look fine. If not, open a ticket with support. However, anything that was added via third-party MediaWiki extensions is not handled by the importer.

The full version does not support adding categories via templates, as some MediaWiki templates might do. VaultWiki categories are stricter than that. Templated categories would only appear as links.

You can import from any version of MediaWiki since 1.5, although I recommend a later version like 1.24.

Uploaded 4.0.13.

Changes in 4.0.13 (released August 9, 2016):

• Users Browsing the Wiki
• Fixed unreleased locks making deferred tasks slow
• Fixed some extra/meaningless queries
• Fixed extra Guest credit in content list
• Fixed missing search results for wiki pages with matching content
• Fixed some counters not updating when wiki content is deleted
• About 55 other bugs were fixed

Note also that the Vulnerabilidad de Las Plagas disclosed today does not affect the Lite version.

Thank you for your reply.

I have over 50,000 pages to import though so I wonder if those "quirks here and there" can not quickly escalate to something unmanageable.

I still can't make my mind about vaultwiki, the license is very cheap and it has many interesting integration features. On the other end I might run into tons of unexpected issues which I have no time to manage, and I will not benefit from future mediawiki upgrade.

Why wouldn't you sell a fully working bridge as well? I would buy the VaultWiki license twice for a working and supported bridge, because there isn't any at the moment afaik. The one product which exists is designed for deprecated php versions which are not valid for production anymore. Sounds like an opportunity for you to expand your market. :)

Updated the ZIP to 4.0.14.

Changes in 4.0.14 (released September 19, 2016):

• Improved performance of some functions
• Fixed wiki overlays not matching forum overlay style
• Fixed Manual Mode causing unexplainable problems during install/upgrade
• About 90 other improvements and bug fixes

Updated the ZIP to 4.0.15.

Changes in 4.0.15 (released November 8, 2016):

• Fixed some race conditions
• Fixed ability to delete old edits
• At least 90 other fixes and improvements

A new set of patches was released this week to address the most recently discovered vulnerability: https://www.vaultwiki.org/articles/200/
Please make sure you are using a patched release if your installation is live.

Please note that there was a patch uploaded to this thread prior to my post. That ZIP was broken, but a working version is now attached as of this post.

It is highly recommended that users apply the latest patch, which fixes broken unsubscribe links: https://www.vaultwiki.org/articles/202/

Uploaded 4.0.17 Patch Level 1, which includes the following:

• Create New Page button on Wiki Index
• Remove All User Subscriptions via Inline Moderation
• Renamed some Admin Panel headings to avoid confusion
• Fixed Subscription Management Flaw VWE-2017-3677 (see: https://www.vaultwiki.org/articles/209/)
• Fixed guests can't view user's list of feeds
• At least 20 other bugs were fixed

The file exists, however it is in /plugins and not in /plugins/forum as the path indicates.

Fatal Error: attempted to instantiate non-existent class vw_Plugins_Forum_Model
[path]/vault/core/model/plugins/forum/vw.php does not exist or does not contain the specified class.

#0: vw_Hard_Core::fetch_object() in [path]/vault/core/model/vw.php at line 682
#1: vw_Hard_Core::model() in [path]/showthread.php(2406) : eval()'d code at line 260
#2: eval() in [path]/showthread.php at line 2406

Please forward this error to VaultWiki technical support at https://www.vaultwiki.org/support/4X/ or email support@vaultwiki.org.

In AdminCP > Plugins & Products > Plugin Manager, locate the VaultWiki plugin for hook "showthread_complete" and remove it. It is not relevant to the Lite version and is responsible for this error. I will upload a new version that has this fixed shortly.