Releases: spicywebau/craft-neo
Releases · spicywebau/craft-neo
v2.3.5
v2.3.4
v2.3.3
Fixed
- Fix PostgreSQL error when saving new block types - thanks @ttempleton
- Fixed issue where groups were duplicated when changing min/max blocks
v2.3.2
Fixed
- Ensure field layout IDs are set when setting a field's block types - Thanks @ttempleton
v2.3.1
Fixed
- Project Config - typecast group sortOrder to int
v2.3.0.1
Changed
- Disable saveModifiedBlocksOnly for now
v2.3.0
Added
- Added support for the project config rebuild functionality introduced in Craft 3.1.20
- Added the Max Top-Level Blocks field setting
- Added the
collapseAllBlocks
plugin setting, allowing all input blocks to display as collapsed by default - Restored the
saveModifiedBlocksOnly
plugin setting (New to Neo 2; previously added to Neo 1.4.1) - Restored support for the Field Labels plugin (New to Neo 2; previously added to Neo 0.5.0 under Field Labels' previous name, Relabel)
- Added
benf\neo\events\BlockTypeEvent
- Added
benf\neo\services\BlockTypes::EVENT_BEFORE_SAVE_BLOCK_TYPE
- Added
benf\neo\services\BlockTypes::EVENT_AFTER_SAVE_BLOCK_TYPE
- Added CKEditor field content to collapsed block summaries
Changed
- Neo now requires Craft 3.1.20 or later
- New icon
- By default, Neo will only save modified blocks when saving a Neo field's value (New to Neo 2; previously added to Neo 1.3.0)
Fixed
- Fixed collapsed block summaries of colour fields on entry revisions
v1.5.2
Fixed
Fixed issue where queries for elements with empty Neo Fields would always return no elements
v2.2.8
Fixed
- Fixed issue where duplicate block type groups could be created (thanks @boboldehampsink)
v2.2.7
Fixed
- Fixed issue, when applying a project config to another environment or project, where a Neo field and block types could be synced before other fields they use, causing the block types not to have those fields in the target environment/project