Dylan Wagstaff
Dylan Wagstaff
Currently (SS 4.2.1) TinyMCE is loaded via Entwine, which is causing issues as we progressively move towards more and more react driven UI components. The usecase sparking this particular issue...
# Story time I am a user I have created a file by uploading `test.jpg` I don't want that file any more I delete that file via `asset admin` 🤔...
 When I select e.g. 4 files for moving, then use the move button at the base of the interface (if you are sighted), the modal that pops up presents...
When using TinyMCE to embed a file, selecting a draft asset from the store modal works as intended. However after publishing the page the asset in the store modal is...
https://github.com/silverstripe/silverstripe-admin/blob/cd1271f86ba890a6d6378794bb58fd320751d29f/code/ModelAdmin.php#L616 The default importer fetch function supposes that the key for each managed model definition is the `dataClass`, but this is normlised to be in the `dataClass` key. The key...
Fixed issue where pagination stopped working after first load Fixed issue where items could not be removed if they were not on the first page
Resulting in ``` ArgumentCountError: Too few arguments to function SilverStripe\Control\HTTPRequest::__construct(), 0 passed in [...]vendor/silverstripe/framework/src/Core/Injector/InjectionCreator.php on line 35 and at least 2 expected ``` https://github.com/silverstripe/silverstripe-admin/blob/55ad9610ff1095b576168a238654d672cb401576/code/SudoModeController.php#L48 ----- Thanks @GuySartorelli for pointing out...