[EPIC] Edit Content Screen: adoption and rollout

Abierto
#38,642 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Java
Estrellas
972
Forks
493
Merge medio
2 d 12 h
PR fusionados (30 d)
228

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotCMS/core

Todos los issues de dotCMS/core

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.