[6.x] Fix Replicator Drag & Drop when multiple fields share the same handle#14310
Merged
jasonvarga merged 1 commit into6.xfrom Mar 20, 2026
Merged
[6.x] Fix Replicator Drag & Drop when multiple fields share the same handle#14310jasonvarga merged 1 commit into6.xfrom
jasonvarga merged 1 commit into6.xfrom
Conversation
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.
This pull request fixes an issue where drag & drop in the Replicator fieldtype would become glitchy when multiple fields share the same handle.
This was due to them all outputting the same item/handle classes for the
SortableListcomponent. This PR fixes it by using the field ID instead, which takes the field's path into account.Before
CleanShot.2026-03-20.at.13.41.46.mp4
After
CleanShot.2026-03-20.at.13.40.26.mp4
Fixes #14308