VaultWiki Lite 4.x: Wiki for vBulletin Forums

[thincom2000]

VaultWiki allows your existing forum users to work together on creating and managing a site's content pages, rather than competing to make popular threads. VaultWiki is a fully-featured and fully-supported wiki add-on solution for vBulletin.

Encourage Users to Work Together
VaultWiki allows your community to collaborate to create and publish content pages for your site. Multiple users can edit the same page, and your staff can moderate changes as they are made. VaultWiki maintains a detailed history of every page, making it just as easy to reverse unwanted changes.

Create All Kinds of Content
With VaultWiki, you can create general site content, user manuals for your products, wikis, eBooks, eCommerce product pages, and more. With a little imagination, VaultWiki can be purposed to do almost anything.

Seamlessly Integrates With Your Community
At its core, VaultWiki is an add-on product for your vBulletin forum platform. Its pages all meld with the forum's existing style. Users write new content with the same editor and BB-Codes they are already familiar with. The content is indexed by your forum's built-in search engine. And each user's contributions are acknowledged on his or her profile.

Attract New Membership
VaultWiki creates content and content URLs that are designed to drive new traffic to your site. With guides for search engines embedded in every page, each page preserves its value when it comes to generating traffic.

Fast, Responsive Support
Subscriptions come with free support in our forums and bug tracker system, and documentation is available online at all times. Paid installation and upgrade services can be ordered via our web site.

Active Development
The team at VaultWiki.org are actively involved in the development process. VaultWiki is constantly updated to be compatible with the newest forum software releases, to meet web standards, and to incorporate new technologies. Bugs are fixed promptly and new features come out all the time.

Demo
Demo link: https://www.vaultwiki.org/pages/
Depending on our mood each day, the demo may be the full version or the Lite version.

License
For licensing details, please see the relevant "VaultWiki Lite" sections of the VaultWiki License Agreement here: https://www.vaultwiki.org/pages/Info/Info:License-Agreement

Features the Full Version
The find out more about VaultWiki Lite's features or to purchase the full commercial version, see the comparison here: https://www.vaultwiki.org/features/

Requirements
The following requirements are based on the full version. The Lite version has fewer MySQL tables, fewer files, and takes up less disk space.

PHP: 5.3+ (5.4+ recommended, 5.5+ recommended for big boards)
MySQL: 4.4.1+ (5.1+ recommended)
MySQL tables: 75+ (for some shared hosts)
MySQL max_allowed_packet: ?M+ (500K + expected language row length)
Disk Space: 12M+ (1G+ recommended)
iNodes: 5000+ (for some shared hosts)
Memory limit: 32M+ (128M+ recommended for vBulletin)

Copyright Info
VaultWiki Lite places a copyright notice in your forum's footer on any page where wiki functions are used. It also places a few nag screens that admin users can see. You are not allowed to modify the source code or phrases to remove this copyright or the nag screens.

You can purchase an Ad Removal and/or Branding Removal license for VaultWiki Lite from the official VaultWiki support site. Simply register an account there to access VaultWiki Lite downloads and extras such as these.

Technical Support
You will probably receive faster responses to support questions if you post at the official support site: https://www.vaultwiki.org/support/4X/

Using an old version? You should check here periodically to make sure there are no known security issues affecting that version: https://www.vaultwiki.org/pages/Book/Documentation/Info:Vulnerable-Versions

[Bald Bouncer]

Demo
Demo link: https://www.vaultwiki.org/wiki/
Depending on our mood each day, the demo may be the full version or the Lite version.

Error 404 - Page Not Found
The requested page http://www.vaultwiki.org/wiki/ cannot be found.

If this problem persists please contact us. Mention the error message received and the page you were trying to reach. We are sorry for any inconvenience caused and we will do all we can to fix the error as soon as possible.

[thincom2000]

Demo link updated: https://www.vaultwiki.org/pages/

[EliasAlucard]

Hi, great work. I've been checking out this wiki software, and I'm seriously contemplating using the premium version on my forum. One important question: is it compatible with the GNU Free Documentation License? Is there any option to choose between copyleft licenses, and so on? I remember when I installed MediaWiki a few years ago, I had the choice of licensing all content between the GFDL and various Creative Commons licenses. How does it work with VaultWiki?

And how stable is it now, considering that it's still in beta stage?

[Alan_SP]

Well, I'm using old (v3) version of VW, and I can say that support you get from developer is great.

In case of a bug, you'll pretty soon receive code you need to change, so you don't need to upload new version.

This version (v4) probably would need some more time to reach full stability, but has some great options. So, you can buy old one and start using it, till new version reaches desired stability.

[EliasAlucard]

Well, I'm using old (v3) version of VW, and I can say that support you get from developer is great.Really? They haven't responded yet on their main site. Not even approved my thread there. I guess they're too busy.

In case of a bug, you'll pretty soon receive code you need to change, so you don't need to upload new version.That's cool.

This version (v4) probably would need some more time to reach full stability, but has some great options.Examples?

And why should I use VaultWiki over MediaWiki? I don't like the proprietary EULA of VaultWiki. I prefer the GNU GPL, but I understand they're doing this because they want to be able to charge for the premium version. However, they could just do donations instead, would be much better.

In any case, I'd like to know if there's a license option for the content created in VaultWiki. Using MediaWiki, one can choose between the GFDL or Creative Commons, how does that work with VW?

[Zachery]

Really? They haven't responded yet on their main site. Not even approved my thread there. I guess they're too busy.

That's cool.

Examples?

And why should I use VaultWiki over MediaWiki? I don't like the proprietary EULA of VaultWiki. I prefer the GNU GPL, but I understand they're doing this because they want to be able to charge for the premium version. However, they could just do donations instead, would be much better.

In any case, I'd like to know if there's a license option for the content created in VaultWiki. Using MediaWiki, one can choose between the GFDL or Creative Commons, how does that work with VW?

Technically the GPL license is not compatible with a vBulletin license.

[EliasAlucard]

I'm trying to install VaultWiki Lite, but I get a blank page after I sign in. This (https://www.vaultwiki.org/issues/1534/) wasn't of much help.

Technically the GPL license is not compatible with a vBulletin license.Of course it isn't, because vBulletin is proprietary. That doesn't however mean, content edited on VaultWiki (which is not actually vBulletin, although integrated with it) can't be edited/published/released under GFDL.

The important question here is, why would I use VaultWiki over a hell of a lot more stable, mature, secure, powerful and open source, MediaWiki? All I need is this:

https://www.mediawiki.org/wiki/Extension:VBulletin/Users_Integration

Or this:

https://vborg.vbsupport.ru/showthread.php?t=270517

To get the important vBulletin integration VaultWiki offers.

I don't like VaultWiki's EULA.

[Zachery]

Then don't, and get out of the topic?

[Alan_SP]

Examples?

And why should I use VaultWiki over MediaWiki?

You have your needs, I have mine. And, they are different (it's obvious, but I think this fact needed to be said).

If you want completely integrated wiki product for your vBulletin forum, there's only one wiki product you can use: VaultWiki. Others, in best case scenario, has bridges that help a bit integrating two different software platforms.

About features I like very much in VW4, it's thread headers, based on forum headers, but just in threads, then handling languages. There are of course more new features, but these two are my favorites. And yes, there would be more new features, as developer listens to community. I know that for a fact, thread headers was my suggestion.

[EliasAlucard]

Then don't, and get out of the topic?I'm definitely interested in VaultWiki, but that doesn't mean it doesn't have any shortcomings. I'm posting in this thread because I want answers and possibly a discussion, if the developer(s) is active enough.

You have your needs, I have mine. And, they are different (it's obvious, but I think this fact needed to be said).

If you want completely integrated wiki product for your vBulletin forum, there's only one wiki product you can use: VaultWiki. Others, in best case scenario, has bridges that help a bit integrating two different software platforms.

About features I like very much in VW4, it's thread headers, based on forum headers, but just in threads, then handling languages. There are of course more new features, but these two are my favorites. And yes, there would be more new features, as developer listens to community. I know that for a fact, thread headers was my suggestion.VaultWiki's vBulletin integration makes it a serious alternative to MediaWiki. That's its strongest point. Had it not been for that, I wouldn't even care about VaultWiki. That VaultWiki is cross platform too (XenForo and IPBoard) makes it even better. But other than that, I don't see any other major pros, and it's mostly cons aside from its forum integration.

VaultWiki would have been a lot more stable, mature, feature rich and powerful, had it been open source. What happens if the main author/developer dies in a car accident tomorrow, for example? Who will maintain the proprietary source code? VaultWiki will die out in such a scenario.

VW's vBulletin integration is very compelling, but I think the best thing thincom/pegasus can do, is go GNU GPL v3 and ask for donations. I and many others would happily and much rather, fund VaultWiki with such an approach.

[thincom2000]

I'm definitely interested in VaultWiki, but that doesn't mean it doesn't have any shortcomings. I'm posting in this thread because I want answers and possibly a discussion, if the developer(s) is active enough.

VaultWiki's vBulletin integration makes it a serious alternative to MediaWiki. That's its strongest point. Had it not been for that, I wouldn't even care about VaultWiki. That VaultWiki is cross platform too (XenForo and IPBoard) makes it even better. But other than that, I don't see any other major pros, and it's mostly cons aside from its forum integration.

VaultWiki would have been a lot more stable, mature, feature rich and powerful, had it been open source. What happens if the main author/developer dies in a car accident tomorrow, for example? Who will maintain the proprietary source code? VaultWiki will die out in such a scenario.

VW's vBulletin integration is very compelling, but I think the best thing thincom/pegasus can do, is go GNU GPL v3 and ask for donations. I and many others would happily and much rather, fund VaultWiki with such an approach.
The parent company (Cracked Egg Studios) is currently in charge of licensing, and I doubt they are considering a public license for the full product anymore. It was originally released in late 2007 as a public license, and was changed to a proprietary EULA in summer 2008, because a significant outcry of its user base said that it should NOT be offered for free. In 2010, VaultWiki was given a little more autonomy as VaultWiki Team was formed, but we still have to answer to CES. Throughout that entire time, the product, its image, and feature set have only improved. It tends to be a rule with VaultWiki: if something changes, it doesn't change back.

If there are features that MediaWiki has (vanilla or not) that VaultWiki doesn't have, you are welcomed to make feature requests. We recognize MediaWiki as competition, know it sets the standard, and that we have to exceed that standard when we can. VaultWiki was created by CES in 2007 after they used MediaWiki for a year and decided it didn't have the features they needed (granted that was MW 1.4 versus MW 1.22 or whatever it's up to now). Ignoring the forum integrations, there are many aspects VaultWiki (full) now has over MediaWiki: BB-Code, better permissions, language/translation management, book/chapter management, easier media insertion.

I'm currently compiling a list of feature comparison between MediaWiki and VaultWiki. This is what I have so far (for MediaWiki, these are all "Yes" for VaultWiki). If I'm incorrect on any of these points, please let me know. If an Extension lets you do it, let me know, but the final list would only include popular and active extensions (e.g. Extension:AutoLink is no longer maintained).

Here's the MediaWiki list:

New Licenses: FREE
Free updates: Yes
Pages indexed by forum search: No
Automatically create links: No
Store link data: Yes
Syntax uses BB-Code: No

Pages use tabs: Yes
Post comments: No (a talk page isn't the same as individual user comments)
Show comments below: No
Multiple Discussions: No
Collapsible sections: No
Split content: No
Auto-TOC: Yes
Fully parsed preview: No

Editable by multiple users: Yes
Edit paragraphs: Yes
Protect pages: Yes
Blacklist titles: Yes
Pages show list of contributors: No
Create categories: Yes
BB-Code variables: Yes

List of all edits: Yes
Fully parsed versions: Yes
Compare two edits: Yes
Approve edits: No
Revert a page: Yes

Post reusable attachments: Yes
Easily find, insert, upload: No
View, compare, undo: Yes

Write pages in any language: Extension required
Translate pages: Extension required
Easily switch between translations: No

Keep your pages organized in multiple areas: No
Use prefixes to keep similar pages unique: Yes
Icons show new articles, comments, edits: No
Place wiki content on other forum pages: No
Moderation tools for handling multiple pages simultaneously: No
Anonymous pages allow stand-alone pages: No

Create synonyms: Yes (VaultWiki also lets you create them in reverse, and set expiration)
Create templates: Yes
Integrate templates with content using arguments: Yes

Customize keyword-rich URLs: Yes
Makes use of canonical URLs and 301 redirects: Yes
Use RSS syndication to keep users informed: Extension required
Promote wiki content with Facebook: No

Add pages to Books: No
Read book collections with simple navigation: No
Place chapters in any order: No

View statistics: Yes
Look up recent edits: Yes
Pages meeting various criteria: Yes

List of edits made by any user: Yes
User contributions in user's profile: No
User can have wiki preferences: Yes
Utilize wiki usage data for trophies or other promotions: No

Users can subscribe to pages or discussions: Yes
Users can organize their subscriptions: Yes
Notifications can be sent instantly, daily, weekly: Yes

Pages maintained by group members: No
Private pages for group members: No

Control CSS for each forum style: No
Change image paths for each style: No

Quickly jump to other wiki pages: Yes
Watch recent wiki activity live: No
View technical analysis of each page: No
Find similar or related wiki content: No
Customize the sidebar: No
Use wiki sidebar in forum sidebar: No

Specify which Special pages each usergroup can access: No
Allow usergroups to edit, protect, and undo edits: Not forum usergroups
Define moderators to manage new and existing content: Yes

Import wiki information seamlessly: Yes
Various settings let you fine-tune look and feel: Yes

Fully phrased using the forum language system: separate system used
Developer hooks through forum plugin system: separate system used

[thincom2000]

A note on the MIN_PACKET (minimum max_allowed_packet value). vBulletin support has in the past recommended at least 32M, and sometimes as much as 128M, to prevent MySQL gone away and other packet-related database errors.

Some users are still using default or host-restricted packet values of 1M, 2M, or even 500K. VaultWiki now uses a dynamic minimum, calculated based on your current forum and expected query size.

The most packet-expensive query in vBulletin is the one that caches phrase translations in columns on the language table. Rather than do this one column at a time, it updates all the columns at once, which quickly uses up all available packet space.

To determine the requirement, VaultWiki builds this query without executing it, and calculates how many bytes it will transfer. If the current max_packet is exceeded, or only has a small margin, then VaultWiki will refuse to install.

If this happens, your only option is to upgrade your max_allowed_packet. There is nothing VaultWiki can do to improve this - as I describe above, max_allowed_packet errors are due to a design flaw in the vBulletin language system.

[thincom2000]

The first post is now updated: you can purchase Ad Removal and Branding Removal for VaultWiki Lite from the official site. If you need help installing or upgrading, you can also purchase install or upgrade services from the main site. Previously these options were only available for licensed users, but now they are available to anyone, including Lite users.

If you do purchase one of these extras, you would have to always download it from there in the future, because the Members area will automatically remove those elements for you, and the ZIP attached to this thread will not.

[thincom2000]

I'm trying to install VaultWiki Lite, but I get a blank page after I sign in.
Make sure your PHP version is at least 5.3. VaultWiki's source code won't parse on lower versions.

A blank page is usually due to a PHP error, but you have errors hidden. You will have to turn on 'display_errors' in your php.ini file to see them. But I suspect that the error you see is due to your PHP version being too low.

If it is, we need to create a bug report, because you should AT LEAST be able to reach the screen that says your site doesn't meet the PHP requirement.

[EliasAlucard]

Make sure your PHP version is at least 5.3. VaultWiki's source code won't parse on lower versions.

A blank page is usually due to a PHP error, but you have errors hidden. You will have to turn on 'display_errors' in your php.ini file to see them. But I suspect that the error you see is due to your PHP version being too low.

If it is, we need to create a bug report, because you should AT LEAST be able to reach the screen that says your site doesn't meet the PHP requirement.I'm on PHP 5.4... and no, I didn't get that far. Just the sign in and then blank.

By the way, is it possible to export VaultWiki's article database to MediaWiki? You know, if I'd change my mind later.

[thincom2000]

Any VaultWiki > MediaWiki tool would be a lossy conversion, since there is a lot of functionality and page types that simply don't exist in MediaWiki. We have not written something like this, but we do plan to eventually have a generic export tool that would export XML or something like that. It is not high on the priority list right now, as it's not one of those every-day features that our users ask for.

Even so, we still have to do some research to see if there is a mostly loss-less format that other wiki software might be able to import.

From what I have seen, it's rare for any software to provide an export function to a competing software. For example, if you search online for a MediaWiki exporter to Dokuwiki, what you will find is:
- a Dokuwiki function that imports MediaWiki
- third parties that wrote scripts to do this
However there is not a script within MediaWiki itself to do this.

If we expect that most software and VaultWiki continues to follow this model, I am not aware if MediaWiki or other potentially intermediate software currently includes a function to import VaultWiki data.

As far as the blank page, it really sounds like a PHP error. You will need to track down the error message by enabling 'display_errors' or viewing your error logs. Once you have the error you can report it here or the VaultWiki site. The VaultWiki site has faster response time.

[thincom2000]

Just wanted to note that I uploaded a new ZIP today. Technically it's the same version, but a lot of issues getting the installation/un-installation process to run smoothly are fixed.

For example, previous versions of the ZIP could not be extracted using the WinZIP client, and there were fatal errors whenever cron jobs tried to run. These are now resolved.

Also, starting with the new upload, the Javascript will be minified from now on. If you want access to the un-minified Javascript, please download VaultWiki Lite from the main support site since you can choose your download settings there.

[thincom2000]

What happens if the main author/developer dies in a car accident tomorrow, for example? Who will maintain the proprietary source code? VaultWiki will die out in such a scenario.

VW's vBulletin integration is very compelling, but I think the best thing thincom/pegasus can do, is go GNU GPL v3 and ask for donations. I and many others would happily and much rather, fund VaultWiki with such an approach.
We have heard your concerns and there is now a sub-section in the current EULA to cover this:
In the event of compulsory liquidation of ownership, currently Cracked Egg Studios, LLC, on the grounds that the number of members falls below the minimum prescribed by statute, the Software shall thereafter be released to the community under the GNU General Public License version 3 to continue the project and do with as they please.
This has also been a serious concern of ours, because VaultWiki was created under similar circumstances to what you describe. The owner of a software called NuWiki mysteriously disappeared, and because of a proprietary EULA, myself and a few other users of that software pooled our resources to create VaultWiki from scratch. We don't want VaultWiki to die out, even if we do.

But of course, while we are alive we would like to profit from it if we can.

Cracked Egg Studios, LLC is a publicly registered company, so you can with a little research find out if all of ownership suddenly dropped dead at once, like during a suspicious period of inactivity.

[thincom2000]

The Lite version of Gamma 6 has been posted today, above.

(released June 8, 2014)

Status Icons are now Font-Based
Serious error fixed: removing old revisions deletes the entire page
Fixed Bug: race condition - AJAX requests occur before AJAX params are ready
Fixed Bug: bbcode does not have options field in Lite version
Fixed Bug: index URL caches with guest session attached
Fixed Bug: invalid index URL for guests with cookies disabled
About 30 other bugs that weren't limited to vBulletin are fixed

[ywwz]

Ah.... I got this when trying vault/install/index.php

Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home3/name/public_html/mywebsite/forum/vault/core/model/vw.php on line 308

My PHP version is 5.4.29
What should I do ah@@

[thincom2000]

You might have PHP 5.4.29 installed on your server as you say, but apparently your server also has PHP < 5.3 installed, and it is using that instead for vBulletin. You will have to make sure in your Apache, nginx, or other config, that it is using the correct path to the PHP 5.4.29 binary when a .php request comes in.

If you maintain multiple versions of PHP, it is usually easier to keep track of this if the PHP path has the version number in it. But I have found that it is sometimes possible to update the wrong PHP location if you forget to set your prefixes properly when you compile the update.

If this error did not occur, then the loaded page should tell you that the PHP version is too low, and the actual PHP version that is executing the page. You can try to get at least that far, so it can give you some clues about your version, by editing vault/core/model/vw.php. Find:
$classname::select_child($class, $file, $depends);
Replace with:
call_user_func_array(array($classname, 'select_child'), array(&$class, &$file, $depends));

[ywwz]

You might have PHP 5.4.29 installed on your server as you say, but apparently your server also has PHP < 5.3 installed, and it is using that instead for vBulletin. You will have to make sure in your Apache, nginx, or other config, that it is using the correct path to the PHP 5.4.29 binary when a .php request comes in.

If you maintain multiple versions of PHP, it is usually easier to keep track of this if the PHP path has the version number in it. But I have found that it is sometimes possible to update the wrong PHP location if you forget to set your prefixes properly when you compile the update.

If this error did not occur, then the loaded page should tell you that the PHP version is too low, and the actual PHP version that is executing the page. You can try to get at least that far, so it can give you some clues about your version, by editing vault/core/model/vw.php. Find:
$classname::select_child($class, $file, $depends);
Replace with:
call_user_func_array(array($classname, 'select_child'), array(&$class, &$file, $depends));

Thank you so much for your professional help, I'll try these code first and contact my site hoster if necessary. All the best!

[thincom2000]

The Gamma 7 version of VaultWiki Lite has been posted today, above. Here are some details of the release:

(released July 1, 2014)

HTML5 MicroData in Wiki Pages
vw_additional.css for easier CSS overrides
Opt Wiki Areas In/Out of Web Search Results
Improved CSS caching
CSS separated into multiple templates for easier management
fatal error searching wiki content in vB3
word wrap occurs in CODE blocks
word wrap is not multi-byte safe
About 25 other bugs that weren't limited to vBulletin are fixed

[halkum]

Getting this error when installing:

Fatal error: Configuration: You must insert a value for dirs.core in /vault/core.php in /home/uta/public_html/forum/vault/core/model/vw.php on line 109

Looked and there is no core.php in my vault folder.

[halkum]

Nevermind, I was running PHP 5.2. Updated and looks to be working correctly now.

[halkum]

Running PHP 5.4 currently.

VaultWiki has been installed. I have yet to do any post installation configuration though. It seems when the VaultWiki plugin is enabled on my forums, suddenly BBCode does not display correctly on the forums. It just shows the tags around the text.

I disable VaultWiki, and suddenly BBCode parses correctly.

Screenshot of example of what I mean attached.

[thincom2000]

I cannot reproduce the problem on my Lite wiki. If you can, I would advise you to submit a Support Ticket through the Members area at vaultwiki.org, so that a developer can resolve this for you.

[thincom2000]

Getting this error when installing:

Fatal error: Configuration: You must insert a value for dirs.core in /vault/core.php in /home/uta/public_html/forum/vault/core/model/vw.php on line 109

Looked and there is no core.php in my vault folder.
The error message refers to an incorrect file name, but the message means that VaultWiki is having trouble automatically finding your vBulletin root directory.

If you had some sort of open_basedir restriction which jails PHP to the vBulletin directory, this would be confusing to VaultWiki. However, from the error message, I don't see such a restriction.

If you have a Windows server with PHP 5.2.4 - 5.2.6 installed, the behavior of the PHP function realpath is inconsistent in this environment. In all PHP versions below 5.3.0, realpath randomly fails to return a value, and in 5.3.1, it only works in some cases.

I have logged a bug report (https://www.vaultwiki.org/issues/3846/) at vaultwiki.org so that the developers can implement a workaround for these versions. Even if your PHP version is too low, VaultWiki is supposed to load far enough to tell you "your PHP version is too low"...

[thincom2000]

Release Candidate 1 has been posted today. Here are some of the changes in this release:
(released July 28, 2014)
History updated: more detailed and user-friendly
Fixed setting rebuilds in Debug Mode
Fixed fatal error subscribing via tab
Fixed sample area being invisible
Fixed signatures failing to parse
Fixed database error previewing new pages
About 35 other bugs that weren't limited to vBulletin are fixed

[BenOwns]

hello,
thanks for the product...

but i cannot create any sections without purchasing?
i noticed that you cannot do much of anything except use the wiki as a blog pretty much unless you pay... any chance of that changing?

[thincom2000]

My understanding is that the Lite version is supposed to be like a "trial version" where most things are only possible if you pay. However, you should be able to create basic articles, link them all together, and view their change histories.

If you're having trouble performing a simple task, it might be a bug in the Lite version. If you can be more specific about the steps you are attempting, I can try to reproduce the problem and come up with a fix.

[BenOwns]

I am just going in to the admin side and trying to create sections to see how it all works out. but no options for itl

[thincom2000]

VaultWiki 4 RC 2 is available today. For Lite users, it includes a bunch of stability improvements, as well as a new feature: users can give Reputation for wiki comments.

For a full list of the changes in RC 2 (not only for Lite users), see this snapshot from the tracker: https://www.vaultwiki.org/projectsearch.php?do=viewreport&issuereportid=30

[thincom2000]

Just posted the update to Lite for VaultWiki 4 RC 3, which has been out 2 weeks now. It seems to have been a pretty stable release so far, so RC might be over soon. Even so, RC 3 did not change much compared to RC 2 when looking at the Lite version. It would seem that most of the core features are already pretty stable, and that mostly non-Lite features have been having problems.

Here's some of the relevant bits for Lite:

(released September 23, 2014)

Fixed dynamic scripts always loading from CDNs
Fixed a lot of missing phrases
Fixed blank moderator notifications
Fixed integrity of moderated content
About 35 other bugs that weren't limited to vBulletin (or Lite) are fixed

[croft]

Getting this error when trying to install it.

Step 4
Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING, expecting ')' in /hermes/waloraweb030/b1466/moo.dabevecom/forum/vault/core/controller/install/db/insert/bbcode/vb3.php on line 78

Fatal Error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING, expecting ')'

vw_CP_Progress_View->handle_fatal_error()

[thincom2000]

Thanks, I'll upload a new package tonight.

EDIT: Newer package uploaded.

[thincom2000]

This was posted to Twitter moments ago:

"While debugging our @MediaWiki importer, we discovered that upgrades from Lite left users in non-upgraded state. Users who upgraded from VaultWiki Lite during RC should contact support for a data integrity review."

Support is currently working on an alternate upgrade path to resolve affected installations without performing a re-install.

[thincom2000]

Updated the thread here with 4.0.0 RC 4 Patch Level 1

(Released October 30, 2014)

Fixed wiki_ajax.php DDoS vector
See: https://www.vaultwiki.org/articles/160/

Also: 4.0.0 RC 3 Patch Level 2, 4.0.0 RC 2 Patch Level 2, 4.0.0 RC 1 Patch Level 2

[alfieb]

Tried your product. Liked what I saw at first, but it broke my forum. I don't know if it was a conflict or what, but BBcodes simply did not work on the forum anymore.

Image codes did, but everything else did not. Tried disabling the VaultWiki, and even that didn't fix the problem, so I had to uninstall it entirely, and everything went back to normal.

Like my friend EliasAlucard, I like the concept of VaultWiki because I want full integration without having multiple databases and user accounts. Since there is no MediaWiki bridge for vB4, I suppose I'll just go without a Wiki for now.

I hope that I am able to reinstall it again in the future.

[thincom2000]

If VaultWiki breaks your site, submit a ticket through the Members area of the VaultWiki web site, and the devs will usually try to fix both your site and VaultWiki for free.

[thincom2000]

@alfieb, thanks for reporting that issue with BB-Code parsing. It only occurred in the Lite version.

In vault/core/model/tag/vw.php, find:
$boolean = false;
Replace with:
$boolean = true;
I have uploaded a fixed ZIP now.

[alfieb]

Tried again. Fresh install. Replaced the vw.php file. BBCodes are still broken.

The issue seems to be related to that file, because I was able to disable the plugin and delete that file, and now my BBCodes work without having to fully uninstall like I did the last time.

[thincom2000]

I don't know then. It works on my install with the new file. If you still have issues, then you will definitely have to request Ticket Support service as it's probably a conflict with another mod or a cache issue on your site.

[Areku]

How do i install it?

README says:


Installation
------------
1) Follow the instructions at:
https://www.vaultwiki.org/manual/vaultwiki-4-manual


but


Error 404 - Page Not Found
The requested page http://www.vaultwiki.org/manual/vaultwiki-4-manual cannot be found.

[thincom2000]

Thanks for reporting that issue. That URL should now redirect you to the correct location.

[Gadget_Guy]

When will you have the V4 documentation on-line?

We installed the paid version a couple days ago but we are confused as to how to properly set it all up and maintain it.

D.

[thincom2000]

Someone is currently working on it. We wanted to have it ready at the same time as our gold release (which is the next release). I will see what I can do to accelerate this process and hopefully have it online before the holiday.

In the mean time, if you have a question about performing a specific task, I would be happy to answer it for you.

[thincom2000]

VaultWiki Lite is now gold/stable with 4.0.0 (released January 1, 2015)

Content Feeds for Showcasing Wiki Content
Fixed URL rebuild not clearing post cache
Fixed Javascript breaking with PHP Suhosin patch
Fixed some illogical permission stacking for wiki headers
Fixed 'Patch Level' in version name breaks forward compatibility
Fixed notifications not sending in various situations
Fixed various PHP notices
Fixed admin panel suggesting install-dir removal during upgrade
Fixed can't WIKI link to the index
Fixed DDoS still possible within small window
Fixed race condition in permission cache
About 40 other bugs are fixed

[AkibaWorld]

Hello! I installed your wiki and I dont know why but it works HORRIBLE on my vb4

I want to unistalled because the the wiki I dont know how, but it disabled the BBCODES, and all my posts are in html right now...

The problem is that the link that you give to the people for uninstalling it doesnt work... Please can you helpe with that? Thanks.

[thincom2000]

There aren't that many code changes in today's update. It's mainly a re-upload because some required files were missing from the last upload.

Let me re-iterate for users STILL experiencing the disabled-BB-Code issue. I cannot reproduce this issue on my test board. If you are experiencing this issue, I recommend setting up a test board that has this issue and filling out a Support Ticket over at the VaultWiki support site. It cannot be addressed without access to a board that has the issue. We have tried multiple times now to resolve this just by guessing what might be happening, and some users are still reporting problems, even on new installations. So if you have this issue, a Support Ticket is needed.

[leemart44]

Just wondering where the xml file is for it

[thincom2000]

There is no XML file. vBulletin doesn't support multi-page install XML which is needed for better installation performance, so you must run /vault/install/index.php in order to install it.

[leemart44]

Thanks for the info

[thincom2000]

Just posted: VaultWiki Lite v4.0.1 (released January 28, 2015)
Fixed cached forum content showing as unparsed
Fixed fatal error viewing discussion with comment by a deleted user
Fixed missing error handling for some admin panels
Fixed WYSIWYG editor using wrong character encoding
Fixed global feeds only editable by moderators
Fixed cron cleanup not using indexes
Fixed feed content not adhering to search engine rules
Fixed fatal error with some custom VW_DEPS_PATH values
Fixed inability to name wiki content '0'
Fixed CSS with PHP Suhosin path
Fixed unexpected last-info for some update types
Fixed some caches empty after install
About 70 other bugs are fixed

Let me reiterate for everyone that the forum BB-Codes showing as unparsed is now fixed! This was occurring for some installations after the first-reading of a post if the forum had a post cache lifetime > 0 and the lifetime had not yet been reached for that post. @AkibaWorld @alfieb @halkum

[leemart44]

lite version is basically a demo as most features are turned off, so basically useless.
But I guess that's how these lite versions are, to get us to buy full version

[AkibaWorld]

Hello.

Yes, the BB-code problem is solved, thanks. But I find some erros and I posted them here, on your website.

Link: https://www.vaultwiki.org/issues/4151/

I want to tell to everybody that this mod is very cool and easy to use, but you need to improve some things.

Congrats for the mod.

[thincom2000]

Today's update is not a new version, just some small changes for 4.0.1. Most notably there was a conflict with vBulletin 4.2's Mobile Style that is now resolved.

[thincom2000]

Regarding the security vulnerability announced here: https://www.vaultwiki.org/articles/168/

The vulnerability does not affect Lite versions. If you're using the full version, you should install one of the patches mentioned in the article.

[thincom2000]

VaultWiki Lite 4.0.2 (released March 15, 2015)
Open Graph Integration
Updated to YUI 3.18.1
Fixed race condition in Javascript
Fixed database error viewing allowed child in disallowed parent
Fixed permissions for feeds too lax
Fixed public facing patch numbers
Fixed issues with low PCRE recursion and backtrack limits
About 75 other bugs are fixed

Among the issues that are fixed in 4.0.2 is a newly discovered permissions vulnerability (users can do things admins expect them not to) that was introduced with the Feeds feature in 4.0.0.

[tjournals]

I am having a problem accessing vaultwiki.org to purchases the pro version. I checked it out on http://ismysiteworking.com and it said the site was down.

edit: site is back online, so nvm


edit: and now it is down again, not sure why one moment I can use your site and the next I can't...

[thincom2000]

Pursuant to the announcement of this vulnerability: https://www.vaultwiki.org/articles/171/

I have updated this thread with the patched version.

[thincom2000]

Updated this thread with 4.0.2 Patch Level 2, which fixes a vulnerability affecting installations on vBulletin 3. Part of a multiple-disclosure here: https://www.vaultwiki.org/articles/172/

[thincom2000]

Update: VaultWiki Lite 4.0.3 (released April 13, 2015)
AJAX Icon Previews
Persistent popup menus
Updated SSL certificate when fetching external content
2 vulnerabilities resolved
About 25 bugs are fixed
Full announcement here: https://www.vaultwiki.org/articles/173/

[thincom2000]

Finally got our new vulnerability database up-to-date with all known disclosed issues: https://www.vaultwiki.org/pages/Book/Documentation/Info:Vulnerable-Versions

If you aren't always able to keep up with our news announcements, you can use this page to see if the VaultWiki version you're running is vulnerable. By clicking that version, you can read more about the specific vulnerabilities and if any workarounds are unavailable.

[drsmash]

how to download the new version of vault wiki

Version Info
Installed Version
v4.0.3 Build 001
Latest Version Available
VaultWiki v4.0.3 Build 002- Now

[drsmash]

there is a problem when trying Rebuild Content URLs

Database error in vBulletin 4.0.5:

Invalid SQL:
TRUNCATE TABLE `vw_path`;

[thincom2000]

there is a problem when trying Rebuild Content URLs

Database error in vBulletin 4.0.5:

Invalid SQL:
TRUNCATE TABLE `vw_path`;
There is nothing "invalid" about that SQL statement. Is there more to the error message?

[thincom2000]

Update: VaultWiki Lite 4.0.4 (released May 21, 2015):
Filter Search by Page Type
Fixed feeds not appearing in search, activity stream
Fixed a few race conditions
Fixed feed chooser on Promote tab
Fixed some errors in live search results
About 35 other bugs are fixed

The Lite version was not affected by "Photo of Loris" or other vulnerabilities disclosed on May 21, so this is just a regular maintenance release.

[e24h]

Just posted the update to Lite for VaultWiki 4 RC 3, which has been out 2 weeks now. It seems to have been a pretty stable release so far, so RC might be over soon. Even so, RC 3 did not change much compared to RC 2 when looking at the Lite version. It would seem that most of the core features are already pretty stable, and that mostly non-Lite features have been having problems.

[thincom2000]

RC 3 was released last September. I would recommend updating to a newer release.

[Mark.uG]

Adding data to table: vw_page

Creating required and example areas
Database Error Database error

Invalid SQL:
UPDATE `vw_counter` SET `editcount` = CASE `pageid`
WHEN 3 THEN editcount + 1
END WHERE `pageid` IN (3) LIMIT 1;

MySQL Error : Unknown column 'pageid' in 'where clause'
Error Number : 1054

[thincom2000]

Adding data to table: vw_page

Creating required and example areas
Database Error Database error


Invalid SQL:
UPDATE `vw_counter` SET `editcount` = CASE `pageid`
WHEN 3 THEN editcount + 1
END WHERE `pageid` IN (3) LIMIT 1;

MySQL Error : Unknown column 'pageid' in 'where clause'
Error Number : 1054
I've uploaded a more recent build which should resolve this issue for users who are encountering it.

If you get a message like "A node with the title Wiki was not found" after installation, you will need to reinstall, as there was a compatibility issue for MySQL < 5.6.4 in the last ZIP, which prevented the wiki tree from being created.

[conradk]

4.2.3 + VaultWiki Lite 4.x, After installed/enabled, Advanced Search page appears white. Disabling VW returns functionality.

Also was confused as to how to get a similar 'index' page that is shown in the first screenshot. Only showed the primary Wiki area, and no other content.

[khalled]

can i place adsense code inside Wiki content pages

[khalled]

i get the following erro after install and try access my forum
Fatal error: Call to a member function is_cloud_cachable() on a non-object in /home/..../public_html/vb/includes/block/tagcloud.php on line 136

and when disable the forum all run good

[thincom2000]

For the tagcloud.php fatal errors, or a blank screen on search.php, run the following MySQL query:
UPDATE contenttype
SET cantag = '0'
WHERE class = 'vwPage'
LIMIT 1
After this change you may have to go to AdminCP > Maintenance > Clean System Cache. If you don't have this option, try running VaultWiki's upgrade script, even if you are already on the latest version, since the upgrade script will rebuild the cache too.

[e24h]

can i place adsense code inside Wiki content pages

[thincom2000]

You can place your adsense code anywhere you want by editing the templates in vBulletin's style manager. A good template to place ad code is vw_node_shell, because it is used on every wiki page.

In the full version, you can also place one in the sidebar by doing one of these:
Create a "Custom HTML" type wiki sideblock and put the adsense code as the content.
For long articles, place adsense code in between sections by adding it to the vw_block_separator template.
We recommend that you use ad code that uses DOM methods instead of document.write.

[Vintum]

Anyone know what happens if we have the full version and our license expires?

[Alan_SP]

You don't get access to support and new versions of software. Installed version of software continues to work as before.

After you decide you want to upgrade, you purchase new license and upgrade software to new version.

It's explained on their site.

[khalled]

You don't get access to support and new versions of software. Installed version of software continues to work as before.

After you decide you want to upgrade, you purchase new license and upgrade software to new version.

It's explained on their site.

so i will not return to lit version if i purchase the full version and my license expires

[Alan_SP]

No, full version (whichever it is) continues to work indefinitely. Only problem is if you found bugs that affects you and you can't access support or newer version with this (or those) bug(s) solved.

From my experience, developers are very quick to solve reported bugs and you have one year support upon purchase, so you could say you're pretty safe in having working wiki version on your site, even if you don't ever plan on purchasing additional years of support.

[dougdirac]

I'm currently running VaultiWiki 3.0.11 Lite on vB 4.2.3. I plan to migrate to XF 1.5.

How do I upgrade to VaultWiki 4? What is the order of operations to upgrade and preserve my data to move to XF?

[friendlymela]

This is a good mod

[thincom2000]

Posted 4.0.6 Patch Level 2 (released October 10, 2015)
Fixes a Denial of Service vulnerability that was introduced in 4.0.4

4.0.6 also:
New Feature: Allow Renaming of BB-Code Tags created by VaultWiki
New Feature: refuse to install/upgrade if Zend Opcache is poorly configured
Changed: Merged Syntax Manager settings to BB Code Manager
Fixed Bug: "Unregistered" created "Wiki" in Activity Stream in vB4
Fixed Bug: editor toolbar shows 'Array' and extra separators in vB3
Fixed Bug: list and create buttons are linked to preview length
Fixed Bug: BB-Code button images broken in BB Code Manager in vB
Fixed Bug: tagcloud.php fatal error on some forum pages in lite in vB4
Fixed Bug: reinstall might use old Memcache/Xcache entries in vB
Fixed Bug: improper URL protocol locks admins out on some servers
Fixed Bug: truncated reason input might be invalid UTF8
Fixed Bug: URL resolver doesn't support // protocol
Fixed Bug: base URL starting with // doubles host
Fixed Bug: database error viewing tag cloud in vB4

Since 4.0.5 was not uploaded here, the following also applies:
Fixed Bug: mysql version detection not working
Fixed Bug: editor not word-wrapping in vB4.1.4+
Fixed Bug: quoted text should automatically be updated for expected parser states
Fixed Bug: database error rebuilding URLs in lite
Fixed Bug: sitemaps are missing in vB in lite

[thincom2000]

Posted 4.0.7 (released October 30, 2015)
Permission for Contributions on Profile
Style Properties for Wiki Icon Colors
Fixed database error creating BB-Code with blank varname
Fixed possible duplicate entries in area listing
Fixed new wiki content not being indexed
Fixed corrupt pages on activity stream
Fixed database error viewing areas with corrupt contents

4.0.7 includes changes from 4.0.6 Patch Level 3:
Fixed the Plagiarizer Vulnerability (HTML/Javascript injection via Permissions escalation)

[thincom2000]

Two recently disclosed vulnerabilities in 4.0.7 (Template Usage and Template Expansion) do not affect the Lite version, but Node Overload affects Lite since 4.0.0. See: https://www.vaultwiki.org/articles/181/

I have uploaded the Lite version of the patch. We recommend updating immediately.

[iiioroh]

Database error in vBulletin 4.2.3:

Invalid SQL:
SELECT * FROM `bbcode` WHERE productid = 'vaultwiki';

MySQL Error : Unknown column 'productid' in 'where clause'
Error Number : 1054
Request Date : Wednesday, December 2nd 2015 @ 03:25:16 AM
Error Date : Wednesday, December 2nd 2015 @ 03:25:17 AM
Script : http://***.ru/vault/install/index.php
Referrer : http://***.ru/vault/install/index.php
IP Address : 109.110.42.69
Username : Anton Fisher
Classname : vB_Database_MySQLi
MySQL Version : 10.1.8-MariaDB

[thincom2000]

Database error in vBulletin 4.2.3:

Invalid SQL:
SELECT * FROM `bbcode` WHERE productid = 'vaultwiki';

MySQL Error : Unknown column 'productid' in 'where clause'
Error Number : 1054
Request Date : Wednesday, December 2nd 2015 @ 03:25:16 AM
Error Date : Wednesday, December 2nd 2015 @ 03:25:17 AM
Script : http://***.ru/vault/install/index.php
Referrer : http://***.ru/vault/install/index.php
IP Address : 109.110.42.69
Username : Anton Fisher
Classname : vB_Database_MySQLi
MySQL Version : 10.1.8-MariaDB
It is not clear from your post where this was a fresh installation or an upgrade. If it was an upgrade, what was the version before the upgrade? You have also provided the error message out of context. What is the rest of the output from the progress window?

You may have noticed that it took a long time to respond to your post. There are much faster response times on the support site.

[thincom2000]

VaultWiki.org was recently hacked. If you have an account on their forum, you might wish to read the disclosure: https://www.vaultwiki.org/articles/183/

[thincom2000]

Uploaded VaultWiki Lite 4.0.8 Patch Level 1, which includes changes from the following releases:

- 4.0.8: https://www.vaultwiki.org/articles/182/
- 4.0.8 Patch Level 1: https://www.vaultwiki.org/articles/186/

These were originally released December 24, 2015 and January 21, 2016, respectively.

Most notably, this release fixes 3 security vulnerabilities which affected the Lite version:
- Balloon Vulnerability
- Relative Vulnerability
- Bulk Overload Vulnerability

[thincom2000]

To check for product updates, it uses a built-in version checking function because the function vBulletin gives doesn't work for the VaultWiki version numbering system. (Some VaultWiki versions have 8 points and vBulletin's version function only supports 5 points).

The version number lookup is considered to be "external content"
This lookup does not load HTML content from any external source, it just asks for the numbers.
The lookup validates the external server against a bundled trust store, so it will never communicate with a different server for example if someone else buys the domain name in 20 years.

You cannot disable that, no. Once per 24 hours it checks if there is a newer version and shows an alert to admins if there is.

If you are really concerned about the "external content" flag, I would compare it to something else: the full version adds support for Facebook Share/Like, bookmarking, etc. These functions are also considered "external content" by how they work.

[thincom2000]

Updated the ZIP with 4.0.9, released March 2, 2016:
upgrade might skip number of steps from previous upgrade
can't create global feeds if not allowed to make personal
platform upgrade doesn't trigger wiki upgrade when needed
possible schema mismatches when reinstalling
multiple issues with search in vB3
inconsistent parsing of images/videos in vB4
multiple style issues in vB3
fatal error using HTML BB-Code in vB4.2.3
fatal error saving wiki CSS in PHP 7
legacy postbit setting not used for wiki comments
About 70 other bugs were fixed

[thincom2000]

Updated the ZIP with 4.0.10, released April 1, 2016:
Page Statistics in Content Lists
Inline Moderation for List Previews
Navbar Quick Links to Create Wiki Content
Style Variables for Icon Sizes
Fixed MySQL deadlocks
About 50 other bugs were fixed

[donnyaz]

Is there any chance you will be making a version for VB5 ?

[thincom2000]

vBulletin 5 adoption rates are still very low (less than 2% of all vBulletin sites): https://tools.digitalpoint.com/cookie-search
Until this number improves, there is little incentive to invest in making a vB5-compatible release.

[thincom2000]

Uploaded 4.0.12. This thread had not been updated since 4.0.10, so the ZIP covers 2 versions.

Changes in 4.0.12 (released June 12, 2016):
Admin Alert of Disabled Wiki
Permissions Editor Shows Inherited Permissions
Show Contributors on Content Lists
Style Consistency with Forum and Thread Lists
Fixed wiki content missing from sitemaps
About 40 other bugs were fixed

Changes in 4.0.11 (released May 14, 2016):
View Counters for Individual Edits
Fixed Font-Awesome in PHP < 5.4.7
Fixed invalid permission cache for guests on non-wiki pages
Fixed multiple Wiki Moderators groups after re-installing
Fixed approval/denial conversations in some cases
Fixed fatal error viewing feeds with entries by deleted users
Fixed read-states
About 40 other bugs were fixed

[EmjayJR]

Thanks OP. You updated it in last June. Does this work with VB 5?

[X-or]

The most important thing to me is : does it feature a fully working mediawiki dump and images importer? Mostly pages (with their whole format, templates, pagelinks, images, galleries, etc...) and the whole categorization. And what version of mediawiki should I import from? I really need to know if I should expect a lot of formatting bugs in articles imported from mediawiki dumps.

Thank you :)

[thincom2000]

Thanks OP. You updated it in last June. Does this work with VB 5?
This does NOT work with vBulletin 5.

The most important thing to me is : does it feature a fully working mediawiki dump and images importer? Mostly pages (with their whole format, templates, pagelinks, images, galleries, etc...) and the whole categorization. And what version of mediawiki should I import from? I really need to know if I should expect a lot of formatting bugs in articles imported from mediawiki dumps.

Thank you :)
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.

[thincom2000]

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 (https://www.vaultwiki.org/articles/195/) disclosed today does not affect the Lite version.

[X-or]

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.

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. :)

[thincom2000]

Updated the ZIP to 4.0.14.

Changes in 4.0.14 (released September 19, 2016 (https://www.vaultwiki.org/articles/197/)):
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

[thincom2000]

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

[thincom2000]

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.

[thincom2000]

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

[thincom2000]

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

[In Omnibus]

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.

[thincom2000]

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.

[thincom2000]

Uploaded 4.0.20 Patch Level 1, which includes the following:
Unsent instant notifications now expire after 7 days
Fixed VWE-2017-4266 (https://www.vaultwiki.org/pages/Book/Documentation/VWE-2017-4266), a Denial of Service issue in the wiki's static CSS cache
Fixed fatal error on some showthread.php pages
Fixed missing database records for users who registered while add-on was disabled
Fixed some race conditions
Over 250 fixes and improvements since last upload for issues that may or may not have been affecting the Lite version

[Dirks]

I only recently upgraded to the newest version. When I click add new page, it's redirecting me to my forum homepage. Where is the page I just created? Do I need to create a forum and call it a page like I did under the old version?

[thincom2000]

Uploaded 4.0.21 Patch Level 1, which includes the following:
Health information for the Wiki Active setting
Scalability improvements in clean-up tasks
Fixed VWE-2018-4471 (https://www.vaultwiki.org/pages/Book/Documentation/VWE-2018-4471), a Race Condition issue in the wiki's deferred tasks.
Over 80 fixes and improvements since last upload for issues that may or may not have been affecting the Lite version

[Mikep-]

Hi I am getting the following error on a new install:

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 697
#1: vw_Hard_Core::model() in [path]/global.php(37) : eval()'d code at line 25
#2: eval() in [path]/global.php at line 37
#3: require_once() in [path]/forum.php at line 67
#4: require() in [path]/index.php at line 43

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

[thincom2000]

In the AdminCP, go to the Plugin Manager and look for a VaultWiki-related plugin at hook location "global_setup_complete". Edit the plugin and remove the following code:
switch (THIS_SCRIPT)
{
case 'showpost':
{
vw_Hard_Core::model('Plugins/Forum')->showpost_start();
break;
}

case 'showthread':
{
vw_Hard_Core::model('Plugins/Forum')->showthread_start();
break;
}

case 'forumdisplay':
case 'index':
{
vw_Hard_Core::model('Plugins/Forum')->forumdisplay_start();
break;
}
}

[Palidino76]

Your website says the current version is 4.0.23, does that mean this version has an exploit?

[nookta]

there is no upload template