Fixes#758.
The edits made to the fancylayout.less should more directly target just the root elements of the UI, and not spill over into nested forms.
Test case in the Test plugin: wintercms/wn-test-plugin@eaebfae
Accessible in the Pages section.
Adds the "develop.debugSnowboard" config option to enable to disable Snowboard debugging, overriding the default behaviour in following the app debug mode.
Also performs the sync with model instances rather than just raw IDs to support relationships with a custom relatedKey set (the key on the related model's table that is stored on the pivot table to connect the relationship, normally just the primary key but can be anything).
The Singleton changes introduced to Storm (ca5959495b) that bind singletons to the app means that in unit tests, we will need to re-initialise any scope we need for tests, as the app is cleared upon each test case being run.
Updates `failed_jobs` table to add missing `uuid` column. This also updates the `payload` and `exception` columns to be inline with the default Laravel migration.
- If no bootstrap is provided in "phpunit.xml", the standard Winter CMS bootstrap is used.
- If a custom bootstrap is provided by the "-b" option, it will be used.
- Finally, the bootstrap specified in "phpunit.xml" will be used.
- Added the ability for relative and absolute paths to be used in "phpunit.xml" for the bootstrap path.
Fixes#680. Originally meant to support the default length of a VARCHAR column in MySQL it has since been rendered more unhelpful than helpful given that the default length is not always 255 and the silent failure mode when copying and pasting content into the field is a detriment to user experience.
This adds support for applying conditions to a relation column. Given the following structure:
Entries:
- id
- created_at
EntryData:
- entry_id
- key
- value
You can display the individual EntryData records as separate columns in the list widget by using the following configuration:
```yaml
id:
label: ID
created_at:
label: Created at
_entry_field_email:
label: Email
relation: entry_data
conditions: "`key` = 'email'"
select: value
```
Fixes the following error when previewing a column on Import:
"Call to undefined method League\Csv\Reader::setOffset()"
on line 253 of modules/backend/behaviors/ImportExportController.php
Credit to @alxy
ref. octobercms/october#5629
The fixes in 9637b67c23 stopped overridden POST values from working, as these were interpreted as arrayed values. This makes the checkbox and switch inputs stop working, as these have a default "unchecked" value which is then overridden by the "checked" value when checked.