This will track nodes being removed from the DOM, and if any widgets are active in these nodes, they will automatically be destructed. This will be more reliable than just tracking AJAX updates, as it should also apply to elements/widgets being removed by JS, such as widgets within modals.
- Move most shared vendor files used in Backend widgets and UI to separate vendor file
- Remove Vue embedding in Icon Picker (now uses shared vendor instance of Vue)
- Add Widget and Event handlers
- Upgraded Babel Loader to version 5 to fix potential security issue with JSON5 library (not that we used it)
This is causing an error when using relation mode and you have an empty relation and try to save. The method expects an array, but in some cases can be null.
The addFields() method already filters out fields that don't match the current context. As such, the normalized field name should be used when adding the field to the tab containers instead of the name with the context included. This matches the definition in allFields.
A previous bug fix applied here (18af35d928) forced only visible columns to be sortable to prevent an error from occurring if someone sorts by a column that is then removed from the columns list.
This change results in the same fix, but simply checks that the column is sortable (which would be false if the column no longer exists). This would allow columns that are invisible but are also sortable to still be used for sorting purposes.
Fixes#796, #709
Refs:
- https://github.com/octobercms/october/issues/5227
This prevents issues caused by extensions to the RelationController making changes to the relation's parent model for use cases needed in relations. These changes were previously also affecting the model instance used by the FormController behaviour.
If it is desired to interact with the exactly model instance as used by the FormController behaviour inside of your extensions to the RelationController you can use $controller->formGetModel() instead.
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.
