[EPIC] Edit Content Screen: adoption and rollout
メンテナーはふだん 2 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 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時間
- マージ済み PR(30日)
- 228
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- 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 日以内に返信