-
VaultWiki News
by Published on January 4, 2010 12:27 PM
Last night, we closed the site for 3 hours while we updated the Members Area for the next installment of VaultWiki. If you managed to purchase any addons before we discontinued them, they will still be available in your Members Area as a separate download. However, beginning with VaultWiki 3.0.0 Beta 1, Premium users will no longer have to download and install them as separate products - Categories, Images, Xpages, and the others have all been packaged together and integrated with VaultWiki's upgrade system.
After 2 months, we're pleased to announce the first VaultWiki release that is compatible with vBulletin 4. vBulletin 4 owners will notice a level of integration that simply is not possible with vBulletin 3 forums, and at least for this first release, will see the majority of new features. We do have new features planned for vBulletin 3 forums, but these will be forthcoming in the next few betas.
Editor Buttons
The first thing many users will notice is the addition of new icons (
, 
, 
) to the editor. Oddly enough, previous releases never had a button for links to the default wiki space. The other buttons remind users that it's possible to add wiki images to your posts, and it's also possible to categorize your wiki content.
Behind the Scenes
Aside from buttons, the most significant change that affects all vBulletin platforms is that we've rewritten several portions of the back-end to improve performance during administrative tasks on the wiki. We've removed a number of expensive database queries from these processes, and portioned the remaining changes to reduce load on the server.
vB4: Search
With the addition of content types in vBulletin 4, we've been able to integrate with the Search in a more user-friendly fashion. Simply selecting the "Wiki content pages" type will display a list of wiki locations for you to search from in a more intuitive interface than VaultWiki for vB3's Special:Search page. In fact, these changes will allow us to integrate Special pages directly with wiki search in an upcoming beta.
vB4: Asset Management
One of the strong points of vBulletin 4 is the brand new Asset Manager, a form that appears when managing attachments that shows all attachments the user has already uploaded, in case they wish to use it more than once, and provides an easy-to-use button for inserting that attachment into the post.
VaultWiki 3 takes this one step further, by adding a new folder to the Asset Manager containing all images that have been uploaded to the wiki's Image space, even if they were posted by other users. Clicking the "Insert Inline" button will place the image in your post using the wiki's Image BB-Code.
vB4: CSS Styling
One of VaultWiki's most powerful admin tools is the Wiki Style Manager, where admins can apply their own CSS rules to meld the wiki seamlessly into their site's existing design. vBulletin 4 made some significant improvements to its own CSS design, which reduced the amount of code VaultWiki had to use.
Additionally, vBulletin 4 introduced the StyleVar Manager, which contains hundreds of variables that control the overall look of the forum. In VaultWiki 3, the CSS has been modified to use many of these StyleVars. This means that VaultWiki will automatically inherit a site's design and should require minimal stylistic changes to achieve seamless visual integration.
Demo and Beta Status
This is a Beta release. Please take the necessary precautions before installing it in a production environment. We encourage users to take advantage of our support forums and bug tracker to help make this product the best that it can be.
Unfortunately, at this time we cannot provide a demo of VaultWiki running on the vBulletin 4 platform (we are still running vBulletin 3.8). While we intend to upgrade in the future, this isn't something we can do until our bug tracker has been ported. We will be adding screen shots shortly to demonstrate the vBulletin 4-only material. ...by Published on October 30, 2009 12:04 PM
The newest VaultWiki release, as always, contains an impressive number of bug fixes. While we don't consider it a feature release, a relatively important feature has been added - UTF-8 support for URLs.
In VaultWiki 2.5.6, if you have UTF-8 support enabled in VaultWiki's settings and the board's language is configured with UTF-8 encoding, the foreign language characters in your article titles will now be included in the URLs. This will make many admins lives easier because you won't need to add entire character sets to their URL replacements anymore (unless you still want to).
This change doesn't render URL replacements obsolete. They are still useful if your board doesn't use UTF-8, and for defining custom phrases and other replacements for your URLs (e.g. '&' => 'and'). It's likely, however, that the ImpEx feature will start seeing less usage - which is ironic, since we have yet to complete it. ...by Published on October 23, 2009 2:03 PM
With the upcoming release of VaultWiki 3.x more imminent, we thought we would let potential customers know that our prices for certain items will be changing on November 23, 2009.
- VaultWiki Premium will return to $60/license.
- VaultWiki Standard will increase to $45/license.
- License upgrades will decrease to $25/upgrade.
As of that day, VaultWiki Premium addons will no longer be sold separately. They will only be available pre-packaged with the Premium license. This will make updating each one more efficient and easier on both ours and our customers' parts.
Customers who have already purchased these items separately can continue using them but they will not be updated beyond this date. If you want to use them with VaultWiki 3, we recommend upgrading to a Premium license after this date (see above, the price drops).
If you're considering purchasing VaultWiki, be sure to do so before the prices go up on November 23. ...by Published on October 16, 2009 12:49 AM
The newest version of VaultWiki, 2.5.5, breaks the pattern from the last few updates by introducing some new and improved features, increased efficiency, and of course a bunch of bug fixes.
Custom Tab API
While not an entirely "new" feature, the API has been improved so that you can add your own custom tabs without modifying any of VaultWiki's templates. See the following example:
Note: This only adds the clickable part of the tab (if placed in hook vault_contentaction_prepare). You will still need to write your own script to load the tab's content and register it at hook vault_showthread_default in showwiki.php.Code:$content_actions['tab_id'] = array( 'href' => 'url?do=tab_id', 'text' => 'tab_label', 'class' => ($vault->postbit['selected'] == 'tab_id' ? 'selected' : ''), // tab_id of default tab that appears immediately before this tab 'custom' => 'ref_id', // true to follow the link when clicked, or // false to load tab via AJAX (default) 'nojs' => false );
Wiki Editor Button Stylevar
You can now set a different path to your wiki's editor buttons for each style. If you wanted to design your own "Book" or "Table" BB-Code icons, now you can do so. At first glance, you may think that the stylevar would conflict with vBulletin's Stylevar for the same purpose, or interfere with your other custom BB-Codes. But the "Wiki" Editor Stylevar will only apply to BB-Codes that have been added to the "Wiki Code Group" in the Wiki Code Manager.
Synchronized Display Order
The Display Order of a Namespace and the Display Order of its "Top-Level" forum are now one and the same. In previous versions, the value displayed in the Namespace Manager replaced whatever value appeared in the Forum Manager. This was especially confusing when trying to reorder the forums. Now the Display Order in both places have been synchronized and can be modified using either form.
Other Changes
The "Discussion" tab now shows the number of posts in the tab's label. Keeping this count in such a visible place (it used to be only at the bottom of the article) should help improve the number of users who click through to read and post comments. ...by Published on September 26, 2009 4:32 PM
Today we released VaultWiki 2.5.4. This is wholly a maintenance release - there are no new features introduced in 2.5.4.
Some changes in 2.5.4 are:
- Improved no-Javascript version of article pages
- Improved line break processing
- Fixed bug where creating new book via Book tab doesn't add the chapter
- Fixed bug where human verification was missing for guest articles/edits
- Click here to see the complete list of changes
by Published on September 22, 2009 5:25 PM
Beginning today, we are giving back to customers who have spread the word about VaultWiki.
Customers who have written reviews of VaultWiki on other sites can contact a member of our staff about extending the duration of one of your licenses for various amounts of time, without purchasing a full year's renewal. Of course, you can still spread the word and receive an extension if you haven't started already.
More details are available here.
Note that as of today, coupon codes discussed in this promotion are no longer valid. If you have existing posts that mention a discount, you should remove that mention. ...by Published on September 10, 2009 1:06 PM
Today we released VaultWiki 2.5.3. Although there were no new features since the last update, we didn't announce it, so to recap: 2.5.2 contained the MediaWiki Importer and an Import/Export tool for URL Replacements, which will allow users to backup their replacements and share them with the community.
2.5.3 is notable because it corrects a number of rather significant bugs:
- Saving the Island namespace disables new posts throughout the forum
- Placing [TOC] at article start creates an infinite loop
- Placing headlines in templates allows editing of non-existent sections
- Saving a parent style's CSS overwrites the CSS in all its children
- Click here to see the complete list of changes
At the same time, we have released updates to the following mods: Categories, Images, Xpages, Parser Extensions. ...
This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
By continuing to use this site, you are consenting to our use of cookies.