UVE: Editing a contentlet inside Block Editor redirects to Content Search instead of staying in context
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
When a user edits a contentlet nested inside a Block Editor within the UVE (Universal Visual Editor), the application navigates to Content Search instead of preserving the UVE page editing context. The Block Editor modal remains open, but the underlying UVE view is replaced by the Content Search view — causing the user to lose their place entirely.
Jalinson Diaz confirmed: "we do not handle nested editing, so maybe it's an enhancement we need".
Steps to Reproduce
- Create a page
- Add a Blog Editor (or any Block Editor) content to the page
- Open the modal to edit the Block Editor content
- Inside the Block Editor modal, select a content type and click Edit on that content type
- Observe: the edit modal opens for the nested content, but the main UVE view behind it is replaced by the Content Search view
Expected Behavior
Editing a contentlet nested inside a Block Editor should keep the UVE page view intact. The edit should open in a nested/stacked modal or handle navigation in a way that preserves the UVE context when the user finishes editing.
Actual Behavior
The main UVE view is replaced by the Content Search view, losing the page editing context entirely.
Acceptance Criteria
- Clicking "Edit" on a contentlet inside a Block Editor modal does not navigate the background UVE view to Content Search
- The UVE page context is preserved when the nested edit modal opens and closes
- After finishing the nested contentlet edit, the user is returned to the Block Editor modal with the UVE page still in the background
Additional Context
- Reported in Slack: https://dotcms.slack.com/archives/C089DJ48C01/p1776802082829149 (includes a screen recording demonstrating the issue)
- This requires implementing nested editing support — currently unhandled in UVE
- Team: Scout (UVE / Page Editor)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the nested-edit flow in the UVE using the listed steps, then trace the Edit action from the Block Editor modal into Content Search. Define the navigation or modal entry point that replaces the background view, and verify that editing and closing the nested contentlet returns to the Block Editor with the UVE page preserved.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100