VaultWiki News

We are pleased to welcome Castoth to the VaultWiki Team and would like take this opportunity to introduce him to our customers. Beginning earlier this week, Castoth has been creating UI design elements, such as graphics, for use in VaultWiki 4.

Although he is new to the VaultWiki.org site, Castoth has been working with our parent company Cracked Egg Studios, LLC on a number of projects over the years, creating both concept and production artwork, as well as offering his own experience regarding usability. We have been very pleased with his skills, tenacity, and drive for perfection in the past.

He comes from a long line of artists, and we have been lucky to get him right out of school. In previous interviews, I've personally noticed that many seasoned "professional" designers tend to have certain bad habits instilled in them by their firms, deadlines, or misinformation. It's certainly a relief to have someone on our team who is still fresh.

Feel free to drop him a PM, or open a forum thread or two to get him to join in the conversation.

All current and past VaultWiki customers have had new settings added to the Members tab on this site. These new Notification Settings allow users to control when they receive email alerts about updates or their license status.

You can now choose to receive alerts when a new version is released, when a security vulnerability is discovered, and when your license is about to expire.

Previously these alerts were sent to users who allowed site administrators to email them, but these new settings offer more control and allow you to opt out of less important admin-sent emails (i.e. promotions, surveys, newsletters) without risking missing the next update.

With this change, we have also modified the behavior of the "new update" email notifications. In the past, these notifications were only sent to users who had an active license and could download the new version at the time the email was sent. However, we have learned that user behavior is in conflict with the notification's behavior, since many users will let their licenses expire until a new release is confirmed. This particular change makes sure these users are not left in the dark any longer.

All of these notification settings are now automatically on by default for all users who have a valid license, active or expired, and who have not requested in the past that we nullify their license.

Again, if you don't want to receive them, you can disable notifications via the Members tab. If you received a notification in error, please let us know, and we will make sure it doesn't happen again.

VaultWiki 3.0.19 is now available. This release features support for vBulletin 4.2 and updates VaultWiki's navbar tab for compatibility with vBulletin's new Navigation Manager. If you want to use vBulletin 4.2, and you are using an older version of VaultWiki, then it is highly recommended that you upgrade.

VaultWiki 3.0.19 also marks our first release to officially support the PHP 5.4 branch. There may still be corners of VaultWiki that don't conform to the newly enforced Strict Standards, but any that remain can be dealt with on a case-by-case basis.

While we now support PHP 5.4, we do NOT recommend upgrading your server to PHP 5.4 at this time. vBulletin itself is largely broken in such an environment, as are a number of popular modifications, such as vBSEO. You should wait at least until vBulletin announces full support of PHP 5.4 until making that switch.

Regardless of the status of PHP 5.4, VaultWiki 3.0.19 is ready now, and VaultWiki can be installed on your site as soon as you wish.

As part of our policy of rolling out quick support for new versions of vBulletin in VaultWiki, we've begun updating VaultWiki to meet that goal. We've also upgraded the site to vBulletin 4.2, because to be honest, problems with integration are more obvious in a live environment.

Please bear with us as we make the necessary changes, and if you see something strange, please report it.

Most notably, vBulletin 4.2 brings significant changes to the navigation system. For customers currently running VaultWiki, we don't recommend upgrading to vBulletin 4.2 until VaultWiki 3.0.19 is released.

VaultWiki 3.0.18 is out now. This maintenance release contains a number of bug fixes including some critical issues involving edit rollback and moderation. For any sites that utilize the wiki's history functions, which should be most, you should upgrade as soon as possible to avoid accidental data loss.

To fix some CSS class stacking issues, wiki images have also been given a complete style reboot. You may need to adjust the CSS again to get them working with custom styles.

As always, for a list of updated templates and phrases, see: https://www.vaultwiki.org/threads/2109/