pegasus
by Published on October 3, 2010 1:27 PM
This coming December, we plan to release a completely revamped version of VaultWiki, version 4 (previously discussed as 3.1). After considering the number of core structural and stylistic changes involved in the product, we thought a major version change was in order.
In version 4, there will NOT be a distinction between Standard or Premium versions - there will just be VaultWiki 4. Users with a Premium license will automatically have access at no additional charge, but users with a Standard license will have to upgrade before March 1, 2011.
As of March 1, 2011, users who did not upgrade will have to purchase a new VaultWiki license, because the Premium Upgrade option will no longer be available.
As of today, the Standard version will no longer be available for purchase. This should prevent new customers from purchasing it if they have missed this announcement.
As of today, the cost of a Premium Upgrade has been reduced over 30% to $19.99. This is the difference in current price between the Standard and Premium versions, and we believe the most fair way to enforce this change, rather than paying the full upgrade amount.
Reasons for making this change:
- Developing with multiple product levels in mind causes a reduction in productivity for one level or the other, because time must be spent discussing whether new features become globally available or only in Premium. Discontinuing Standard allows us to streamline the development process.
- Because both levels rely on the same core code, except with snippets being removed from the Standard release, Standard has historically been more bug-prone than Premium. Discontinuing Standard prevents QA from testing levels unequally, because there is only one level.
- VaultWiki 4 will install as a completely new product. There will not be an upgrade process from version 3. Instead, after installing, current users would have to import their old data. Again, this goes back to point #1
Despite these changes, users who choose to continue using VaultWiki 3 Standard will still be able to download the product and renew their license in the case of any Patch Level releases. They can continue using the old product on their sites under the terms of the License Agreement.
For those who are not sure how to upgrade, you must log in to your account, and open the Members tab in our site's navigation bar. Find the license you need to upgrade in the list. Below the "Download" link, you will also see an "Upgrade" link.by Published on September 30, 2010 11:15 AM
Last week we released VaultWiki 3.0.4 and 2.5.7 Patch Level 3, and have delayed this on-site announcement until our existing customers could be properly contacted about the patches. These versions address a total of 3 critical security concerns, 2 of which involved possible Denial of Service attacks. Due to this and other showstopper bugs that have been addressed, we recommended that customers update as soon as they are able.
Also in VaultWiki 3.0.4, we have fixed over 40 other bugs, including redirects not caching correctly or showing the correct comments, and AJAX title edits "disappearing" articles. As for functionality changes, the import system now handles article history properly.by Published on August 17, 2010 4:56 PM
Today we released VaultWiki 3.0.3, which addresses a critical security concern. Due to this and other showstopper bugs that have been addressed, we recommend that customers update as soon as they are able.
Also in VaultWiki 3.0.3, we have made a number of changes that we believe will improve performance on a number of boards. One of these changes simplifies processing for Who's Online pages and the display of the user's current location.
A big improvement in 3.0.3 is the vastly increased support for MySQL slave databases. Among other things, Special page data, in-article contributions, and page history are now read from the slave database, if available. When the server and vBulletin are configured properly, this change should reduce locking issues on these more-trafficked tables.by Published on August 3, 2010 10:26 AM
As of this past Sunday, August 1, as was announced last month, new prices on all our products and services have taken effect.
Last week, a security issue was identified in the 2.5.x branch of VaultWiki. At the same time, two (2) security issues were also identified in the 3.0.x branch.
Last Wednesday, VaultWiki 2.5.7 Patch Level 2 and VaultWiki 3.0.2 were released to address each set of vulnerabilities, respectfully. Our customers were notified by email and advised to apply the update.
Not only does 3.0.2 solve 2 vulnerabilities and fix numerous Internet Explorer 6 and 7 style issues, but it also includes some useful new moderation features. Keep in mind that due to the security issues, this release was rushed out before the features could be fully tested, so consider them beta:
History Moderation
Users can now report previous versions of articles to moderators as offensive, questionable, or spam. In the past, moderators could change the current version back to acceptable ones, but the problematic version would remain visible through the article's history. It is now possible to completely remove a bad version from a page's history using the "purge" function.by Published on June 29, 2010 7:42 PM
Today the VaultWiki 3.0.1 maintenance release is available to the public. This contains a rollup of fixes since 3.0.0 and some changes to the database structure that should improve speed on many wiki pages and save actions.
A complete list of changes is here: http://www.vaultwiki.org/projectsear...ssuereportid=6
On August 1, 2010, prices on VaultWiki products and services will be changing as follows:
- VaultWiki Premium: $75
- VaultWiki Standard: $55
- Branding Removal: $60
- License Renewal (active license): $30
- License Renewal (inactive license): $40
- Upgrade Standard to Premium: $30
by Published on June 9, 2010 3:09 AM
Today, what we believe to be a stable VaultWiki 3 release has become available. We recommend that users upgrade as soon as they can, because it fixes an XSS issue in previous VaultWiki 3.x versions.
Partial Rewrite
The product has been reworked to load less data and consume less memory than ever before. This is especially noticeable on non-wiki pages, when few wiki integration features are enabled.
However, this also means that many add-ons that were written for previous versions will not function correctly when used with VaultWiki 3. We recommend disabling any VaultWiki addons prior to upgrading, and updating them at your earliest convenience.
Book Improvements
In addition to a large number of bug fixes, VaultWiki 3 features quite a few improvements to the Book system. It is now easier than ever to create books and add chapters. After creating the Book's start page, simply click the "Add New Chapter" button in its Table of Contents. When the window refreshes, the next few pages will guide you through the process.
You can easily see what chapters are new or have been modified right from the Table of Contents. The color-coded icons that make these distinctions can be customized using the updated GDK.
When a user is subscribed to a Book via Daily or Weekly emails, the user will receive notices when any chapter or sub-chapter within that Book has been added or modified by another user.
More Friendly Comments
Using new settings, it's now possible to move wiki comments from a separate tab to below the article, where they can be read and replied to in a more public position using a minimal number of clicks.
Release Notes
If you already had VaultWiki 3.0.0 RC 3 installed, then the 3.0.0 upgrade process will attempt to move some data from the post table to a new location. If you have a very large number of posts in your forum, we recommend upgrading only after turning your forum off for maintenance.
The data will not be copied in forums with millions of posts, but removing the old data may still take a long time. In this case, any non-wiki posts that used the Parsing Options "Wiki Codes" will have to make their selections again once the upgrade is complete.by Published on May 15, 2010 1:43 AM
Earlier in the week, we discovered a possible XSS vulnerability in all previous versions of VaultWiki. The new releases 2.5.7 Patch Level 1 and 3.0.0 RC 3 contain the changes that fix this hole. Even though this particular vulnerability requires some special circumstances, we recommend updating immediately to ensure you are protected.
Because of this discovery, RC 3 does not contain many of the features that were planned for its release, but it does contain roughly 60 bug fixes. Notably, we improved performance on Special pages, and fixed the subscriptions to daily and weekly wiki edit notifications.
New Directory Structure
The directory structure and file names used by VaultWiki have been changed. To have the smoothest upgrade process and avoid making your forums inaccessible, we recommend:
- Have a copy of the /vault folder from RC 2 ready in case you need to rollback. If you follow these instructions in order, you should not have a problem.
- Disable VaultWiki via the Product Manager in the AdminCP.
- Delete the /vault directory on your server. MAKE SURE VaultWiki is disabled before you do this, or you'll have to replace the RC 2 folder and start over.
- Upload the new RC 3 files.
- Proceed to upgrade normally.
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.