Releases: spicywebau/craft-neo
Releases · spicywebau/craft-neo
v2.2.2
Fixed
- Fixed issue where block types would lose any blank tabs in Neo 2.2.0 and 2.2.1
v2.2.1
Fixed
- Fixed issue where Craft would try to run Neo's Craft 3 upgrade migration on updating to Neo 2.2.0 if Neo 2 was originally installed as a pre-release version
v2.2.0
Added
- Added Craft 3.1 project config support
- Added Craft 3.1 soft-deletes support
- Restored the ability to convert Neo fields to Matrix (New to Neo 2.x; previously added to Neo 1.4.0)
- Restored automatic Neo-to-Matrix conversion on uninstalling Neo (New to Neo 2.x; previously added to Neo 1.4.0)
Changed
- Neo now requires Craft 3.1.0 or newer
- Collapsed block summaries now also show content from child blocks
Fixed
- Fixed issue where blocks would disappear if a Neo field's 'manage blocks on a per-site basis' setting was changed
- Fixed duplicated blocks when saving after setting an existing field to manage blocks on a per-site basis
v2.1.8
Fixed
- Fixed multi-site issue, when enabling a site for a section, where a Neo field set not to manage its blocks on a per-site basis would cause the resaving of the section's entries to fail
v2.1.7
Fixed
- Fixed issue where Neo blocks would not appear on duplicated entries
v2.1.6
Fixed
- Fixed error when pasting or cloning blocks on single-site Craft installations
v2.1.5
Fixed
- Fixed issue where structure IDs were not being set for block queries, causing duplicated blocks to appear in Craft 3.1.0 and newer
v2.1.4
Fixed
- Fixed issue on multi-site Craft installs where entry/category fields in new or pasted/cloned Neo blocks were always listing elements from the primary site
v2.1.3
Fixed
- Fixed error when duplicating an element with a Neo field set not to manage blocks on a per-site basis
v2.1.2
Added
- Added the ability to copy multiple selected blocks from different levels, which can be pasted at the same level
Fixed
- Now always saves the block type field layout when saving a block type; fixes an issue with Schematic importing Neo before its field layout fields are imported (thanks @boboldehampsink)