VaultWiki Roadmap

**pegasus** · April 28, 2009

You can always check the milestones for VaultWiki to see what we have planned, and the tentative release dates for those changes. See this page.

**we_are_borg** · January 1, 2011

Pegasus can you give a new time frame for VaultWiki 4.0 the milestone says it overdue, what is the estimate target date at the moment.

**pegasus** · April 3, 2011

Please note that although VaultWiki 4 Alpha 1 was scheduled for tomorrow, we ran into unexpected delays moving the server (back on April 1) and are now roughly 2 days behind. At this time, we still expect to release it before the end of the week.

**Moses** · April 6, 2011

Would this beta be compatiable with xenforo?

**we_are_borg** · April 13, 2011

Pegasus can you provide us with new dates for Alpha 1 testing and what Moses asked will it be compatible with Xenforo and IPS.

**pegasus** · April 13, 2011

I can't provide an exact date for Alpha 1 now. We slated it for earlier this month to coincide with the new CKeditor in vBulletin 4.1.3 but they have delayed that feature until at least 4.1.4. It doesn't make sense for us to release a major product version so soon before a major change like this in vBulletin, just to release a new alpha so quickly once it does. VW 4 Alpha 1 will be released on or around the release of vB 4.1.4, provided that actually contains the new editor.

This delay has given us extra time to work on optimization and other framework updates that we weren't originally planning for Alpha 1.

As has been previously mentioned, XenForo will not be supported before Alpha 2, and IPS not before Alpha 3. Since it is really going to be an Alpha version (we've changed everything about how VaultWiki works), we want to make sure the core works as intended before releasing the extensions for other forums and complicating things.

**ashley76** · April 13, 2011

So it sounds like lots of changes are coming... Will it affect any of our "data" in the wiki?

**pegasus** · April 14, 2011

At this point, we intend to move most data to the new format. Certain features will be easier to use; in most cases this just means you will have to learn the new (easier) way.

Some data will be lost, because these features don't exist in VaultWiki 4 Alpha 1:

Polls that are on articles
Ratings on articles
Post history (for comments) / moderation logs
Thread prefixes, but will be merged onto the title
Domain Manager settings
User access masks for wiki forums
maybe more, this is all I remember right now

**ashley76** · April 14, 2011

Give me an example of Thread prefixes merged into the title?

**pegasus** · April 14, 2011

https://www.vaultwiki.org/demo/test-prefix-DVD
here, the article uses the "DVD" prefix. It has title "test prefix".

In VaultWiki 4, the title would be "test prefix (DVD)", which as you see by the autolink, is equivalent.

**we_are_borg** · April 14, 2011

Thanks for the update Pegasus.

Its really annoying that vBulletin keeps postpone the new editor. It will be a major upgrade so everything that uses the editor should be effected.

**ashley76** · April 14, 2011

okay, so I am really ignorant pegasus... Could you look at my wiki http://www.kordindustries.com and give me an example of something on mine?

**pegasus** · April 14, 2011

If you don't know what it is, then you don't use them, and you won't be affected by that particular change.

There is a section in the vBulletin AdminCP where you create "Thread Prefixes" and add them to "Prefix Sets". These Prefix Sets can be applied on a per-forum basis so that users can (or must, depending on your config) pick one of the admin-defined prefixes when they create a new thread. It is mainly used as another level of organization within a given forum.

**ashley76** · April 14, 2011

Sweet! Thanks for the info and keep up the good work! I look forward to the next version!

**pegasus** · May 20, 2011

vBulletin released 4.1.4 CKeditor yesterday. We will be adding support for 3.0.12 and integrating it into 4.0.0 Alpha 1 as well. We will have 4 out as soon as we can, but of course the priority is updating the current version.