Fields DOM container is not rendered when viewing an existing ticket in the simplified interface
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
- 45/100
Línea de trabajo
Compare the standard and simplified ticket-rendering paths for an existing ticket, excluding the native /Form/Render/ form engine. Reproduce the issue with a dom container and the stated entity and profile rights, then trace how container visibility and read/update access are handled. Done means the active container and its fields appear in the simplified view while preserving the standard view behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Code of Conduct
- I agree to follow this project's Code of Conduct
Is there an existing issue for this?
- I have searched the existing issues
GLPI Version
11.0.8
Plugin version
1.24.4
Bug description
Description
An active Fields container of type Insertion in the form (before the save button) (dom) is correctly displayed on existing tickets in the standard interface, but it is not rendered when the same ticket is viewed through the simplified interface.
The ticket itself loads normally and no error message is displayed. The issue seems limited to the rendering of the Fields container in the simplified ticket view.
Container configuration
- Container type:
dom/ Insertion in the form before the save button - Active: Yes
- Associated item types: Tickets, Problems and Changes
- Entity: parent entity of the affected ticket
- Recursive to child entities: Yes
- Affected profile interface: Simplified interface
- Container right tested with: Read and Update
- Display conditions: None during the final test
Steps to reproduce
- Create an active Fields container of type
domassociated withTicket. - Add at least one active field.
- Grant a simplified-interface profile read access to the container.
- Make the container available in the ticket entity, directly or recursively.
- Open an existing ticket in the standard interface and confirm that the container is displayed.
- Open the same ticket using the simplified-interface profile.
- Notice that the ticket is displayed, but the Fields container is missing.
- Grant update access to the profile and repeat the test.
- Remove all container display conditions and repeat the test.
Expected behavior
The active container and its fields should be rendered when an authorized simplified-interface user views an existing ticket. Read access should display readable values, while update access should follow the configured editability of each field.
Actual behavior
The container is displayed in the standard interface but is completely absent from the simplified interface. Changing the container right from Read to Update and removing the display condition do not change the result. No error is shown.
Troubleshooting already performed
- Confirmed that the container is active.
- Confirmed that it is a
domcontainer associated with Tickets. - Confirmed entity visibility and recursive access to child entities.
- Tested both Read and Update profile rights.
- Removed the container display condition.
- Confirmed that the same container works in the standard interface.
- No core or plugin files were modified.
Additional context
This report concerns viewing an existing ticket in the simplified interface. It is not about rendering Fields questions in the GLPI 11 native /Form/Render/ form engine.
Screenshots can be provided for:
- container configuration;
- profile rights;
- missing container in the simplified interface;
- working container in the standard interface;
- container without display conditions.
Relevant log output
Don't have any log.
Page URL
No response
Steps To reproduce
No response
Your GLPI setup information
No response
Anything else?
No response
- Lenguaje dominante
- PHP
- Estrellas
- 116
- Forks
- 82
- Merge medio
- 3 d 4 h
- PR fusionados (30 d)
- 18
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pluginsGLPI/fields
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
pluginsGLPI/fields#1280 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 3/5 1-2 días Aptitud para principiantes 66/100
pluginsGLPI/fields#1270 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
pluginsGLPI/fields#1245 · 4 comentarios ·
Los mantenedores suelen responder en 2 días
-
Dificultad 3/5 1-2 días Aptitud para principiantes 30/100
pluginsGLPI/fields#1015 ·
Los mantenedores suelen responder en 2 días
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
pluginsGLPI/fields#847 · 6 comentarios ·
Los mantenedores suelen responder en 2 días
Todos los issues de pluginsGLPI/fields
Issues similares
-
sync-en
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
Los mantenedores suelen responder en 1 día
-
sync-en
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 3 días
-
Form
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
symfony/symfony-docs#23159 ·
Los mantenedores suelen responder en 3 días
-
bug component: bulk editor support
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Yoast/wordpress-seo#23669 ·
Los mantenedores suelen responder en 3 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
php/frankenphp#2688 ·
Los mantenedores suelen responder en 1 día