Work completed in the last couple of weeks
As the beta release for Silverstripe CMS 5.3.0 comes close, our focus has mostly shifted to CMS 6. Because of this you’re likely to see work being completely more slowly, not because we’re working any slower but because the scope of the work we’re doing will tend to be larger.
Bug fixes and other immediate changes
- Updated translation strings
- Various regressions and linting fixes found via CI
- Improved permission scope for CI
- Added rule in CI to catch bad i18n keys
- SearchableDropdownField should be clearable by default - patched in silverstripe/framework
- Fixed bug where trailing slash was added to external redirects - patched in silverstripe/framework
- Fixed bug where
canArchive()was not called before archiving versioned links - patched in silverstripe/linkfield - Fixed bug where chained properties resulted in errors if TemplateGlobalProvider returns
null- patched in silverstripe/framework
Changes to look forward to in future releases
- Made scaffolding for CMSFields form fields configurable and added new options for it
- Added new
TabSet::changeTabOrder()method
Community pull requests merged
- FIX Update EditableFormHeading.php to output unique ID attributes to comply with accessibility standards by holyavocad0
Focus for the next couple of weeks
As mentioned above and in the previous update, our focus has shifted to CMS 6.
We’re working on making SiteTree use form field scaffolding and moving towards using more standard endpoints in the CMS.
We have also scoped several possible levels of abstractions we can do in various areas of the codebase, but we’re working out what the main priorities will be in that area before we go to far with them.