Silverstripe CMS 5.0.0 beta1 has been tagged last week. This is an important milestone and gives a chance to developers to start working with CMS 5.
CMS5 work
- Completed the upgrade to the frontend stack of all supported module.
-
Folded the
silverstripe/security-extensionsinto core modules for CMS 5 - Made the silverstripe/webauthn-authenticator compatible with CMS 5
- Fix a CMS5 bug that prevented users from login into the CMS if the mfa module was installed
- Replace thirdparty simpletest in framework for CMS5
- Set the correct version for vendor-plugin and recipe-plugin in CMS 5
- Made a sustained effort to get most of our CMS5 builds green.
- Added a few more modules to our “kitchen sink” test module. This will make it easier for the dev teams to release all supported modules all at once.
- Upgraded our diff library in framework
- Fix a CMS5 issue that was making it impossible to delete an image in an HTML Editor.
- Make the DynamoDB module CMS5 compatible.
CMS 4 patch
Community pull requests merged
As always,a big thank you to community members who raise pull requests to fix bugs or implement new high value features. We haven’t had a lot of time to look at these so far this year while preparing for the beta release, but there were some that got merged:
Work in progress
Now the beta is out, we’re shifting our focus towards stabilising Silverstripe CMS 5. This means doing a full regression on CMS 5 and identify issues that need to be addressed.
We’re also keen to support early CMS 5 adopters. If you get stuck on an issue, don’t hesitate to bring it to our attention by asking a question on this forum. If you think you’ve come across a CMS5 regression open an issue against the relevant repo.