VaultWiki Roadmap

**Alfa1** · April 22, 2015

What is the plan for VW4.1? Will this be the release that makes it irresistible to upgrade from VW3 to VW4?
What compelling features are to be included?

Is this a correct list of features that will be included in vaultwiki 4.1?
https://www.vaultwiki.org/milestones/23/list/

Has work on 4.1 begun?

**pegasus** · April 22, 2015

If anyone is looking for a pressing reason to upgrade, please see: https://www.vaultwiki.org/pages/Book...-Vulnerability
Every version of VW3 contains at least 1 vulnerability, including this vulnerability, which makes it possible for anyone with some basic coding knowledge and internet access to perform a denial of service attack from a single location by exploiting a bug in VaultWiki 3 to consume server resources.

...

We will not announce all new features so far ahead of time, but we can confirm these right now:
https://www.vaultwiki.org/issues/3259/ (also improves autonomy of article headings, performance, MySQL usage, allows merging edit conflicts, and more)
https://www.vaultwiki.org/issues/2634/

We have already laid the ground-work for many of the features on the list you posted. Some of the smaller features that don't rely on major changes might be included sooner (hint).

You should start to see a major push regarding 4.1 and an expanded feature set, now that our recent security audit is complete, the known bugs in 4.0.x are few, and the number of bugs that were found and resolved by the latest release was a very small amount.

I can say that a number of the items slated for 4.1 have already been started.

**Alfa1** · January 21, 2016

Is 4.0.9 imminent? Need the maintenance release as 4.0.8 needs a lot of fixes.

**pegasus** · January 21, 2016

This is what my changelog shows for 4.0.9 (as of this morning):

Code:

Fixed Bug: poor responsive style of area bits on index
Fixed Bug: VW3 import default dependency not applied when target is XF
Fixed Bug: no instant emails for uploads to same subscribed attachment
Fixed Bug: warning when creator/last-editor was a now-deleted user
Fixed Bug: corrupt cached similar block containing invalid UTF8
Fixed Bug: strict standards error on pages exceeding stop limit in vB
Fixed Bug: can't save page containing index link
Fixed Bug: fatal errors saving some wiki CSS in PHP 7
Fixed Bug: no attachment display in comments in vB3
Fixed Bug: missing user info in comments in vB3
Fixed Bug: wiki uses legacy postbit regardless of forum setting in vB
Fixed Bug: wrong position of content list pagenav popup in vB3
Fixed Bug: TOC not collapsible in vB3
Fixed Bug: editor still shows template usage after removing all templates from page
Fixed Bug: missing categories created by link convert in VW3 import don't use edit date
Fixed Bug: notices & notifications missing from header in vB3
Fixed Bug: fatal error viewing RSS in vB3
Fixed Bug: platform upgrade doesn't trigger pending wiki upgrade when needed
Fixed Bug: gracefully handle schema mismatches on reinstall after failed uninstall
Fixed Bug: no New Wiki Updates results in vB3 search

A lot of vB3 fixes.

There were some other things we wanted to put in the release, but as you might expect, we've pretty much lost this week with respect to development time, so it might get pushed to another.

It will not be a month since last build 001 until Monday. I'm not sure yet if the lost week will push it to the following Monday.

If you are aware of other bugs not on this list, please let me know. Compared to the list from 4.0.8, this one is sparse.

Other things I have noticed this month:
- No permission to create global feeds in vB3 (possibly other platforms)
- No navigation when category has over 200 sub-categories (e.g. https://www.vaultwiki.org/pages/Book...-Vulnerability)

Other things that need attention / design changes to resolve (but may now be deferred):
- Re-enable management of pages with more than 500 categories, feeds, tags
- Re-enable management of books with more than 500 chapters, nested sub-books

**Alfa1** · January 22, 2016

I am waiting for these XF issues to land in a release:
https://www.vaultwiki.org/issues/4502/
https://www.vaultwiki.org/issues/4501/
https://www.vaultwiki.org/issues/4504/

**pegasus** · January 22, 2016

If you check the status of those 3 issues, they were all resolved by a later build of 4.0.8.

**Alfa1** · January 2, 2017

How is 4.0.16 coming along? Is it due soon?

**pegasus** · January 3, 2017

4.0.16 has been testing since this weekend. It will be released when it passes.

**Alfa1** · February 19, 2017

Is 4.0.17 near?

**pegasus** · February 19, 2017

We expect 4.0.17 this week. There are still a handful of outstanding issues that need to be resolved.

**Alfa1** · May 26, 2018

How does the roadmap for the coming months look?
Is 4.1 getting close(r)
What will 4.1 entail?

**pegasus** · May 26, 2018

Since 4.1 is approaching, the sidebar on our forum index is updated frequently with the information you're asking about. As of this posting it says:

VaultWiki 4.1.x Progress
A summary of development activity for future 4.1.x, which will add XenForo 2.x support, a small number of minor features, and other improvements.
Activity
Development Time 210 days
ETA ~10 weeks
Currently XenForo 2.x Inline Moderation
Differences Between Future and Current Release are In
Files 2,371 (11.28/day)
Lines of code 238,253 (1,133/day)

The ETA is estimated based on the tasks remaining and the expected time to complete those tasks, assuming nothing else gets in the way (such as the GDPR rollout last week).

**Alfa1** · May 26, 2018

Are any major features scheduled for 4.1? (except XF2 compatibility)

**pegasus** · May 26, 2018

No, major features are not being added for 4.1, with some exceptions:
- Features that are required for XF2 compatibility
- Certain features that already were developed during 4.0 but were never released.

As it is XF2 compatibility (while maintaining current compatibilities) is resulting in a >50% rewrite of existing code. By limiting extra features, we make sure that users aren't kept waiting for another year before they can start using XF2.