[EPIC] Edit Content Screen: adoption and rollout
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- java
- 领域
- backend, full-stack
调研方向
Start with the linked child issues grouped under each PR; the epic does not name implementation files or test paths. Read the child issues and their associated code and tests to understand each change. Done means the scoped save, validation, relationship, image editor, legacy field, permissions, rollout, and documentation outcomes are met, with the security EPIC complete before the default editor changes.
由索引模型根据 Issue 内容生成。
描述
Description
First child EPIC of #38634. It holds everything that must be true before content teams use the new Edit Content Screen every day and before new content types default to it: the save and unsaved-changes flow is trustworthy, required fields are always surfaced, relationship fields work at real content volumes, legacy custom fields keep working or have a documented migration, the image editor respects permissions and language, limited users get a usable screen, and the activation docs exist.
Scope is deliberately narrow: defects that lose or corrupt edits, block a save, or make a customer turn the editor off. Visual polish and feature parity live in the second EPIC; refactors in the third. Security findings for the screen are tracked in the private repository EPIC and are referenced here by number only.
Work is grouped by the PR that closes it, so one branch closes a whole row.
Desired Outcome
- A content author can edit any field type, including legacy custom fields, and the "unsaved changes" prompt appears only when something changed.
- Lock, unlock, save and every workflow action keep the author's edits and show the saved result without a manual reload.
- A required field in any tab is surfaced on save: the tab is switched or marked and the field shows its error.
- Relationship fields with thousands of related items load and save without losing relationships.
- Legacy custom fields render without breaking the form, and the DotCustomFieldApi migration path is published.
- The image editor edits the field that was clicked, enforces permissions on the referenced asset, and saves in the asset's language.
- A user without edit permission sees a read-only form and a message, not an empty command bar.
- The rollout decision for new content types is made and implemented; the security EPIC is complete before the default flips.
- The go-to-market documentation is published.
Target Personas
- Developer teams
- Content teams
- DevOps teams
- System administrators (dotCMS)
Links
- Pillar: #38634
- GTM EPIC (done): #35846
- Security EPIC: dotCMS/private-issues#1124
- Side panel everywhere (Product): #38303
- Slack: #feat-edit-content
- Research and QA map: https://claude.ai/artifact/ADYDL6f5366umrfWQ3yzJE
- Architecture review: https://claude.ai/artifact/WCb2nTqHfQ9nXKP9cNriGc
Scope, grouped by the PR that closes it
PR 1 · form state and save flow
- #38034 lock/unlock reverts unsaved relationship edits (absorbs draft PR #38076)
- #36014 fields marked dirty during async load
- #36015 pristine timer races slow fields
- #38643 false "unsaved changes" prompt with custom fields
- #38644 save disables the whole form and gives no confirmation
- #38645 content not refreshed after a workflow action changes fields
PR 2 · validation and workflow selection
- #38174 required field in a non-active tab blocks save silently
- #37996 WYSIWYG implicit language detection blocks save (close if not reproducible)
- #38648 content type without a workflow shows a blank dialog and cannot save
PR 3 · relationship field at scale
- #37734 spike: multilingual and high-volume relationships vs legacy
- #35136 server-side pagination and relationParentIds for
/api/v1/content/search - #38302 folder filter not applied after "Clear all"
PR 4 · image editor and field data correctness
- #38389 image editor opens the wrong field's image when a type has two binary image fields
- #36513 image editor does not enforce permissions on the referenced dotAsset
- #36514 image editor saves in the UI session language
- #38546 WYSIWYG link tool inserts the first-version inode for dotAssets
- #35823 multi-select, checkbox and tag values with commas corrupt stored data
PR 5 · legacy custom fields and WYSIWYG config
- #38664 legacy custom fields stop working after side-panel navigation from a new-editor type to a legacy-editor type
- #38646 legacy custom-field markup and styles break the new form
- #38647 custom-field bridge must guard against
inputevent recursion - #34724 align Host content type behaviour with the legacy editor
- #38514 system-wide TinyMCE config intermittently ignored
- #38007
dot-ui-vtl-migrationskill in agent-toolkit
PR 6 · limited users
- #34787 limited role without the Search tool errors on add or edit
- #38649 user without edit permission sees an empty command bar instead of a read-only form
Rollout
- #32794 guard to redirect between new and old editor
- #37467 go-to-market documentation
- #38650 decide and implement the default editor for new content types (gated on the security EPIC)
Linked, not attached
- #38505 custom-field preview in the content-type editor (PR #38534 open): content-type portlet, not this screen.
- 主要语言
- Java
- 星标
- 972
- 派生
- 493
- 平均合并
- 2 天 12 小时
- 30 天内合并 PR
- 228
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
dotCMS/core 的其他 Issue
-
dotCMS : UVE OKR : Customer Support Team : Maintenance Type : Defect
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 2 天内回复
-
OKR : Customer Support Team : Maintenance Type : Defect
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
Opening content from Content Search replaces the "Search" breadcrumb in the new Edit Content screen未关闭dotCMS: New Edit Contentlet OKR : Customer Support Team : Falcon Type : Defect
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
Escape the Binary field hint in the legacy content editor so an apostrophe doesn't break the field未关闭OKR : Customer Support Team : Maintenance Type : Defect
难度 2/5 1-3 小时 新手友好度 79/100
维护者通常 2 天内回复
-
dotCMS : Permissions OKR : Customer Support Team : Maintenance Type : Defect
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 2 天内回复
相似的 Issue
-
desktop grp:about type:graphics-bug ui-public
难度 1/5 1 小时以内 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 2 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 70/100
it-at-m/Wahllokalsystem#3846 ·
维护者通常 2 天内回复
-
Area/Connector module/solace Priority/Low Type/Bug
难度 2/5 1-3 小时 新手友好度 77/100
ballerina-platform/ballerina-library#9849 ·
维护者通常 1 天内回复