Releases: spicywebau/craft-neo
Releases · spicywebau/craft-neo
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
v2.2.6
Changed
- Neo now requires Craft 3.1.13 or later
Fixed
- Fixed error when applying a project config to another project where a Neo field from the first project doesn't exist
- Fixed error in some cases when deleting a block type and that block type's blocks
v2.2.5
Fixed
- Fixed issue in Neo 2.2.4 with disabled blocks being deleted when saving a Neo field's contents
v1.5.1
Added
Changed developer to Spicy WebFixed
Fixed issue with blocks disappearing on elements with more than one Neo fieldFixed
Fixed issue with lightswitches not working on new blocksFixed
Fixed flickering Reasons modal when using Reasons v1.0.11Fixed
Fixed disabled blocks showing in live previewFixed
Fixed issue where the handle of an existing block type was changing when editing the nameFixed
Clean up block structures if duplicates exist, which could cause blocks either to disappear or to all nest within a newly-added block
Changes from v1.5.0
Added
New icon 😎Added
Copy and paste functionality for blocks (replaces the Duplicate block option)Added
The CpFieldLinks plugin is now supported in blocksAdded
Addedcraft.neo.blocks()
template query function to query for site-wide Neo blocks, much like entries and other elements (thanks @intoeetive)Improved
Saving new entries will now copy Neo contents to all other localesImproved
Added owner property to neoblock to use with dynamic assets pathFixed
Generating keywords for blocks now only iterates the fields of that block, fixing issues with generating keywords on old fields and third-party plugin conflictsFixed
Fixed issue where field types like Matrix used within blocks could not clean up properly if that block was deleted, leading to stranded Matrix blocks left in the databaseFixed
Fixed issue with stacking block criteria model filters in Live Preview sometimes not showing the right resultsFixed
Fixed issue with translated relational fields (eg. Asset field) inside translated Neo fields not saving properly on newly added blocks
v2.2.4
Changed
- Now supports filtering an entry draft's Neo field content with query parameters
Fixed
- Fixed error when creating a new section
v2.2.3
Added
- Added support for the CP Field Inspect plugin
Fixed
- Fixed issue with pasting or cloning blocks where number field values were not retained