pegasus
by Published on February 25, 2009 12:41 AM
With the most recent build of VaultWiki, we encountered the largest and longest running report volume of install problems ever. While the product page had mentioned that the product should be treated as unstable for a couple of days after a new build is released, a couple of days was never intended to turn into almost an entire week.
On top of that, there was no indication aside from a news entry of when the build was released, so customers could only try to figure out in their heads if enough time had passed for the ZIP to be considered reliable. Another option was to look at recent bug reports, and see whether a calm(ing) had been achieved for the most recent version.
However, none of this is sufficient, and a number of very serious bugs had appeared without warning, forcing us to release revision after revision of the software that for many users was impossible to keep up with. In the case of one of these bugs, we were unable to notify all of our customers by email, simply due to technical limitations - our outbox was flooded.
Today we implemented an "Unstable" flag that will appear next to new versions when you select one to download. This will appear when a new build is available and will remain for several days until a small number of customers have reported successful installs. If you don't want to take the risk of installing or upgrading at that time, simply wait for the "Unstable" text to be removed, or install the next latest version.
Again, we are deeply sorry for the confusion and headaches we and the product have caused in the past several days. ...by Published on January 31, 2009 1:58 PM
After another 2 glorious months of development, Cracked Egg Studios has finally released CES VaultWiki v2.2.0. New in this version: a manager to control various wiki settings if you somehow got your forum to work on multiple domain names, a template-based CSS system, and the ability to use templates inside each other.
I know people had been wanting an AdminCP page for the CSS for a while, so hopefully this is exactly what we were all looking for. ...by Published on December 9, 2008 11:38 PM
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. ...by Published on October 12, 2008 3:01 PM
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. ...by Published on September 21, 2008 10:40 PM
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. ...by Published on August 30, 2008 6:42 AM
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 ...by Published on August 7, 2008 7:56 PM
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. ...
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.