Releases: craftcms/cms
Releases · craftcms/cms
5.6.9.1
- Fixed a bug where newly-created custom fields wouldn’t have their full settings intact for
afterSave()
.
4.14.8.1
- Fixed a bug where newly-created custom fields wouldn’t have their full settings intact for
afterSave()
.
5.6.9
- Fixed a bug where scrollable panes weren’t automatically scrolling when dragging objects near their edges. (#16738)
- Fixed a bug where “Applying new propagation method to [Field Name] entries” jobs weren’t getting queued when deploying changes to Matrix fields’ Propagation Method settings. (#16740)
- Fixed a bug where field layout designers’ library HUDs could open above the “Add” button, hiding the tab contents. (#16747)
4.14.8
5.6.8
- Added
craft\base\Element::ancestors()
. - Added
craft\base\Element::descendants()
. - Fixed an error that occurred when deleting a category or Structure section entry if its ancestors were eager-loaded. (#16722)
- Fixed a bug where category and entry edit pages didn’t include breadcrumbs for any disabled ancestor elements.
- Fixed a bug where the “Delete (with descendants)” bulk element action wasn’t deleting disabled descendants.
- Fixed a bug where asset files could be deleted when modified. (#16686)
- Fixed an error that could occur if a Matrix field was saved from a console request. (#16724)
- Fixed a bug where the Sort field within element index View menus wasn’t updating after the sort attribute/direction was changed by pressing on a table header.
4.14.7
- Added
craft\base\Element::ancestors()
. - Added
craft\base\Element::descendants()
. - Fixed an error that occurred when deleting a category or Structure section entry if its ancestors were eager-loaded. (#16722)
- Fixed a bug where category and entry edit pages didn’t include breadcrumbs for any disabled ancestor elements.
- Fixed a bug where the “Delete (with descendants)” bulk element action wasn’t deleting disabled descendants.
- Fixed a bug where asset files could be deleted when modified. (#16686)
5.6.7
- Fixed a bug where multiple “New file uploaded.” notifications could be shown at once. (#16688)
- Fixed an error that could occur during garbage collection if the database user didn’t have permission to disable foreign key constraints. (#16700)
- Fixed a bug where datepickers could have scrollbars. (#16697)
- Fixed a bug where asset files could be prematurely deleted when moved to a different volume, if an error occurred. (#16686)
- Fixed a bug where clearing out a Structure section’s Parent field wasn’t persisting if editing the entry for a newly-added site. (#16691)
- Fixed a bug where SVG asset transforms could get two
preserveAspectRatio
attributes. (#16709) - Fixed a bug where Number fields weren’t handling semi-numeric strings properly. (craftcms/feed-me#1575)
- Fixed an error that could occur if a field’s input HTML contained
<style>
tags. (nystudio107/craft-retour#329) - Fixed a bug where slideouts weren’t fully initializing/deinitializing their UI for users who preferred reduced motion. (#16707)
- Fixed a bug where GraphQL types for entry types were being named using sections’ and fields’ handle overrides. (#16713)
- Fixed styling issues. (#16699, #16712, #16721)
4.14.6
- Fixed a bug where multiple “New file uploaded.” notifications could be shown at once. (#16688)
- Fixed an error that could occur during garbage collection if the database user didn’t have permission to disable foreign key constraints. (#16700)
- Fixed a bug where datepickers could have scrollbars. (#16697)
- Fixed a bug where asset files could be prematurely deleted when moved to a different volume, if an error occurred. (#16686)
- Fixed a bug where clearing out a Structure section’s Parent field wasn’t persisting if editing the entry for a newly-added site. (#16691)
- Fixed a bug where SVG asset transforms could get two
preserveAspectRatio
attributes. (#16709) - Fixed a bug where Number fields weren’t handling semi-numeric strings properly. (craftcms/feed-me#1575)
- Fixed styling issues. (#16699, #16721)
5.6.6
- Fixed a bug where multi-site elements’ search indexes could be updated twice.
- Fixed a bug where some nested Matrix entries weren’t getting propagated to newly-added sites of their owners, if any blocks had been modified. (#16640)
- Fixed an error that could occur when deleting a draft.
- Fixed an error that could occur when saving a Structure section entry, if it had an Assets field with a dynamic subpath that referenced
level
. (#16661) - Fixed a bug where “Fit” image transforms were showing the “Default Focal Point” setting. (#16665)
- Fixed a bug where the “Image Position” setting wasn’t saving for “Letterbox” image transforms. (#16648)
- Fixed a bug where the
up
command, theapp/migrate
action, and the Project Config utility weren’t aware of pending project config changes if a database backup was restored but caches weren’t cleared. (#16668) - Fixed a bug where condition rules weren’t always getting created with their condition set. (#16676)
- Fixed an error that occurred when opening the filter HUD within the element selection modal for a relational field, if the user didn’t have permission to view the selected source outside of the field. (#16678)
- Fixed a bug where Number fields weren’t getting sorted properly in PostgreSQL. (#15828)
- Fixed a bug where Matrix fields’ “Default View Mode” settings included a “Display in a structured table” option. (#16631)
- Fixed a bug where user addresses weren’t getting restored when soft-deleted users were restored. (#16636)
- Fixed a bug where pressing the “New entry” button multiple times quickly would create multiple nested entries, circumventing the “Max Entries” settings. (#16642)
- Fixed a bug where Link fields without values were always getting marked as dirty when making another change to the element. (#16649)
- Fixed an error that could occur when programmatically duplicating a nested element for a new site. (#16659)
- Fixed a bug where Link fields’ “URL Suffix” and “Target” advanced fields were getting enabled even if they had been disabled in Craft 5.5. (#16663)
- Fixed an error that occurred when executing the
users/remove-2fa
command. - Fixed a potential phishing attack vector.
- Fixed styling issues. (#16683, #16684)
4.14.5
- Fixed a bug where multi-site elements’ search indexes could be updated twice.
- Fixed a bug where the
utils/delete-empty-volume-folders
command was deleting folders that had no assets directly, but had subfolders. (#16388) - Fixed a bug where some Matrix blocks weren’t getting propagated to newly-added sites of their owners, if any blocks had been modified. (#16640)
- Fixed an error that could occur when deleting a draft.
- Fixed an error that could occur when saving a Structure section entry, if it had an Assets field with a dynamic subpath that referenced
level
. (#16661) - Fixed a bug where “Fit” image transforms were showing the “Default Focal Point” setting. (#16665)
- Fixed a bug where the “Image Position” setting wasn’t saving for “Letterbox” image transforms. (#16648)
- Fixed a bug where the
up
command, theapp/migrate
action, and the Project Config utility weren’t aware of pending project config changes if a database backup was restored but caches weren’t cleared. (#16668) - Fixed a bug where condition rules weren’t always getting created with their condition set. (#16676)
- Fixed an error that occurred when opening the filter HUD within the element selection modal for a relational field, if the user didn’t have permission to view the selected source outside of the field. (#16678)
- Fixed a potential phishing attack vector.