The last two weeks have been very productive. A lot of work has been done to automate many processes, as well as improve existing ones. Documentation has also been updated and minor issues have been resolved. Active work has begun on improvements that will be available in CMS 6
Changes to look forward to in future releases
- Unable to inline save related data
- Incomplete code for handling current-scope loop in templates
- Strongly type FieldList
- Run module-standardiser
- Ability to loop through containers containing primitives in Silverstripe templates
- Add a PHP 8.3 build to the sink
- Restore batch action is unusable - Remove it
Bug fixes and other immediate changes
- Review best practice for drafting documentation in the developer docs
- Thumbnails in CMS File system not showing up in Subfolders
- Create a workflow to create an issue linking to broken builds and broken merge-ups on a weekly cron
- GitHub Workflows security hardening
- Misleading docs about querying many_many through join data
- Allow “from” class in many_many through to accept subclasses
- SearchableDropdownField breaks grid field filtering
- Turn off 4.13 ci cron + resolve red builds
- Update repositories that pull in data from silverstripe/supported-modules
- The matrix is trying to include installer for cow CI runs
- Undefined array key
- Make developer-docs the first thing processed
Community pull requests merged
We are sincerely grateful for the valuable contributions made by the Silverstripe community.
- NEW Nested gridfield by Niklas Forsdahl
- FIX: Fixed move to prev/next page functionality by Loz Calver
- FIX Ensure correct link is used when gridfield is readonly by AljosaB
- Fix broken link in readme by Ed Wilde
- FIX ‘which’ check in ‘sake’ now works for aliases by Hernold Koch
- FIX: Update model class importer key by Mike Nuguid
- FIX #64: TinyMCE text and image alignment issue by Thor(Shenghan) Chen
- FIX Don’t hardcode table name by Werner Krauß
Work in progress
In the upcoming fortnight, our primary focus will be on advancing CMS 6. Specifically, we’ll be introducing the capability to utilise arrays in templates. Moreover, we’ll dedicate efforts to enhance CI processes further and continue addressing any ongoing issues.