- Fixed a bug where field layout elements of collapsed Neo blocks could be interacted with
- Fixed a "Column 'structureId' in where clause is ambiguous" error that could occur when merging canonical block changes into derivative blocks
- Fixed a bug when saving an entry, where new Neo blocks could have incorrect validation errors concerning invalid child block types
- Fixed a bug where validation error messages on block type settings would not display after saving the Neo field failed
{note} If you are a developer of a plugin or module that extends Neo functionality, check the upgrade guide.
- Added the
blockTypeIconPathplugin setting - Added the
blockTypeIconSelectModeplugin setting - Added
benf\neo\console\controllers\BlockTypesController::actionConvertIcons() - Added
benf\neo\enums\BlockTypeIconSelectMode - Added
benf\neo\jobs\ResaveFieldBlockStructures - Added
benf\neo\models\BlockType::$iconFilename - Added
benf\neo\models\BlockType::getIconPath() - Added
benf\neo\models\BlockType::getIconUrl() - Added
benf\neo\services\BlockTypes::getAllIconFilenames() - Added
benf\neo\services\BlockTypes::getIconPath() - Added
benf\neo\services\BlockTypes::getIconUrl() - Added
benf\neo\services\Fields::applyPropagationMethod()
- Block type and block type groups now have their sort orders stored in a per-field ordered array in the project config
- Whether a Neo block type's Top Level, Max Sibling Blocks of This Type, Child Blocks or Max Child Blocks settings have been violated is now validated server-side when saving a Neo field's contents, rather than relying on them to be enforced by client-side JavaScript
benf\neo\elements\Block::getOwner()will now returnnullif the block's owner no longer exists, instead of throwingyii\base\InvalidConfigException
- Removed
benf\neo\assets\FieldAsset; usebenf\neo\assets\InputAssetinstead - Removed
benf\neo\assets\SettingsAsset::EVENT_SET_CONDITION_ELEMENT_TYPES; usebenf\neo\services\BlockTypes::EVENT_SET_CONDITION_ELEMENT_TYPESinstead - Removed
benf\neo\controllers\Configurator::actionRenderFieldLayout(); usebenf\neo\controllers\Configurator::actionRenderBlockType()and access the returned array'slayoutHtmlvalue instead - Removed
benf\neo\services\BlockTypes::renderBlockTypeSettings(); usebenf\neo\services\BlockTypes::renderSettings()and access the returned array'ssettingsHtmlandsettingsJsvalues instead - Removed
benf\neo\tasks\DuplicateNeoStructureTask; usebenf\neo\jobs\SaveBlockStructuresinstead - Removed the
Block.getNewId()JavaScript method - Removed the
Block.updateMenuStates()JavaScript method; useBlock.updateActionsMenu()instead - Removed the
BlockType.loadFieldLayout()JavaScript method; useBlockType.load()instead - Removed the
BlockTypeSettings.setSortOrder()JavaScript method - Removed the
GroupSettings.setSortOrder()JavaScript method - Removed the
Settings.getSortOrder()JavaScript method - Removed the
Settings.setSortOrder()JavaScript method
- Fixed a bug where applying a propagation method change to a Neo field would not create new block structures for the duplicated blocks
- Fixed a bug where queries for Neo blocks with a specific owner entry/category could return duplicate blocks, if the entry/category had any drafts and the duplicated blocks were owned by both the entry/category and the drafts
- Fixed an error that occurred when lazy loading a new block that requires at least two child blocks
- Add
uidhandling for blocks when converting from serialised blocks (thanks @engram-design)
- Fixed invalid HTML being generated for new blocks' top bar checkboxes (thanks @engram-design)
- Fixed a bug when lazy loading new blocks in a slideout element editor, where the values of new blocks' fields affected by condition rules weren't being saved
- Fixed a bug when lazy loading new blocks in a slideout element editor, where the new blocks' field values weren't being saved
- Added
benf\neo\services\BlockTypes::renderSettings()
- Deprecated
benf\neo\services\BlockTypes::renderBlockTypeSettings()
- Fixed a JavaScript error that occurred when loading the settings for a block type using the 'related to' condition
- Fixed a bug with the spinner placement when lazy loading new blocks, when a new block was created with the add block above action
- Fixed a bug where conditionally hidden fields on new blocks would not display the first time conditions were met for it to display
- Fixed a JavaScript error that occurred when deleting saved parent blocks
- Fixed a bug where Craft garbage collection would delete block structures for drafts and revisions of elements that had been deleted and restored
- Fixed a bug when the
enableLazyLoadingNewBlocksplugin setting was disabled, where JavaScript was being initialised twice for each existing block - Fixed a bug where published Neo blocks could be merged into the wrong place in a draft block structure in some cases
- Fixed an error that could occur when saving an entry containing a Neo field
- Fixed a bug that occurred when using the child block UI element, where creating the parent block and then creating the child block before the draft had finished saving would cause blocks to be lost
- Fixed a bug when creating at least two block types at once, where parent-child relations set between the new block types would not be saved
- Fixed a bug when lazy loading new blocks, where relation element fields in new blocks would show elements from the default site, rather than the active site
- Fixed an error that could occur when lazy loading new blocks
- Fixed a bug where nested fields that depend on external CSS or JavaScript files weren't loading correctly when lazy loading new blocks
- Fixed an error that could occur when upgrading from Craft 3 to Craft 4 (thanks @oliver-amann)
- Added the
enableLazyLoadingNewBlocksplugin setting (defaults totrue; setting tofalsewill revert to pre-3.9.0 behaviour)
- Fixed a bug where empty field layout tabs on Neo block types would be duplicated when saving the Neo field
- Fixed an error that occurred when creating a new block that contains a Vizy field
- Fixed a bug where content of newly created Neo blocks would be lost on owner element save
- Fixed a bug that occurred when pasting Neo input blocks that use the child block UI element and have descendants, where the descendants would disappear after updating visible field layout elements for the Neo field
- Added Dutch translations (thanks @lavandongen)
- Neo now requires Craft 4.5.0 or later
- Field layout tabs for new Neo input blocks of a certain block type are now lazy loaded when a block of that type is first created
- Fixed a bug where Neo block structure data would be lost when soft-deleting an entry
- Fixed an error that could occur when applying Neo block type project config changes
- Fixed a bug with the placement of block type handles on input blocks on Craft 4.5, for users who have their preferences set to show field handles in edit forms
- Fixed a bug when trying to save an entry before draft autosaving had completed following the creation of a Neo block, where any further changes to the Neo field would cause that block's contents to disappear
- Fixed an error that occurred when saving an entry that uses a Neo field, if one of that field's block types had been deleted, and any block type that used the deleted block type as a child block type had not been edited
- Fixed an error that could occur during Craft garbage collection if the
neoblockstructurestable contained more than 65535 rows
- Fixed a bug that caused content loss of new Neo blocks' subfields, if the new block was created between a provisional draft saving and dynamic Neo subfield conditions being applied
- Fixed a bug where empty block type descriptions could be inconsistently set to either
''ornull(should now be consistently set to'')
- Added
benf\neo\services\Blocks::getStructures()
- Fixed timeouts caused by Neo that could occur when saving an entry, if Craft is running with a clustered/load-balanced DB service
- Fixed a server error that occurred when using a slideout editor to edit an element with a Neo field
- Fixed a bug with applying dynamic Neo subfield conditions after a draft autosave, if the draft was resaved while Neo was checking which fields should be visible
- Fixed visual bugs and loss of newly created block type and block type group data if validation errors occurred when saving a Neo field, and there had been more than one block type or block type group created
- Added
benf\neo\Field::getItems() - Added
benf\neo\Field::setItems()
- When editing a Neo field's settings, block type and block type group settings are now lazy loaded
- Deprecated
benf\neo\controllers\Configurator::actionRenderFieldLayout()
- Fixed performance issues when loading a Neo field settings page, if the Neo field has a large number of block types
- Fixed an SQL error that could occur when upgrading to Craft 4, if any
neoblockstable rows referenced nonexistent element IDs - Fixed a bug where the copy and clone actions were still available on blocks for users who didn't have permission to create blocks of its type
- Fixed a bug where the add block above action was still available on blocks for users who didn't have permission to create any of the sibling block types
- Fixed a compatibility issue with the Content Templates plugin and Neo 3.7.11
- Fixed a bug when creating drafts on multi-site Craft projects with a Neo field's propagation method set to an option other than "Only save blocks in the site they were created in", where some sites could end up without a Neo block structure for the draft
- Fixed a bug when validation errors occurred when editing an element that has more than one Neo field, where some blocks could have multiple add block buttons added
- Fixed a bug when merging live entry changes into a draft, where newly-created blocks could end up in the wrong places in the draft's block structure
- Fixed a bug where Neo fields would fail validation if they only contained automatically-added blocks (per the field's Min Blocks setting) and no changes were made to them
- Fixed a bug where a block type's min and max child blocks settings weren't being cleared if the block type was set to no longer have any valid child block types
- Neo will no longer create revision block structures using queue jobs if the Craft project's
runQueueAutomaticallygeneral setting is disabled
- Fixed a bug where Neo blocks could get detached from entries when sections were enabled for a new site
- Fixed a bug where pasting or cloning blocks whose types' 'Group Child Block Types' setting was disabled would cause the setting not to be respected on the pasted/cloned block
- Fixed a bug where setting conditions on a child blocks UI element would cause the UI element not to display
- Fixed a JavaScript error that occurred when entry saving failed, if draft autosaving was disabled and new Neo blocks were created containing Redactor fields
- Fixed a bug where Plain Text and Table fields were converting posted shortcode-looking strings to emoji, for Craft 4.5 and later (thanks @brandonkelly)
- Fixed a bug when updating Neo blocks' visible field layout elements, where blocks' top bars could display the incorrect selected tabs
- Added the
enableBlockTypeUserPermissionsplugin setting (defaults totrue)
- Fixed an error that occurred when updating Neo blocks' visible field layout elements if the owner element was disabled
- Fixed a bug when updating visible field layout elements after creating a new block, where disabled blocks in the Neo field weren't being accounted for, causing another block's content to appear in the new block
- Fixed a bug where, when automatically creating child blocks for a newly created block with Min Child Blocks set, the child blocks would be created at the same level as the parent
- Fixed a bug on multi-site Craft installs, where Neo could check for the wrong site's block data when updating visible field layout elements
- Added the ability to set conditions on which global sets a Neo block type can be used for
- Added the Level option to the Neo block layout element condition rules
- Added options to the Neo block layout element condition rules for parent blocks' field values
- Added
benf\neo\conditions\fields\ParentFieldConditionRuleTrait - Added
benf\neo\conditions\fields\ParentDateFieldConditionRule - Added
benf\neo\conditions\fields\ParentLightswitchFieldConditionRule - Added
benf\neo\conditions\fields\ParentNumberFieldConditionRule - Added
benf\neo\conditions\fields\ParentOptionsFieldConditionRule - Added
benf\neo\conditions\fields\ParentRelationalFieldConditionRule - Added
benf\neo\conditions\fields\ParentTextFieldConditionRule - Added
benf\neo\controllers\Input::actionUpdateVisibleElements()
- When using an element editor page, Neo block subfields will now be shown or hidden based on their condition rules after the owner draft is saved
- When opening an element editor page, if a Neo field's Min Blocks setting hasn't been met, and it has only one block type available at the top level, the required blocks will now automatically be created
- When editing an element and creating a new Neo block, if the block type's Min Child Blocks setting is set, and it has only one child block type available, the required child blocks will now automatically be created (however, the child blocks themselves won't have any required child blocks automatically created, to prevent any potential infinite recursion)
- Fixed a bug where the default Neo block type icon wasn't displaying when editing elements that don't have drafts, e.g. global sets, Craft Commerce products
- Fixed a bug with the Add Block Above action, when using the new block menu grid style
- When Neo block queries have a single
ownerId,siteIdand either a singlefieldIdoridset, the appropriatestructureIdwill now also be set on the query, if it exists and wasn't already set on the query
- Fixed an error that occurred when viewing revisions, when using new block menu styles that show icons
- When running Craft garbage collection, Neo will now delete any orphaned Neo block structure data
- Fixed an error that occurred when updating to Neo 3.6.2 if no Neo fields existed
- Fixed a bug where Neo block structures belonging to provisional drafts weren't being deleted when saving the entry
- Fixed a bug where all block types in new block menus on unsaved blocks were showing the default icons, when using new block menu styles that show icons
- Fixed a bug with the format of block type icon data stored in the project config
- Fixed an error that occurred when applying a project config from a Craft install running a Neo version prior to 3.6.0
- Added the
newBlockMenuStyleplugin setting - Added the
blockTypeIconSourcesplugin setting - Added a plugin settings page
- Added French translations (thanks @scandella)
- Added
benf\neo\controllers\Configurator::actionRenderBlockType() - Added
benf\neo\models\BlockType::$iconId - Added
benf\neo\services\BlockTypes::EVENT_SET_CONDITION_ELEMENT_TYPES - Added
benf\neo\services\BlockTypes::renderBlockTypeSettings()
- Deprecated
benf\neo\assets\SettingsAsset::EVENT_SET_CONDITION_ELEMENT_TYPES; usebenf\neo\services\BlockTypes::EVENT_SET_CONDITION_ELEMENT_TYPESinstead
- Fixed a bug where, when pasting or cloning a block type, the block type conditions weren't being copied
- Fixed a bug where users who were disallowed from deleting Neo blocks of a certain block type still didn't have the delete option on existing blocks if the block type's Ignore Permissions setting was enabled
- Fixed a bug where new Neo blocks' collapsed states were being lost when saving
- Fixed a console error that could occur after copying a Neo block if any of the Neo field's block types were being filtered out
- Fixed a bug where revision Neo blocks could be saved at the wrong level
- Fixed a bug where a Neo block type group without a name could have its name set to
nullin the project config, instead of an empty string - Fixed an error that occurred when applying a project config if a Neo block type group without a name had its name set to
nullin the project config - Fixed an error that occurred when using Field Manager to import Neo field data that was exported by the Craft 3 version of Field Manager
- Fixed block structure issues
- Fixed an error that occurred when merging canonical Neo block changes into their derivative blocks
- Fixed a bug where disabled nested Neo blocks, and potentially blocks following them in the block structure, could incorrectly be saved at the top level
- Fixed a bug when using eager loading (including using GraphQL), where querying a Neo block's children would always return no results
- Fixed a bug where a Neo block type's
conditionsproperty was not being set in the project config if there were no conditions on the block type - Fixed style issues with Neo block type handles on Neo input blocks when using Safari
- Fixed a bug in Neo 3.5.9 where Neo block structures weren't being saved for entry revisions
- Fixed an error that could occur when saving entries using Neo 3.5.8
- Fixed a bug where queries for Neo blocks with a specific owner entry/category could return duplicate blocks, if the entry/category had any drafts and the duplicated blocks were owned by both the entry/category and the drafts
- Fixed the position of field status indicators within Neo fields in Live Preview
- Fixed a bug where Neo blocks could be scrambled or the "Can not move a node when the target node is same" error could occur when creating a draft
- Fixed a bug where rebuilding the project config would result in Neo block type config YAML files being removed
- Fixed a console error that occurred in Neo 3.5.4 if there was no Neo copied block data in the browser's local storage
- Fixed a bug where Neo child blocks could be cloned to exceed the parent block's max child blocks setting
- Fixed an error that occurred when executing a GraphQL query, if a field previously of the Neo type had been changed to a different type
{note} The migration that runs in this update saves the value of
ignorePermissionsfor each block type based on which block types already have any user permissions set - if any have been set, then it will be saved asfalse, otherwise it will be saved astrue.
- Added
benf\neo\models\BlockType::$ignorePermissions- Adds the ability to set a block type to ignore any user permissions set for it (in the Advanced section of the block type settings)
- Fixed an error that occurred if Feed Me wasn't installed
- Added support for the Feed Me plugin
- Added the ability to set user permissions for the creation, deletion and editing of blocks of each block type
- Added the ability to set whether the child block types of a block type will be shown in their groups (if any)
- Added
benf\neo\console\controllers\BlockTypesController::$setGroupChildBlockTypes - Added
benf\neo\console\controllers\BlockTypesController::$unsetGroupChildBlockTypes - Added
benf\neo\Field::getBlockTypeFields() - Added
benf\neo\integrations\feedme\Field - Added
benf\neo\models\BlockType::$groupChildBlockTypes - Added
benf\neo\services\Fields::getNeoFields()
- Updated JavaScript dependencies
- Fixed a bug where opening a Neo block's actions menu would not close any already open actions menu belonging to another block in the same Neo field
- Fixed a bug that occurred when using the
collapseAllBlocksplugin setting, where existing blocks could not be expanded
- Fixed a bug where cloning or copying Neo blocks using the child blocks UI element could cause the parent blocks to be pasted/cloned with some of the child block's content
- Neo block subfields can now have condition rules applied based on the owner element's section, entry type, asset volume, category group, user group or tag group
- Added
benf\neo\elements\conditions\BlockCondition - Added
benf\neo\elements\conditions\OwnerCategoryGroupConditionRule - Added
benf\neo\elements\conditions\OwnerConditionRuleTrait - Added
benf\neo\elements\conditions\OwnerEntryTypeConditionRule - Added
benf\neo\elements\conditions\OwnerSectionConditionRule - Added
benf\neo\elements\conditions\OwnerTagGroupConditionRule - Added
benf\neo\elements\conditions\OwnerUserGroupConditionRule - Added
benf\neo\elements\conditions\OwnerVolumeConditionRule
- Copied Neo input block data is now stored on a per-field basis
- Fixed a bug where Neo block tabs weren't showing indicators of validation errors in descendant blocks, if the descendant blocks were hidden in child blocks UI element(s)
- Fixed a bug where the block type names on existing Neo input blocks weren't being translated
- Fixed a bug where the tab names on all Neo input blocks weren't being translated
- Fixed a bug where eager loaded Neo fields with disabled parent blocks would have their enabled child blocks counted as children of the parent's previous sibling block
- Collapsed block previews can now display TinyMCE Field content
- Fixed an error that could occur when upgrading to Craft 4, if any Neo blocks contained null
sortOrdervalues - Fixed an 'Attempt to read property "typeId" on bool' error that could occur during Neo field validation when saving an entry
- Fixed a bug with Min Child Blocks validation when saving an element that doesn't autosave drafts
- Fixed a bug where Neo block tabs weren't showing indicators of validation errors in subfields
- Fixed a gateway timeout that could occur when validation errors occurred with unsaved Neo parent and child blocks
- Fixed an error that occurred when upgrading from Craft 3 to Craft 4 if any Neo fields had been converted to Matrix fields
- Fixed a JavaScript error that occurred if any existing Neo blocks with filtered-out block types had child blocks with allowed block types
- Fixed an 'Undefined array key' error that occurred when saving an element, if any Neo blocks were in formerly valid places in the field for them to exist
- Fixed a bug where Neo fields could be created without any block types at the top level
- Fixed a bug when editing a Neo field's settings, where setting a block type to be allowed or disallowed at the top level was not applying the new state to the block type sidebar
- Fixed a bug with Min Sibling Blocks of This Type validation
- Fixed a bug with GraphQL, where transform directives weren't working on asset field on child blocks
- Fixed a bug where pasted or cloned blocks would appear to be disabled
- Fixed a bug where newly created disabled blocks would not have their disabled state saved
- Renamed the
Input._blockSelectNeo JavaScript property toInput.blockSelect(denoting it as public)
- Fixed a JavaScript error that occurred when trying to enable or disable multiple selected blocks at once
- Fixed a bug where validation errors when creating a new entry could cause Neo blocks' subfield content to be lost
- Improved the appearance of titles of Neo input blocks with validation errors
- Fixed a bug where trying to delete all Neo blocks from a field would cause them not to be deleted
- Fixed a JavaScript error that could occur with a Neo -> Matrix -> Redactor setup if there were validation errors
- Fixed an 'Undefined array key' error that occurred in some cases when saving an element
- Fixed an error that occurred when applying a project config from a Craft install running a Neo version prior to 3.3.0
- Added the Min Levels field setting (added
benf\neo\Field::$minLevels) - Added the Min Top-Level Blocks field setting (added
benf\neo\Field::$minTopBlocks) - Added the Enabled block type setting (added
benf\neo\models\BlockType::$enabledand added theenabledcolumn to theneoblocktypestable) - Added the Min Blocks block type setting (added
benf\neo\models\BlockType::$minBlocksand added theminBlockscolumn to theneoblocktypestable) - Added the Min Sibling Blocks of This Type block type setting (added
benf\neo\models\BlockType::$minSiblingBlocksand added theminSiblingBlockscolumn to theneoblocktypestable) - Added the Min Child Blocks block type setting (added
benf\neo\models\BlockType::$minChildBlocksand added theminChildBlockscolumn to theneoblocktypestable) - Added
benf\neo\console\controllers\BlockTypesController::$setEnabled(added the--set-enabledoption to thephp craft neo/block-types/editconsole command) - Added
benf\neo\console\controllers\BlockTypesController::$unsetEnabled(added the--unset-enabledoption to thephp craft neo/block-types/editconsole command) - Added
benf\neo\console\controllers\BlockTypesController::$setMinBlocks(added the--set-min-blocksoption to thephp craft neo/block-types/editconsole command) - Added
benf\neo\console\controllers\BlockTypesController::$setMinSiblingBlocks(added the--set-min-sibling-blocksoption to thephp craft neo/block-types/editconsole command) - Added
benf\neo\console\controllers\BlockTypesController::$setMinChildBlocks(added the--set-min-child-blocksoption to thephp craft neo/block-types/editconsole command)
- Restored the ability to show Linkit field content in collapsed block previews
- Fixed a bug when saving an element, where Neo fields weren't being validated on block types' Max Blocks settings, unless at least one of the Neo field's Max Top-Level Blocks and Max Levels settings were set
- Fixed a bug where copying and pasting a block type would not copy the old block type's description to the new block type
- Fixed a bug where collapsed block previews were still displaying after expanding a block
- Fixed a bug where collapsed block previews were not displaying the content of multi-line plain text fields
- Fixed a bug on multi-site Craft installs, where a provisional draft being created with an unedited Neo field could cause the Neo field's block structure not to be created for the provisional draft, if the Neo field's propagation method was set to "Only save blocks to the site they were created in"
- Fixed a bug where disabled Neo input blocks could appear to be enabled, and selecting the disable action on these blocks would have no effect
- Fixed a bug where disabled Neo input blocks could sometimes not appear, if there were validation errors when saving an element
- Fixed a bug where calling
ids()on a memoized Neo block query would always return an empty array - Fixed a bug that occurred when saving an element that doesn't autosave drafts, where validation errors would cause new Neo blocks that had any child blocks to incorrectly detect themselves as their own child block
- Fixed a bug that occurred when saving an element that doesn't autosave drafts, where changes to a Neo block's enabled/disabled state wouldn't be saved
- Added
benf\neo\console\controllers\FieldsController::$withPropagationMethod(added the--with-propagation-methodto thephp craft neo/fields/reapply-propagation-methodconsole command)
- Fixed potential performance issues when executing Neo block queries with memoized blocks if the
statusproperty was set on the query - Fixed a bug when reverting to an entry revision, where Neo revision blocks that had deleted canonical blocks weren't being reverted
- Fixed a bug where Neo fields were assuming their values hadn't been eager-loaded on element save
- Element conditions can now include condition rules for Neo fields on Craft 4.2.0 or later
- Updated JavaScript dependencies
- Fixed a bug where saving an element with a Neo field that only contained disabled blocks would cause the blocks to be deleted
- Fixed a bug where
benf\neo\elements\db\BlockQuery::exists()could incorrectly returnfalseif the query wasn't memoized and had no cached result - Fixed a bug where cloned Neo blocks using the child blocks UI element wouldn't have child block buttons
- Fixed a bug on multi-site Craft installs, where Neo revision blocks weren't being saved for entry revisions if the canonical blocks weren't saved for the site that was active when the entry was saved
- Fixed a bug where setting a Neo block as disabled on a provisional draft would cause the disabled state to be lost
- Fixed a bug where reordering a Neo field's blocks could sometimes cause them to move out of order after saving
- Fixed an 'Attempting to duplicate an element in an unsupported site' error that occurred when disabling a section for a site, if any Neo blocks belonging to any of the section's entries were only saved for the disabled site
- Fixed an error that could occur when upgrading to Neo 3.2.0 if using MySQL
- Added the
php craft neo/block-types/deleteconsole command - Added the
php craft neo/block-types/editconsole command - Added the ability to set conditions on the owner elements a Neo block type can be used for, through condition fields for Craft CMS and Craft Commerce element types on the Neo block type settings
- Added
benf\neo\assets\SettingsAsset::EVENT_SET_CONDITION_ELEMENT_TYPES(allowing other plugins to register element types for the Neo block type condition fields) - Added
benf\neo\console\controllers\BlockTypesController - Added
benf\neo\events\SetConditionElementTypesEvent - Added
benf\neo\models\BlockType::$conditionsand added theconditionscolumn to theneoblocktypestable
- Fixed a JavaScript error that occurred when pasting a block type
- Fixed an incorrect German translation of 'Min Blocks' (thanks @alumpe)
- Fixed a bug where the child blocks UI element wasn't appearing on the field layout designer sidebar on existing block types
- Fixed a JavaScript error that occurred when saving an element that doesn't autosave drafts, if a validation error occurred and a new block contained a Redactor field
- Fixed a bug where block type field layout changes would be lost if the Neo field failed to save due to a validation error
- Fixed a bug where blocks that had reached their block type's max child blocks setting were having their add block above, paste, and clone actions disabled, regardless of whether or not they should have been disabled
- Fixed a bug when editing an element via the slideout editor, where new Neo blocks weren't being saved when saving the element
- Fixed a bug when editing a new entry with a Neo field with the propagation method 'Only save blocks to the site they were created in', where new Neo blocks weren't getting duplicated for the other sites
- Fixed a bug where pasting a Neo block would paste it as a child block of the block where the paste action was selected, instead of after that block at the same level, if that block was allowed to have child blocks
- Fixed a bug when saving a provisional draft on a multi-site Craft install, where Neo blocks could be saved at the wrong level, as a result of Neo finding the wrong structure ID for the original entry
- Fixed a bug where unedited Neo blocks were being duplicated in preview mode, when editing a provisional draft, if the blocks were eager loaded
- Fixed an error that could occur when saving a Neo field value if PostgreSQL is being used
- Fixed a bug in Neo 3.1.2 where saving an entry would fail if the database table names used a table prefix
- Fixed a JavaScript error that occurred when filtering out a Neo block type in a case where the block type was already in use; now, Neo blocks with filtered-out types won't be rendered, and will be deleted if structural changes are made to the Neo field
- Fixed a JavaScript error that occurred as a result of cloning a block that uses the child blocks UI element
- Fixed a bug where disabled blocks weren't displaying on entry revisions
- Fixed a bug where block structures weren't being resaved when saving a provisional draft
- Fixed a bug where collapsed Neo blocks had the 'Collapse' action display in the actions menu instead of 'Expand' after saving them
- Fixed an error that occurred when updating from a Neo version prior to 3.0.4, if a Neo-to-Matrix conversion had been performed in the past
- Fixed a bug where Neo fields with enough block types / groups that the buttons wouldn't fit within an element editor page container, on non-active tabs when the page loaded, would still show the buttons (overflowing the editor container) instead of a dropdown
- Fixed an error that occurred when using the
php craft neo/block-type-groups/deleteconsole command if the block type group ID specified didn't exist - Fixed a bug where changes to existing Neo blocks weren't saving for element types that supported drafts but not change tracking
- Fixed a bug where unedited Neo blocks weren't being added to their field's block structure for provisional drafts
- Fixed a bug where
primaryOwnerIdwas being set in the eager loading map criteria instead ofownerId, causing unedited Neo blocks not to appear in preview mode if the Neo field was eager loaded
- Added the
php craft neo/block-type-groups/deleteconsole command - Added the
php craft neo/block-type-groups/editconsole command - Added
benf\neo\console\controllers\BlockTypeGroupsController - Added
benf\neo\enums\BlockTypeGroupDropdown - Added
benf\neo\services\BlockTypes::renderFieldLayoutDesigner()
- Neo block type settings are now rendered in PHP/Twig instead of JavaScript
- When editing a Neo field's settings, the existing block types' field layout designers are now lazy loaded
- Neo input blocks now show the block type's handle next to the name on desktops/tablets, for users who have their 'Show field handles in edit forms' user setting enabled
benf\neo\elements\Block::useMemoized()andbenf\neo\elements\db\BlockQuery::useMemoized()now support being given anIlluminate\Support\Collectionobject
- Fixed a bug where block type groups with blank names would appear in the block type settings sidebar with the name
NULLwhen first loading a Neo field settings page
- Fixed an error that occurred when passing an array of handles to a Neo block query's
type()method
- Fixed a bug where block type groups that only contained non-top-level block types were displaying as a disabled dropdown at the top level on Neo input fields
- Added
benf\neo\models\BlockType::$description(thanks @leevigraham)
- Neo input blocks now have a
data-neo-b-nameattribute (thanks @davidhellmann) - Block type descriptions can appear on hover over new block buttons
- Fixed a bug where copied top level Neo blocks could be pasted into places in the Neo field where that block type shouldn't have been allowed
- Fixed a bug where creating a Quick Post widget with a visible Neo field would cause an error
- Fixed a bug where Neo blocks at the top level that were disabled weren't having their disabled state saved
- Fixed a bug where Neo blocks not at the top level that were disabled weren't being displayed on element editor pages
- Fixed a bug where, when converting a Neo field to Matrix, the old Neo block types and block type groups weren't getting deleted from the database and project config
- Fixed a bug where it was possible to exceed a Neo block type's Max Blocks and Max Sibling Blocks of This Type settings, by pasting blocks that were copied from a different browser tab
- Fixed a bug where running a migration that creates a new entry with Neo content would cause an error
- Fixed an error that could occur on Craft installs upgraded from Craft 3 / Neo 2 when applying project config changes
- The Neo block type settings sidebar now displays block type handles under the block type names
- Fixed a bug where top-level Neo blocks' Paste, Clone and Add Block Above actions weren't being disabled when the field had reached its Max Top-Level Blocks setting
- Fixed a bug where, when selecting a block type tab that has a space in its name, the tab's contents wouldn't display
- Fixed a bug where selecting block type tabs on mobile devices wasn't working
- Fixed a bug where errors that occurred when rendering Neo input HTML would cause Neo input fields to display the "Unable to nest Neo fields" error, instead of displaying the actual error that occurred
- Fixed an error that occurred when querying Neo block contents using GraphQL
- Added Craft 4 compatibility
- Added the ability to show or hide block type group dropdowns where the group only has one available block type
- Added the
defaultAlwaysShowGroupDropdownsplugin setting (defaults totrue) - Added the
alwaysShowDropdowncolumn to theneoblocktypegroupstable - Added
benf\neo\models\BlockTypeGroup::$alwaysShowDropdown - Added
benf\neo\assets\InputAsset - Added
benf\neo\assets\SettingsAsset - Added
benf\neo\controllers\Configurator - Added
benf\neo\jobs\SaveBlockStructures
- Existing Neo input field content is no longer rendered using JavaScript (other than new block buttons)
- Whether a Neo block type's max blocks setting has been exceeded is now validated server-side when saving a Neo field's contents, rather than relying on it to be enforced by client-side JavaScript
- The
neoblockstructurestable'sownerSiteIdcolumn has been renamed tositeId, and thebenf\neo\models\BlockStructureclass's$ownerSiteIdproperty has been renamed to$siteId - The amount of animations and transitions Neo uses is now reduced if the user has requested reduced motion
- When editing a Neo field's block types, creating a new block type will show the settings tab, if the field layout tab was previously showing
- Visual improvements to the Neo block type settings
- Updated JavaScript dependencies
- Deprecated
benf\neo\assets\FieldAsset; users ofEVENT_FILTER_BLOCK_TYPESshould useInputAssetinstead - Deprecated
benf\neo\tasks\DuplicateNeoStructureTask; usebenf\neo\jobs\SaveBlockStructuresinstead
- Removed Craft 3 compatibility
- Removed the unused
saveModifiedBlocksOnlysetting - Removed the unused
ownerSiteIdcolumn from theneoblockstable - Removed
benf\neo\Field::$localizeBlocks; use$propagationMethodinstead - Removed
benf\neo\Field::$wasModified - Removed
benf\neo\Plugin::$blockHasSortOrder - Removed
benf\neo\integrations\fieldlabels\FieldLabels - Removed
benf\neo\converters\Field(Neo Field Converter for Schematic) - Removed
benf\neo\converters\models\BlockType(Neo BlockType Converter for Schematic) - Removed
benf\neo\converters\models\BlockTypeGroup(Neo BlockTypeGroup Converter for Schematic) - Removed
benf\neo\elements\Block::getModified(); use$dirtyinstead - Removed
benf\neo\elements\Block::setModified(); use$dirtyinstead - Removed
benf\neo\elements\Block::$ownerSiteId; use$siteIdinstead - Removed
benf\neo\elements\db\BlockQuery::ownerLocale(); usesite()orsiteId()instead - Removed
benf\neo\elements\db\BlockQuery::ownerSite(); usesite()orsiteId()instead - Removed
benf\neo\elements\db\BlockQuery::ownerSiteId(); usesite()orsiteId()instead - Removed
benf\neo\elements\db\BlockQuery::$ownerSiteId; use$siteIdinstead - Removed
benf\neo\services\Blocks::getSearchKeywords() - Removed
benf\neo\services\BlockTypes::renderTabs() - Removed
benf\neo\services\Fields::getSupportedSiteIdsForField()
- Fixed a bug where it was possible to create a Neo field with no block types
- Fixed an integrity constraint violation that could occur when saving an existing entry that has a Neo field
- Neo will no longer create revision block structures using queue jobs if the Craft project's
runQueueAutomaticallygeneral setting is disabled
- When running Craft garbage collection, Neo will now delete any orphaned Neo block structure data
- Fixed a bug where Neo block structures belonging to provisional drafts weren't being deleted when saving the entry
- Added
benf\neo\jobs\DeleteBlock
- Fixed performance issues when applying entry drafts (deletion of the old draft Neo blocks is now performed by queue jobs)
- Fixed a JavaScript error that occurred when creating a new Neo block type, if Quick Field was used to delete a field group that wasn't created using Quick Field
- Fixed an error that could occur when merging changes to canonical Neo blocks into derivative blocks, due to Neo incorrectly trying to merge changes into derivative blocks that didn't belong to a block structure
- Fixed a bug where Neo block type names could be overwritten by translations on a Neo field settings page
- Added support for the Craft 3 version of the Quick Field plugin
- Fixed a bug where Codeception tests of Neo content were failing if the
dbSetupoption'scleanandsetupCraftwere set to true, due to Neo not finding its block types - Fixed a bug where eager loaded block children queries could return a non-0 indexed array
- Fixed an error caused by Neo that occurred when upgrading from Craft 2 to Craft 3
- Fixed a JavaScript error that occurred when collapsing a Neo block on a global set, which caused the collapsed state of the block not to be saved
- Fixed a bug where filtering memoized block query results by criteria was incorrectly not returning results in some cases
- Fixed a bug where filtering memoized block query results by block type ID(s) would cause an error if an integer was passed instead of an array
- Fixed some performance issues when saving Neo blocks
- Fixed an error that could occur when saving Neo blocks, when checking if a block has a searchable block type
- Fixed a JavaScript error that occurred on Neo field settings pages, when changing a block type's 'Max Sibling Blocks of This Type' value
- Added the
php craft resave/neo-blocksconsole command - Added
benf\neo\elements\db\BlockQuery::field()
- Fixed an error that occurred on a Neo field settings page when copying and pasting a block type that was set to use all of the field's block types as child block types
- Fixed style issues with UI elements on Neo blocks
- Changed the migration from Neo 2.13.0 that adds the
groupIdcolumn to theneoblocktypestable, to set each block type'sgroupin the project config, instead of setting thegroupIdon the block type model and resaving the block type - When applying project config changes and when applying the
groupIdmigration, if any block types still have blank tabs from before Neo 2.8 / Craft 3.5, they will now be kept (but resaving them through the control panel will still cause the blank tabs to be lost)
- Fixed a bug that could cause Neo project config data to not be applied when applying a project config to a different environment
- Fixed an error that occurred when applying a project config from prior to Neo 2.13.0
{warning} If you're updating from a Neo version prior to 2.8.16, you're running a multi-site Craft install, and you've ever changed your Neo fields' propagation methods, run the
php craft neo/fields/reapply-propagation-methodcommand after updating to potentially fix a bug from prior to Neo 2.8.14 where changes to a field's propagation method weren't being applied to their blocks. If that command causes an error, runphp craft neo/fields/reapply-propagation-method --by-block-structureinstead (be aware that this may create many jobs in the queue).
- Added the
groupIdcolumn to theneoblocktypestable - Added the
getGroup()method to theBlockTypemodel - Added the
getGroupById()method to theBlockTypesservice - Added the
FilterBlockTypesEvent, which allows filtering which block types or block type groups display on a Neo field depending on the entry or other element being edited (thanks @myleshyson) - Added the
php craft neo/fields/reapply-propagation-methodcommand with options--field-id=<your comma-separated Neo field IDs here>and--by-block-structure
- Code from a migration added in Neo 2.8.14 and updated in 2.8.16 to reapply Neo fields' propagation methods to their blocks has been moved to the
php craft neo/fields/reapply-propagation-methodcommand
- Fixed a bug that prevented Matrix block menus from working properly within Neo fields (thanks @brandonkelly)
- Fixed a bug affecting multi-site Craft installs, where applying changes to two sites from two different drafts would cause Neo blocks to be duplicated
- Fixed a bug where restoring a trashed entry was not properly restoring the Neo blocks/structures for that entry on multisite Craft installs
- Fixed a bug that occurred when using
craft.neo.blocks(), where trying to set the Neo block query'sownerparameter to an owner element using a criteria array would cause theownerparameter to be ignored
- Fixed an error that could occur when merging live entry Neo content into a draft if a live entry Neo parent block had been deleted in the draft
- Fixed a bug that could cause Neo blocks to be saved out of order
- Fixed a deprecation warning that could occur when eager loading Neo fields on Craft installs that have a custom field with the handle
order
- Added the Custom propagation method
- Fixed a bug affecting element types using the old Live Preview mode (e.g. categories) where unsaved Neo blocks at the top level would be counted as children of the previous top-level block
- Fixed a bug where Neo block queries that were filtering by block ID weren't working in the old Live Preview mode if they were using an array of IDs
- Fixed a bug that could cause the
m201208_110049_delete_blocks_without_sort_ordermigration to fail (thanks @naboo)
- Fixed an error that occurred on Craft 3.7.24 when editing a Neo field's settings
- Fixed a bug involving incorrect merging of Neo block content from drafts and revisions in some cases
- Fixed a bug where GraphQL queries for asset fields in Neo blocks would return no results if the block type handle contained an underscore
- Fixed a bug where GraphQL queries wouldn't return Neo child blocks in some cases
- Fixed a bug where an entry's provisional draft would be created or updated if a Neo block was expanded or collapsed
- Fixed a bug where expanding or collapsing a Neo block on a provisional draft wouldn't also set the expanded/collapsed state on the canonical block
- Fixed a bug when adding new blocks to a Neo field using GraphQL mutations, where queries for the returned data to include child blocks would not return the child blocks
- Fixed an error that occurred when cloning or pasting a Neo block that uses the child blocks UI element
- Fixed a bug where new entry blocks (e.g. from a newly-applied draft) could be merged into the incorrect position of an already existing provisional draft
- Fixed an error that could occur on a multi-site Craft install when saving a new entry from changes to an existing entry, if the entry had a Neo field with a propagation method other than "Only save blocks to the site they were created in" and the entry's section was disabled for any site
- Fixed an issue where getting a Neo block's children in a GraphQL query could cause a deprecation warning to be logged if the block had no children
- Fixed a bug when reverting an entry to a previous revision, where Neo blocks that had since been soft-deleted couldn't be restored
- Fixed a CSS issue with Neo fields in element editor slideouts, where unselected Neo block tab content would still be displayed along with the selected tab's content
- In GraphQL queries, Neo blocks now have a
levelfield
- Fixed a bug where disabled Neo blocks could disappear if validation errors occurred elsewhere in the Neo field
- Fixed a bug where, when saving a Neo field, Neo block types with no child block types could have their
childBlocksvalue stored as an empty string in the project config, rather thannull - Fixed a bug with GraphQL mutations, where mutating an existing Neo block without specifying a level argument would cause it to be moved to level 1 if it was at a different level
- Fixed a potential error when saving an entry
- Fixed an error that could occur with the Gatsby Helper and Gatsby Source plugins
- Neo now requires Craft 3.7.12 or later
- Improved the performance of applying drafts with Neo content, in combination with draft performance improvements in Craft 3.7.12
- Fixed a bug that could cause disabled Neo blocks to be validated when saving
- Fixed a bug where Neo block queries could cause errors in preview mode, if the preview request token had no
draftIdorrevisionIdproperties set
- Fixed a bug affecting element types using the old Craft Live Preview system (e.g. categories) where querying for the children of unsaved blocks would return no results
- Collapsed block previews can now display CodeMirror field content
- Collapsed block previews can now display oEmbed field input content
- Changed the "Move Up" and "Move Down" Neo block action button text to "Move up" and "Move down"
- Fixed a bug where the "Move up" and "Move down" Neo block action button text couldn't be translated
- Fixed an error with the Neo 2.11.6 migration on PHP 7.x
{warning} This release includes a migration to delete old Neo block structure data on single-site Craft installs that could cause duplicate blocks to appear when eager loading or using GraphQL. If your Craft install is single-site, make sure to backup your database before updating Neo.
- Fixed an issue affecting single-site Craft installs, where two Neo block structures could exist for a given field/owner, causing duplicate blocks to appear when eager loading or using GraphQL
- Fixed a compatibility issue with Field Manager (thanks @engram-design)
- Fixed a bug where changing the sort order of Neo blocks without otherwise modifying the Neo field's block structure would cause the new sort order not to be saved
- Fixed a bug where new draft blocks could be lost in some cases when merging updated entry content into drafts
- Fixed a bug where a revision could lose blocks when reverting the entry to that revision
- Fixed a bug where Neo sub-fields' status indicators were not positioned correctly
- Fixed a bug where block children/descendant queries weren't working on draft/revision previews
- Fixed a bug where drafts wouldn't autosave after using the 'move up' or 'move down' Neo block actions
- Neo now requires Craft 3.7.0 or later
- Fixed a bug where Neo field data could be lost when saving an entry, if a new Neo block had been created, and the entry was saved before the provisional draft could autosave after a content change
- Added compatibility with provisional drafts in Craft 3.7
- Added compatibility with canonical/derivative element merging in Craft 3.7
- Added the ability to copy and paste block types between fields
- Neo now requires Craft 3.7.0-beta.6 or later
- Deprecated Neo blocks'
getModified()andsetModified()methods
- Fixed a bug where drafts wouldn't autosave after deleting, cloning or pasting Neo blocks, or when collapsing or expanding blocks by double-clicking the top bar
- Fixed a bug where, when using the 'Add block above' action on a child block, new block buttons for block types that had reached their 'Max Sibling Blocks of This Type' limit were not being disabled
- Fixed a bug when cloning or pasting a Neo block that uses the child blocks UI element, where two child block containers would appear
- Fixed a bug where GraphQL queries for a Neo field's contents with the field's
levelargument set to0would only return level 1 blocks, rather than all blocks belonging to the field
- Added the ability to clone a Neo field's block types within that field when editing the field's settings, from dropdown menus on the block types sidebar
- When editing a Neo field's settings, block types can now be deleted from the new dropdown menus on the block types sidebar
- Fixed a GraphQL error that could occur when accessing a Neo block's children on a query for entries from a non-default site
- Fixed a bug where, if a Neo field was showing the "Add a block" dropdown and a non-empty block type group followed a non-empty block type group, some HTML would fail to be output, causing styling issues
- Fixed an error when saving Neo fields from console commands (thanks @nstCactus)
- Fixed a bug where, when trying to delete all block type group(s) belonging to a Neo field, they would fail to be deleted
- Added the Child Blocks UI element, which allows for putting the child blocks in a single place anywhere in a block type's field layout, rather than displaying them at the bottom of every tab
- Added the
optimiseSearchIndexingplugin setting (enabled by default) - Added the
getByHandle()method to theBlockTypesservice
- Neo now requires Craft 3.6.6 or later
- When Craft runs garbage collection, incomplete Neo element data will now be deleted
- When saving a Neo block that doesn't have a field layout, doesn't have any searchable sub-fields or belongs to a non-searchable Neo field, Neo will now opt out of updating search indexes for that block unless the
optimiseSearchIndexingplugin setting is disabled - Updated Neo fields' 'add block' button styling to match that of Matrix fields' 'add block' button
- Changed Neo's JavaScript dependency package management from Yarn to NPM
- Fixed a bug where Neo input blocks could be dragged to positions where they would exceed their field's Max Levels setting
- Fixed a bug where Neo blocks' enabled and collapsed states weren't retained in some cases when cloning them
- Fixed a bug where, if a Neo field was showing the "Add a block" dropdown, the headings of block type groups would always show, even if none of that group's block types could be added in that position in the field
- Fixed a potential migration error when updating to Neo 2.9.11 or 2.9.12
- Fixed incompatibility with Field Manager (thanks @engram-design)
- Fixed a bug that could sometimes cause Neo blocks to appear out of order
- Fixed a bug when editing a Neo field's settings, where a new block type's handle would not be updated in the child block type checkbox values if the handle was auto-updated as a result of the block type name being updated; if the new block type was then used as a child block type, the child block types array would store an empty string instead of the block type's handle
- Runs a migration to remove empty strings from child block type arrays, which can cause JavaScript errors in the Craft control panel
- Fixed a bug where Neo blocks' children could not be retrieved in GraphQL entry queries when the
draftIdorrevisionIdarguments were used
- Fixed a bug where an error could occur when attempting to apply a project config
- Fixed a bug when viewing the preview of an entry draft or revision, where querying for a Neo block's children or other relatives wouldn't return any blocks
- Added the
allowOwnerDraftsandallowOwnerRevisionsparameters for Neo block queries (thanks @nickdunn)
- Fixed a JavaScript error on Craft 3.6.11 and later
- Fixed a potential 'Invalid owner ID' error when changing a Neo field's propagation method
- Fixed a potential 'Attempting to save an element in an unsupported site' error when resaving entries
- Fixed an error that occurred when publishing a draft with an outdated Neo field (thanks @brandonkelly)
- Fixed a bug that occurred when generating search keywords for a Neo field, where a sub-field's search keywords would be included even if the sub-field was set not to be searchable
- Fixed an issue that occurred on Craft installs running Craft 3.6.7 or later, on which the control panel is accessible on a separate subdomain, where links to an entry in a Redactor field on a Neo block would have unwanted attributes added
- Fixed a bug with Neo 2.9.1 where the max levels warning would display in some cases where it shouldn't display
- Fixed a bug that occurred when a Neo field's Max Levels setting is used, where a Neo block's child block buttons and max levels warnings would not show or hide when the block was dragged to or from the max level
- Added move up/down options to Neo blocks' actions menus
- Added the Max Levels field setting
- Added support for the tag-based cache invalidation introduced in Craft 3.5
- Added support for GraphQL mutations introduced in Craft 3.5
- Added a default English translation file
- Added
getConfig()methods for theBlockTypeandBlockTypeGroupmodels
- Neo-to-Matrix conversion now supports converting Neo fields that have Super Table sub-field(s)
- Updated Neo's project config rebuild code to rebuild based on the
BlockTypeandBlockTypeGroupgetConfig()methods - Neo blocks' tab names will now display in red when a field in that tab has had a validation error
- Fixed a display issue with the tab dropdown button icon on Neo input blocks on mobile devices
- Fixed some padding issues with Neo input blocks
- Fixed a bug in Neo 2.8.22, where an exception could occur when editing a Neo field if one of its block types allows all of the field's block types as child block types
- Fixed a bug when saving a Neo field, where a Neo block type's
childBlocksproperty could mistakenly be set as a string representing an array, rather than an array, which could cause project config formatting issues
- Fixed a bug in Neo 2.8.20 when loading a previously-saved draft, where Neo blocks would fail to resave when changing subfield values
- Fixed a bug when editing drafts, where a Neo block could sometimes fail to resave if its subfield values were set back to the same values it had on page load
- Fixed a bug where, for revisions of entries on sections that were not enabled for the primary site, Neo fields' block structures were not being saved, resulting in all blocks being treated as top-level blocks
- Updated the
standardJavaScript dev dependency to 16.0.3
- Fixed a bug when using a Neo block's
useMemoized()method and accessing a block's children, where a disabled block's enabled descendants would be attached to the previous enabled block existing at the same level as the disabled block
- Fixed a GraphQL bug where, when a query included more than one reference to the same Neo field and did not specify a block level, the returned data would include blocks of all levels, rather than just the top level
{warning} This release includes a migration to hard-delete old Neo block data, no longer associated with an owner element, that may cause errors when setting a new propagation method for their fields. Make sure to backup your database before updating Neo.
- Runs a migration to hard-delete any Neo blocks with an
ownerIdthat doesn't exist in theelementstable; fixes potential issues when setting a new propagation method for the fields those blocks belong to - Fixed an issue where, in some cases, Neo blocks could remain in the database when they should have been hard-deleted
- Rewrote the Neo 2.8.14 migration to fix the "There was a problem getting the parent element" error that could occur in some cases
- Fixed a PostgreSQL error with the migration in Neo 2.8.15 (thanks @boboldehampsink)
{warning} This release includes a migration to soft-delete old Neo block data, no longer associated with any block structure, that may cause errors when setting a new propagation method for their fields. Make sure to backup your database before updating Neo.
- Runs a migration to soft-delete any Neo blocks without a
sortOrder, which could have occurred if any blocks were no longer associated with a block structure prior to Neo 2.7.0; fixes an "Attempting to save an element in an unsupported site" error when setting a new propagation method for the fields those blocks belong to
{warning} This release includes a migration affecting multi-site Craft installations, which reapplies propagation methods to blocks belonging to Neo fields with propagation methods other than "save blocks to all sites the owner element is saved in", due to a bug where changes to a field's propagation method were not being applied to their blocks. If your Craft install is multi-site, make sure to backup your database before updating Neo.
- In Neo's JavaScript code, added the
afterInitevent toNeo.Input
- Fixed an issue on multi-site Craft installs where, when a Neo field's propagation method was changed, the field's blocks were not having the new propagation method applied
- Attempts to apply project config changes that include a Neo block type that belongs to an invalid field UID will now throw an exception immediately on the failure to get the field's ID, rather than still trying (and failing) to insert the block type into the database
- Fixed an issue where Neo block types' field layout UIDs were not being saved in the project config, which could cause attempts to apply project config YAML file changes to fail to apply the correct block type settings on Craft 3.5 releases prior to Craft 3.5.13
- Fixed an issue when performing a project config rebuild, where Neo field layouts could lose their custom labels and UI elements
- Fixed a bug when editing a Neo block type's field layout, where non-required fields that had custom labels or instructions were incorrectly showing as required on the field settings modal
- Fixed some Neo-to-Matrix conversion errors
- Fixed a bug where asset thumbnails on a Neo block's hidden tabs would not be loaded when the tab was selected
- Fixed an issue introduced in Neo 2.8.10 where some more complex GraphQL queries could produce duplicate results
- Added the ability in GraphQL queries to query Neo field data according to the block level (thanks @smcyr)
- Fixed a bug where some eager loading queries of Neo field data could return duplicate block data
- Fixed an error that occurred when executing a Neo block query in which the
fieldIdandownerIdproperties were both arrays
- Fixed a bug when editing a Neo field's settings where, in some cases, sub-fields could incorrectly display as required in the field layout designer
- Fixed a bug with editing a Neo field's settings where, when clicking to delete a block type but then clicking cancel on the confirmation window, that block type would be removed from the Child Blocks settings field on all block types
- Neo now requires Craft 3.5.8 or later
- Fixed a compatibility issue introduced with Craft 3.5.8, where required Neo sub-fields would not appear as required in the field layout designer
- Fixed an issue where saving an otherwise-unmodified Neo block with a newly-added Super Table field, that has either a minimum number or rows or a static row, would cause an "Attempting to duplicate an unsaved element" error
- Neo's JavaScript source has been converted to use the Standard JS style
- Fixed a bug where some GraphQL queries of Neo field data could return duplicate block data
- Fixed a bug where Neo block pasting was not being disabled at the top level if a field had reached its max top level blocks
- Fixed an error that could occur when simultaneously upgrading Craft to 3.5, Neo to 2.8 and Field Labels to 1.3
- Removed all cases of loose equality comparisons in Neo's JavaScript source
- Neo now requires Craft 3.5.4 or later
- Fixed a bug where Neo fields which were set to translatable on a Craft 2 install would not have their propagation method properly set when upgrading to Craft 3
- Fixed a compatibility issue with Craft 3.5.4 when editing a Neo field's settings, where the instructions on block type and block type group settings fields were not displaying properly
- Fixed a compatibility issue with Craft 3.5.4 when editing a Neo block type's field layout, where the hide label checkbox would not work on other fields after checking the box on one field
- Fixed a compatibility issue with Craft 3.5.4 when editing a Neo block type's field layout, where
__blank__would display as a field's label if the field was set to have its label hidden - Fixed a bug when editing a Neo field's settings, where the Field Layout tab would display and be selectable if a block type group was selected
- Some minor changes to JavaScript code related to new block button enabling/disabling, block dragging, and Neo-to-Matrix conversion
- Fixed an issue where child blocks could not be dragged if
Max Sibling Blocks of This Typewas not set on the block type
- When saving a Neo field's settings, existing block type groups are now properly resaved, not just deleted and recreated
- Fixed an error, involving block type group resaving, that could occur when running
./craft project-config/applywhen Craft'sallowAdminChangessetting is disabled - Fixed an error that occurred with Craft 3.5 / Neo 2.8 when rebuilding the project config, if any Neo block type field layout consisted only of blank tab(s)
- Fixed a bug with previous Neo 2.8 releases where default values on dropdown fields were not being applied to new Neo blocks
- Fixed a potential GraphQL "Failed to validate the GQL Schema" error when querying for Neo field data
- Replaced the usage of various deprecated Twig classes
- Neo now requires Craft 3.5.0 or later
- Fixed a CSS issue where unselected Neo block tab content would still be displayed along with the selected tab's content when in live preview mode
- Fixed a CSS issue where unselected Neo block tab content would still be displayed along with the selected tab's content
- Fixed a bug where Neo fields created prior to the 2.8.0 upgrade, and that had not since been saved, would cause the
craft project-config/applycommand to fail, due to the lack ofmaxSiblingBlocksproperty
{warning} As part of the changes to Neo 2.8 to support Craft 3.5's new field layout designer, it's no longer possible to save blank tabs in Neo block types' field layouts. Existing blank tabs should be retained when upgrading to Craft 3.5 and Neo 2.8, but they will be lost if they're still blank next time the field is saved. It's recommended to place a UI element in any blank tabs that should be kept.
- Full support for Craft 3.5's new field layout designer
- Added the
Max Sibling Blocks of This Typeblock type setting, which sets the maximum number of blocks of that block type allowed under one parent block or at the top level
- Neo now requires Craft 3.5.0-RC6 or later
- Updated node-sass to ^4.14.1
- Deprecated
benf\neo\integrations\fieldlabels\FieldLabels - Deprecated
benf\neo\converters\Field(Neo Field Converter for Schematic) - Deprecated
benf\neo\converters\models\BlockType(Neo BlockType Converter for Schematic) - Deprecated
benf\neo\converters\models\BlockTypeGroup(Neo BlockTypeGroup Converter for Schematic)
- Removed unused JavaScript related to compatibility with Quick Field, a Craft 2 plugin which was not updated for Craft 3
- Removed usage of babel-polyfill
- Fixed a bug where validation errors that occurred when attempting to publish a draft were not displaying on Neo blocks
- Fixed the position of the new block type / block type group buttons on the Neo field configurator
- Fixed a bug where Neo-to-Matrix conversion failures were not being logged
- Fixed propagation issues that happen when an entry is enabled for a new site (thanks @brandonkelly)
- Fixed a bug where, when saving a Neo field's configuration, block types' field layouts were being deleted and recreated
- Updated the lodash version requirement in yarn.lock to 4.17.19
- Fixed a JavaScript error preventing Neo input blocks from appearing, if the Neo field had any block types with the handles
filterorpush - Corrected the position of a Neo input block's corner checkbox
- Fixed an issue where, when editing a Neo field and selecting to make the field a Matrix field, the Neo-to-Matrix conversion prompt was not appearing
- Fixed an issue where a Neo field containing a Super Table field would cause Neo-to-Matrix conversion to fail, also causing attempts to uninstall Neo to fail
- Fixed an issue where a collapsed block preview could still cover the settings/drag buttons in some cases
- Fixed the padding between parent block content and child blocks
- Fixed an issue where Neo blocks would show the mobile tab dropdown regardless of the device's screen size
- When loading an element edit page, Neo fields now display a spinner before they load
- Reduced the bottom padding on collapsed Neo blocks
- Fixed the side padding on Neo blocks with no fields or child block types
- Fixed an issue where the fade-out of collapsed block preview text was not displaying correctly in Safari
- Collapsed block previews can now display Linkit field content
- Improved Neo's performance during a project config rebuild
- Fixed an issue with displaying a Typed Link Field's selected type in collapsed block previews
- Fixed an issue where the sort order of Neo blocks was not being set properly when editing an element using an element editor modal, causing new blocks to disappear
- Fixed an issue on entry drafts, where Neo blocks with a level that matched the entry's element ID would have their level overwritten with the entry draft element ID
- Collapsed block previews can now display Category Groups Field content
- Neo now requires Craft 3.4.24 or later
- In combination with an update to Craft 3.4.24, fixes an Exception that could occur when saving an entry (thanks @brandonkelly)
- Fixed issue where unmodified Neo fields on entry drafts were being incorrectly set as modified
- Removed old Reasons plugin compatibility code from the Craft 2 version; fixes JavaScript errors when the Craft 3 version of Reasons is installed
- Fixed issue where disabling a parent block, while editing an entry draft, would cause its child blocks to save at the field's top level
- Fixed bug where collapsed block previews could cover the options dropdown and block drag buttons
- Fixed bug where Neo blocks with asset fields with dynamic upload paths were not finding the correct path when editing a new category or product
- Compatibility with Field Labels v1.2.0
- Fixed bug where blocks' correct modified states were not being set after validation errors, causing block content modified before the validation error, but not after, not to be saved
- Updated neo block styling to be more inline with craft 3.4. #346
- remove void return types since it's not compatible with php 7.0. #342
- changes to v2.7.x migration file #336
- need to pass the id for entries, globals and categories. #333
- remove the type for
_setupBlocksHasSortOrder#342
- better postgresql block query fix (more clean)
- added some changes for when a user is updating craft to 3.4 from an older version
- use
$isModifiedvariable instead within_createBlocksFromSerializedData- thanks @ronaldex
- Fixed an issue when publishing a multisite draft #330, comment of issue
- Added a fix for the neo structure job. Thanks @engram-design.
- Update the block preview on load so it correctly shows the preview. #331
- further changes to the neo structure saving job + changes on how the structure is saved
- Made changes for the neo structure job. #330 #325
- Fixed an issue with the draft and revision creation which children are displaced
- Fixed multisite propagation issue #328.
- Made a change for redactor detection. #329
- Small changes to the block query
- On publish of draft or reverting from revision, create the structure immediately #323, #325
- Fix postgresql issue #257, #324 and fix
sortOrderissue relating to the changes.
- Do not create a structure using a job task if a new entry is being created (since it's duplicated from the first draft). Create the structure immediately.
- we need to change the delay of the observer. redactor has 200ms delay when syncing. #319
- Fixed the migration for
sortOrder, should be using theelementIdinstead ofidforstructureelements- thanks @Mosnar
- need to group by all selected values, not just
sortOrder#316 - add the
structureIdto the element query. #317 #318
- if there are blocks to delete then we need to rebuild the structure.
- Add the
orderByclause for postgres only. #315
{note}
This update contains a schema update which could potentially break the structure of the neo blocks. Make sure to backup your database and do the update locally first as it includes migration of all neo blocks. If the structure is indeed broken, re-saving the page should resolve it. See #336. I'm currently looking into this issue so it's best to wait at version v2.6.x for now.The latest release v2.7.9+ has changes to the migration file + fixes the issue when updating from craft at 3.3 and lower #326 (this is most likely the cause of out of order/missing blocks). The migration should only update the new
sortOrdercolumn for each neo block and shouldn't cause any issues with missing blocks/out of order blocks.
- Added
sortOrderto blocks - Modified how the the structure is being saved. #257
- Re-added the project config read only check.
- Added a migration file that creates a new column (
sortOrder) for theneoblockstable and fills in the data using the current structure elements. #257 - Added further checks for delta updates.
- Added redactor field change detection
- need to check if
wasModifiedis set. #310
- Fix an issue where the neo field couldn't be modified. #310
- Fixed an issue where it was impossible to eager-load fields inside Neo fields. #306. - thanks @andris-sevcenko
- Small change for the delta updates. Should be more reliable in determining which blocks should be updated. #257.
- Group buttons will now be translated. #301.
- If there's an error within a field + it's collapsed, the block name will now be highlighted. #299
- Fixed an issue where it would throw an error about a missing function on the dashboard widgets. #304
- Add German translation - thanks @gglnx
- Media fields using dynamic paths should now show the correct directory when adding/copy/cloning new blocks. #233
- Fixed an issue where the groups wouldn't allow the field to be saved when using the project config + further changes for the group duplicating issue.
- Any required matrix blocks (that's empty) will now correctly highlight the tab to show where the issue is. #299
- Fixed a delta blocks namespace issue if the neo field was called 'blocks'
- Fixed an issue where the structure owner site id is 0 and causes an error when saving. It must be at least the primary site id. (craft 2 -> 3 issue)
- updated the input controller for the namespace change.
- Added Delta support
- Added Multi level ordering
- Fixes and updates for Craft 3.4
- Added
getSupportedSiteIds()
- Deprecated
getSupportedSiteIdsForField(). UsedgetSupportedSiteIds()instead.
- Check if
NerdsAndCompany\Schematic\Converters\Base\FieldandNerdsAndCompany\Schematic\Converters\Models\Baseis available. #286 - Updated
isDraftPreviewto return false if it's a console request - Don't set the project config value if in readOnly mode #217
- Fix #287. Make sure there is post data when saving field labels for neo.
- Fix a GraphQL issue where the children blocks are being returned in an incorrect order. #281.
- Field Labels integration: Fixed issue with blank field layout - thanks @verbeeksteven
- Fix #274 - removal of the data-confirm-unload attr is not needed anymore since a better solution for the "Leave Site" issue was implemented in a previous commit.
- Fixed issue with field labels where removing relabeled field doesn't actually remove them.
- Removed ignoring revision and draft blocks by default in beforePrepare() as it was causing issues with graphql live preview and previewing drafts.
- reflect changes that was made in https://github.com/craftcms/cms/commit/80192a55f8f89b129abff2b43d4a0c7d66d60f45
- update format document spacing
- Fix issue #270
- Stop the blocktype always recreating a fieldlayout.uid - thanks @samuelbirch
- Fix #250. When rebuilding the project.yaml file, the fieldLayouts will now correctly be included
- Fix #263 - correctly get the children blocks (GraphQL)
- Add in a check to make sure we're getting the next level blocks only. (GraphQL)
- GraphQL implementation
- Add GraphQL how to doc
- Fix #232 - make sure to clear the uid when cloning the field so the original doesn't get overwritten when converting.
- Update tar
- Update js-yaml
- Fix #249
- Fix #255, removed 0 index with Field Labels Integration as it causes
Undefined offset: 0
- Field Labels compatibility update
- Fix #243. Revert handleDeletedBlockType changes as it causes some issues when deleting the block types in the neo field.
- fix multi-site issue where on draft creation the contents of the draft is copied over to the other site drafts. #246
- Fixed issue with saving a new entry and the alert that appears (the "Do you want to leave" msg on save).
- Fixed issue with field deletion when there's multi level nested blocks #249
- require the siteId for neo structures for eager loading
- fix getSupportedSiteIdsForField language comparison
- Removed the queue job after changing the propagation method for the neo field as it was causing
Attempting to save an element in an unsupported site.. Propagation changes will be applied once the entry containing the field is saved.
-
added beforeSave function to properly update the neo field propagation method by setting and checking the oldPropagationMethod variable.
-
if PROPAGATION_METHOD_NONE is NOT set for the neo field, make sure to duplicate the block and structures for the other sites using the primary content.
-
Fix indentation of code
- Fix - Need to set the new key for neo structures since the ownerSiteId is now set
- Fixed issue #239
- Fixed indentation, swapped to tabs.
- Cleaned up the Field Service
- update composer
- fix multisite site id block save issue
- fix duplicateBlocks so it creates the neo structure for duplicated blocks
- changes for blockstructure and duplicateBlocks
- remove deletion of blocks from duplicateBlocks function
- FIX: Include 'ownerSiteId' when querying neo structure data.
- fix type error when updating search indexes
- fixes to neo structures for multisite
- deprecate ownerSiteId and additional changes to compensate.
- making neo more inline with craft
- Fix #227 - fixed issue where Neo fields could lose their content when updating to Craft 3.2. - thanks @brandonkelly
- implement BlockElementInterface
- update getOwner and correctly return ElementInterface
- update afterSave
- Fix craft constraint to allow update to 3.2
- Fix #227 - fixed issue where Neo fields could lose their content when updating to Craft 3.2
- Update craft version constraints
- Fix #210 - check if viewing a shared draft so it can retrieve the correct data
- Fix #214 - added in type filtering function that was missing for live preview
- Fix #213 - get enabled blocks only instead of any status blocks for live preview
- Fix PostgreSQL error when saving new block types - thanks @ttempleton
- Fixed issue where groups were duplicated when changing min/max blocks
- Ensure field layout IDs are set when setting a field's block types - Thanks @ttempleton
- Project Config - typecast group sortOrder to int
- Disable saveModifiedBlocksOnly for now
- Added support for the project config rebuild functionality introduced in Craft 3.1.20
- Added the Max Top-Level Blocks field setting
- Added the
collapseAllBlocksplugin setting, allowing all input blocks to display as collapsed by default - Restored the
saveModifiedBlocksOnlyplugin 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
- 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 collapsed block summaries of colour fields on entry revisions
- Fixed issue where duplicate block type groups could be created (thanks @boboldehampsink)
- 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
- Neo now requires Craft 3.1.13 or later
- 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
- Fixed issue in Neo 2.2.4 with disabled blocks being deleted when saving a Neo field's contents
- Now supports filtering an entry draft's Neo field content with query parameters
- Fixed error when creating a new section
- Added support for the CP Field Inspect plugin
- Fixed issue with pasting or cloning blocks where number field values were not retained
- Fixed issue where block types would lose any blank tabs in Neo 2.2.0 and 2.2.1
- 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
- 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)
- Neo now requires Craft 3.1.0 or newer
- Collapsed block summaries now also show content from child blocks
- 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
- 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
- Fixed issue where Neo blocks would not appear on duplicated entries
- Fixed error when pasting or cloning blocks on single-site Craft installations
- Fixed issue where structure IDs were not being set for block queries, causing duplicated blocks to appear in Craft 3.1.0 and newer
- 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
- Fixed error when duplicating an element with a Neo field set not to manage blocks on a per-site basis
- Added the ability to copy multiple selected blocks from different levels, which can be pasted at the same level
- 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)
- Fixed issue where Neo was sometimes causing Craft to fail to delete stale template caches
- Added the ability to copy multiple selected blocks at the same level
- Added Schematic support (thanks @boboldehampsink)
- Restored the Duplicate menu option on blocks -- now named Clone
- Fixed incorrect block levels on drafts of existing entries
- Fixed issues with blocks using memoized datasets for queries
- Fixed field eager loading on PostgreSQL (thanks @boboldehampsink)
- Fixed block previews of unfilled color fields
- Fixed issue where the handle of an existing block type was changing when editing the name
- Fixed 500 error accessing block relatives from relational fields in live preview
- Fixed incorrect block levels being set in drafts
- Set correct Craft minimum version requirement of 3.0.17
- Clean up block structures if duplicates exist, which would cause blocks to appear to duplicate
- Block structure-related fixes
- Restored ability to translate block type names
- Initial release for Craft 3