Block Editor asset picker generates inode-based /dA/{inode} video links without a filename/extension

Abierto
#38,502 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
58/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java, typescript
Área
frontend, web-dev

Línea de trabajo

Start at the Block Editor asset picker’s link generation and trace how it gets the asset identifier, filename, and extension; the issue does not name a file or test. Check the generated URLs for video, image, and file assets, then verify inserted videos play behind a CDN or proxy and legacy links still work.

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

Descripción

OKR : Customer Support Team : Scout Triage Type : Defect

Problem Statement

The Block Editor's new asset picker saves selected videos as /dA/{inode} — the ID of a single version, with no filename or extension. Uploads and pre-2026 inserts instead produce /dA/{identifier}/asset/{file}.ext.

Extension-less, version-pinned asset URLs can break downstream CDN/proxy caching of HTTP range requests, causing video playback to fail for site visitors. They also pin the reference to a specific version rather than the content identifier.

  • Front-end issue (asset-picker link generation in the Block Editor).
  • Workaround: asset links in the /dA/{identifier}/asset/{file}.ext form play correctly.

Steps to Reproduce

  1. In a Block Editor field, add a video using the asset picker.
  2. Inspect the generated link/markup for the inserted video.
  3. Observe the URL is /dA/{inode} (a version ID, with no filename/extension) instead of /dA/{identifier}/asset/{file}.ext.
  4. When the content is served behind a CDN/proxy that caches based on the URL/extension, video playback fails for subsequent visitors.

(Reported in the internal dotCMS Slack thread; link omitted.)

Acceptance Criteria

  • The Block Editor asset picker generates identifier-based asset URLs in the form /dA/{identifier}/asset/{file}.ext, including filename and extension, consistent with uploads and pre-2026 inserts.
  • Video assets inserted via the asset picker reference the content identifier, not a single version's inode.
  • Videos inserted via the asset picker play correctly, including when served behind a CDN/proxy that caches by URL.
  • Behavior is consistent across asset types (video, image, file) inserted via the picker.
  • Existing/legacy asset links continue to work unchanged.

dotCMS Version

Latest from main branch.

Severity

High - Major functionality broken (published videos do not play for site visitors).

Links

  • Internal dotCMS Slack thread (link omitted).
  • Freshdesk ticket: NA.
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.