[EPIC] Edit Content Screen: adoption and rollout

未关闭
#38,642 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java

调研方向

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 内容生成。

描述

dotCMS: New Edit Contentlet Epic Team : Scout
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
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 input event recursion
  • #34724 align Host content type behaviour with the legacy editor
  • #38514 system-wide TinyMCE config intermittently ignored
  • #38007 dot-ui-vtl-migration skill 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

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

dotCMS/core 的其他 Issue

查看 dotCMS/core 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。