New Edit Content: the Preview action on a History version does nothing

Abierto
#38,653 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
56/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
frontend

Línea de trabajo

Start with core-web/libs/edit-content/src/lib/store/features/history/history.feature.ts at the PREVIEW case, then compare how the legacy editor previews a version and review the design decision in #38033. Trace which content types have a preview target and where the History action is rendered; add coverage for dispatch and hiding the action. Done means preview opens the selected version as agreed and types without a target no longer show Preview.

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

Each version in the History timeline offers a Preview action. Clicking it has no effect: the store handles the action with an empty case marked as a TODO. Authors expect it to open the version's rendered page, as the legacy editor does from its version list.

Steps to Reproduce
  1. Open a contentlet with several versions in the new editor; open the History tab.
  2. Open the actions menu of any version and click Preview.

Expected: the version is previewed (the rendered page for page or URL-mapped content, or the detail view for other content). Actual: nothing happens, no error.

Acceptance Criteria
  • Preview opens the selected version in the same way the legacy editor previews a version, in a new tab or panel as agreed with design in #38033.
  • Content types with no preview target hide the action instead of showing a dead one.
  • Spec covers the dispatch and the hidden case.
dotCMS Version

main (2026-11-18)

Severity

Minor

Links
  • #38634 pillar; #38033 redesign
  • Code: core-web/libs/edit-content/src/lib/store/features/history/history.feature.ts:693 (PREVIEW case, TODO)
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.