VaultWiki 4.1.0 Release Candidate 1

We are pleased to offer a stable proposal for VaultWiki 4.1.x with Release Candidate 1, which is now available for testing. This is the first release to include compatibility with the newest PHP 7.4. In ensuring that compatibility and preparing for stable proposal, we performed a deep scrub of the code in almost all 5000+ files to get it as clean as possible. As a result, this release includes over 170 bug fixes, in addition to the normal amount of style tweaks, and other changes.

Where to Focus

While RC 1 includes mostly bug fixes, some of those fixes involved some late changes that were rather significant. For example, we fixed a long-standing regression that appeared in 4.0.x, where adding pages to categories by embedding them in templates was no longer possible. In addition, we changed some of the underlying database structure for wiki discussions and comments.

Therefore it would be ideal that this round of testing focuses on categories (especially templated ones) and ensures that discussions still work as expected.

Resolved Security Issues

Since beta versions are not subject to the same patching policy as stable versions, the following issues are patched in this release of the 4.1.x branch, 4.1.0 RC 1:

• Issues covered in the January 2020 security update
• VWE-2020-5468, which is a Permissions escalation issue, under which comments on the index don't respect the index's parsing rules set forth in the Area Manager.

Release Notes

Sites running 4.1.x betas should upgrade to VaultWiki 4.1.0 RC 1 as soon as they are able in order to improve stability. VaultWiki 4.1.0 RC 1 is proposed as stable. We recommend that customers test it first, but it should be usable in a live environment if the customer deems those tests successful.

4.0.x Update

At the same time, the latest update in the 4.0.x branch, 4.0.28 is now available, which likewise adds support for PHP 7.4. Since 4.1.x is proposed as stable, this will be one of, if not the last, main update in the 4.0.x branch, aside from security updates. Customers may have already noticed that a number of bugs reported under 4.0.x were fixed in 4.1.x only. If users have not already done so, we recommend to begin making plans to migrate to the newer 4.1.x branch, when you deem it suitable, so you can continue to benefit from the broadest number of fixes and improvements moving forwards.