Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOC BuildTask is_enabled config #281

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions en/04_Changelogs/5.1.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ title: 5.1.0 (unreleased)

- [Features and enhancements](#features-and-enhancements)
- [Other new features](#other-features)
- [API changes](#api-changes)
- [Bug fixes](#bug-fixes)

## Features and enhancements
Expand All @@ -19,6 +20,10 @@ title: 5.1.0 (unreleased)
- The [`i18nTextCollector`](api:SilverStripe\i18n\TextCollection\i18nTextCollector) now collects strings for ORM properties (e.g. `$db` fields) in `DataObject` and `Extension` classes, and from themes. See [i18n - collecting text](/developer_guides/i18n/#collecting-text) for more details.
- Extensions which modify permissions for [`Group`](api:SilverStripe\Security\Group) records which return `true` will be respected, the same as when modifying permissions for any other `DataObject` record.

## API changes

- [`BuildTask`](api:SilverStripe\Dev\BuildTask) now has boolean `is_enabled` configuration option which has precedence over the existing `BuildTask::enabled` protected class property. The `BuildTask::enabled` property has been marked as deprecated and will be removed in CMS 6 if favour of using `is_enabled` instead.

## Bug fixes

- [`DataList::filterAny()`](api:SilverStripe\ORM\DataList::filterAny()) queries on many-many relations that use an aggregate `HAVING` clause now correctly use an `OR` conjunction rather than an incorrect `AND` conjunction.
Expand Down