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