Entry type relabeling#16453
Merged
brandonkelly merged 6 commits into5.6from Jan 19, 2025
Merged
Conversation
Entry types dropped the unique validation rule in 5.3 [ci skip]
[ci skip]
|
This looks like great news - I'm hoping it means that for sites already upgraded, with integers appended to entry type handles all over the place, that can now be undone with the entry type merge command? I am guessing it depends on the detail of each case and whether the outgoing type is the one to keep? |
Member
Author
|
@rob-c-baker You could already use the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds the ability to override entry types’ names and handles on a per-section/field basis.
The UI for it works identically to custom fields within field layout designers: double-click on an entry type (or press the “Settings” action menu item), and a slideout will open showing a chip with the original entry type details, plus “Name” and “Handle” fields. Setting those fields will only affect the entry type’s name/handle within the context of the section/field you’re editing.
Plus, the
global_entry_typesandentrify_matrix_blocksCraft 5 migrations have been updated to preserve sections’/Matrix fields’ original entry type handles, for any handles that need to be renamed for uniqueness. (They’ve also been updated to stop changing entry types’ names for uniqueness, since entry type names dropped the unique requirement in Craft 5.3.)The
entry-types/mergecommand has also been updated to preserve the outgoing entry type’s name and handle, for any usages that support the overrides.Related issues