[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]

Originally Posted by Alan_SP

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.

Originally Posted by Alan_SP

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.

Originally Posted by Alan_SP

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]

Originally Posted by EliasAlucard

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 wasn't of much help.

Originally Posted by Zachery

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/Exten...rs_Integration

Or this:

http://www.vbulletin.org/forum/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]

Originally Posted by EliasAlucard

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]

Originally Posted by Zachery

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.

Originally Posted by Alan_SP

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]

Originally Posted by EliasAlucard

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]

Originally Posted by EliasAlucard

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.