Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[6.x]: Element editor sidebar Nodes can't include links, buttons or inline SVG

Cerrado
#19,909 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
php
Área
backend

Línea de trabajo

Start from the metaFieldsNodes() method on element types and follow how its returned nodes reach the element editor sidebar, including the TemplateContent node that the issue says is sanitized and rendered inert. The open question is whether sidebar nodes should allow links, buttons and inline SVG, which is a sanitization and security decision the maintainers need to make before any code changes. Done would mean an agreed rule for what sidebar content is allowed, plus a test showing a permitted element survives rendering.

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

Descripción

bug repo:cms
What happened?

Element types add sidebar content via metaFieldsNodes(). For read-only rich content the only option is TemplateContent, which is sanitized (inline SVG, buttons and inputs are dropped) and rendered inert, so even links can't be clicked.

My case: a custom Element sidebar would like to show a supporting URL, inline SVG, and a "Download SVG" button. Today, as a workaround, I render the URL as plain text, the inline SVG as an , and moved the download to the action menu.

Previously, I believe we used to be able to render any HTML as additional content in the sidebar. It would be nice to have more flexibility in the sidebar nodes again.

Craft CMS version

6.0.0-alpha.20

PHP version

No response

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions
Lenguaje dominante
PHP
Estrellas
3.6k
Forks
706
Merge medio
12 h 30 min
PR fusionados (30 d)
274

Preparar el entorno

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 craftcms/cms

Todos los issues de craftcms/cms

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.