VaultWiki News

It's been almost two months now since our last (unannounced) update. Not much has changed in this most recent edition, but a number of minor bugs have been addressed. As always, if you are using the VaultWiki software, we recommend applying the newest update as soon as you can. ...

Two days ago, we released the 2.1.1 update for VaultWiki. It includes a number of small bug fixes and other minor changes that should make, for example, the Protect tab a little easier to understand.

The big new feature in 2.1.1 is the ability to Moderate Edits via the History tab. Who follows edit moderation rules is configurable in the Usergroup and Forum Permissions Managers. 2.1.1 also includes the framework necessary for installing addons like VaultWiki Images. ...

VaultWiki 2.1.0 was released this evening. Users of VaultWiki Categories should update that to version 1.0.2 before rebuilding any caches.

There are several major additions with the newest version. Data managers for links and namespaces allow for easier mod integration and higher performance. A Namespace Manager in the AdminCP allows for easier installation of VaultWiki and more straightforward management of the various namespace settings. The long-awaited Protect tab is now available, allowing for multiple levels of protection for wiki articles. And finally the Special:Search page, which includes a front page that appears when a user doesn't type the title in the URL. ...

We decided to release 4 new features early that were originally slated to be included in 2.1.0. These features are: the Wiki Code Manager, even more improved Forum Marking, Admin Help topics, and CSS that matches default vBulletin's style.

A new version of Categories has also been released, to reflect the changes in VaultWiki since its initial release (some of which Categories necessitated).

Most importantly, we have changed the way the install/upgrades take place, in an attempt to improve performance in this area and also support upgrading from our new Lite version. The Lite version is available to non-paying users who aren't sure if VaultWiki is for them, and thus it basically has no features. It is available at http://www.vbulletin.org/forum/showthread.php?t=189446.

We have also launched a public sandbox at [sandbox removed due to licensing issues], where prospective customers can try out the front-end of the software. AdminCP screenshots have been posted in this thread: https://www.vaultwiki.org/showthread.php?t=1508 ...

It's been a while since the last Release Candidate of VaultWiki. While we had hoped for the build after RC3 to be stable, we did not expect so many bug reports to flood in at the last second. This did cause a huge delay, but we are pretty confident that any remaining bugs would only be minor.

Thanks to your help, we are pleased to announce the stable release of VaultWiki 2.0.0. There are a number of new features in this release that deserve some attention. I'm sure you'll find some on your own, but these may be less obvious.

.PHP-less URLs

We probably all remember the URLs from MediaWiki that can be configured to look like /wiki/ArticleTitle. This is now possible in VaultWiki by simply activating the option (of course you will still need to modify .htaccess to suit your needs).

Article Preview

Previously, Auto Links were the only links in VaultWiki to receive the handy popup previews containing the first few lines of the target articles. This functionality now extends to all links to articles in your wiki.

Advanced Forum Marking

When viewing the forum list, VaultWiki displays Wiki forums with a special icon. Like other forums, if a Wiki forum contains new posts since your last visit, the icon may look a bit different. Unlike other standard forums, the icon may look different still if the Wiki forum contains a new Article.

New TOC Flag

In the stable release, we had to change a number of things about how the Table of Contents is generated in order to support flags with the [toc] BB-Code in cached posts. While we were at it, we added the NONUM flag to remove the chapter numbers from the Table of Contents. ...

I didn't announce the release of RC2, but in my opinion there wasn't much to be said about it. It was a bug fix release.

As for RC3, on the other hand, not only is it a major bug fix release (thanks to everyone who started making reports last week), but also includes two new features (and others that were hidden before).

Editor Wiki Code Buttons

This has been a desired feature for a while now. RC3 adds two more segments to your editor toolbar. The first is a set of buttons for linking to articles in each (important) namespace. Buttons are included for each of Special, Template, Book, and Help, as well as an additional button for your content namespace. Additional buttons for additional namespaces must be created and configured on your own.

The second set of buttons are for non-linking codes and will change depending on whether you are editing an article or a standard post.

Namespaces on Forum Display

Because Namespaces are required to be top-level forums, they cannot be placed in categories, and especially when using Forum Links to set Main Pages, they tend to be an ugly addition to Forum Home. Now, even if your Namespace's Display Order is set to 0, you can use two new forum settings to configure if and how they will display in the forum list.

The first allows you to set a "Display Parent" so you can add them to a Forum Category or another Forum without corrupting your cached articles. The second allows you to set a "Display Name" for the forum or Namespace so that you don't necessarily have to use what shows in the URL. ...