New Edit Content: a historical version opened from the History tab is editable instead of read-only

Abierto
#38,652 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java, typescript
Área
frontend

Línea de trabajo

Start in core-web/libs/edit-content/src/lib/components/dot-edit-content-form/dot-edit-content-form.component.ts at the TODO on line 377, then read the skipped spec at dot-edit-content-form.component.spec.ts:1865. Restore the historical view's disabled state and banner, and check that leaving it restores the working version without marking the form dirty. Run the restored spec to confirm the acceptance criteria.

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

Descripción

dotCMS: New Edit Contentlet Team : Scout Type : Defect
Problem Statement

Selecting an older version in the History tab loads it into the form, but the form stays enabled. The author can type into fields of a version that is not the working one, and the "unsaved changes" prompt then refers to edits that cannot be meaningfully saved. The read-only switch was removed during a refactor and left as a TODO; the spec that covered it is skipped.

Steps to Reproduce
  1. Open a contentlet with at least two versions in the new Edit Content Screen.
  2. In the sidebar, open History and click an older version.
  3. Click into any field and type.

Expected: fields are disabled while a historical version is shown, with a visible "viewing version from " state and a way back. Actual: fields accept input.

Acceptance Criteria
  • While a historical version is displayed, every field and the workflow actions are disabled, and a banner states which version is shown.
  • Leaving the historical view restores the working version and re-enables the form without marking it dirty.
  • The skipped spec "should disable / enable form when exiting historical version view" is restored and passes.
dotCMS Version

main (2026-11-18)

Severity

Serious

Links
  • #38634 pillar; History redesign #38033
  • Code: core-web/libs/edit-content/src/lib/components/dot-edit-content-form/dot-edit-content-form.component.ts:377 (TODO), dot-edit-content-form.component.spec.ts:1865 (it.skip)
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.