mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-10-22 14:05:37 +02:00
DOCS Adding information about better buttons to the release changelog (#9049)
This commit is contained in:
parent
e2894b414b
commit
c57584dada
@ -13,6 +13,8 @@
|
||||
- dev/build is now non-destructive for all Enums, not just ClassNames. This means your data won't be lost if you're switching between versions, but watch out for code that breaks when it sees an unrecognised value!
|
||||
- Removed `File.migrate_legacy_file` config option. Migration tasks now need to run via `dev/tasks/`,
|
||||
running them as part of `dev/build` is no longer supported
|
||||
- [Added navigation and new record actions](#better-buttons) to grid field detail forms. Inspired by @unclecheese's
|
||||
"better buttons".
|
||||
|
||||
|
||||
### DevelopmentAdmin controllers
|
||||
@ -361,6 +363,27 @@ that gets modified on every deploy update so that the framework will automatical
|
||||
The best practice is not to reuse the application manifest cache between deploys.
|
||||
</div>
|
||||
|
||||
### New GridField detail form actions {#better-buttons}
|
||||
|
||||
Pagination controls and an add new button has been added to the bottom toolbar of GridField detail forms. This is
|
||||
enabled by default. In cases where you do not want these buttons to appear on your detail form then you can use the new
|
||||
[constructor API](http://api.silverstripe.com/4/SilverStripe/Forms/GridField/GridFieldDetailForm.html#method___construct)
|
||||
of the detail form to control whether pagination and/or the add button are shown. Additionally the default value can be
|
||||
set globally with the following configuration:
|
||||
|
||||
```yaml
|
||||
---
|
||||
Name: app_buttons
|
||||
After:
|
||||
- '#buttons'
|
||||
---
|
||||
SilverStripe\Forms\GridField\GridFieldDetailForm_ItemRequest:
|
||||
formActions:
|
||||
showPagination: false
|
||||
showAdd: false
|
||||
|
||||
```
|
||||
|
||||
## Changes to internal APIs
|
||||
|
||||
- `PDOQuery::__construct()` now has a 2nd argument. If you have subclassed PDOQuery and overridden __construct()
|
||||
@ -612,4 +635,4 @@ The best practice is not to reuse the application manifest cache between deploys
|
||||
* 2018-10-04 [261539953](https://github.com/silverstripe/silverstripe-framework/commit/261539953568e18361d30d7603c22ad3cb7c8cef) Use PDO’s built-in transaction support in MySQLDatabase. (Sam Minnee)
|
||||
* 2018-10-04 [0111b98b1](https://github.com/silverstripe/silverstripe-framework/commit/0111b98b18a273ca5c37013d880c5d21f94396af) Ensure that types are preserved fetching from database (Sam Minnee)
|
||||
* 2018-09-14 [274657f4f](https://github.com/silverstripe/silverstripe-framework/commit/274657f4f815cfb990c23b39ab81c1def91b37ad) Add support in "I should see a message" step definition for Bootstrap alerts (Robbie Averill)
|
||||
* 2018-07-04 [18293f7af](https://github.com/silverstripe/silverstripe-framework/commit/18293f7afed8db2c4a83356312027d8245fd4c3f) Rename pushHandler to pushLogger (Robbie Averill)
|
||||
* 2018-07-04 [18293f7af](https://github.com/silverstripe/silverstripe-framework/commit/18293f7afed8db2c4a83356312027d8245fd4c3f) Rename pushHandler to pushLogger (Robbie Averill)
|
||||
|
Loading…
Reference in New Issue
Block a user