Repository navigation
[6.x] Fix new entries in structured collections having no URL until the next request - #15776
Merged
duncanmcclean merged 1 commit intoNov 3, 2026
Conversation
…lection Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
In a structured collection, entries created after the tree has been read in the same request have a
nullURL until the next request. Duplicating entries in the CP runs into this too, so anything listening toEntrySaved(search indexing, static cache invalidation, addons) sees no URL for the duplicates.New entries only get added to the tree when it's read, and the tree is cached for the request. #15238 already flushes that cache when an entry is created, but only for orderable collections. This flushes it for any structured collection.
Fixes #5046
🤖 Generated with Claude Code