Code of Conduct
Is there an existing issue for this?
GLPI Version
GLPI CLOUD
Plugin version
1.24.4
Describe the bug
Fields containers are rendered as expected in the classic ticket form
(front/ticket.form.php), but are not rendered at all in the GLPI 11
native form engine (/Form/Render/{id}).
The mandatory constraint, however, is still enforced when the form
destination creates the ticket. The form therefore cannot be submitted,
and the user gets a validation error listing fields that were never shown:
Échec de l'envoi du formulaire, veuillez contacter votre administrateur.
Détails : Des champs obligatoires sont vides : [field labels]
Disabling the Fields plugin allows submission. Unsetting "mandatory" on
each field also unblocks submission, but the fields remain invisible in
the rendered form.
Steps to reproduce
- Create a Fields container of type "block" associated with
Ticket
- Add one or more fields to it and mark them as mandatory
- Open
front/ticket.form.php → the container fields are displayed
- Create a form in Assistance > Forms with a ticket destination
- Open
/Form/Render/{id} → the container fields are not displayed
- Submit → validation fails on those fields
Reproduced with a super-admin profile, so this is not a rights issue.
All profiles defined on the container have write access.
Expected behavior
Either the container fields are rendered in the native form engine, or
the mandatory constraint is not enforced for fields that are not displayed.
Actual behavior
Fields are absent from /Form/Render/{id} regardless of profile, but
mandatory validation is applied at ticket creation, making submission
impossible.
Additional context
As this is a managed Cloud instance, I have no access to the database,
server logs or PHP configuration.
Other installed plugins: rename strings, Alerts.
Code of Conduct
Is there an existing issue for this?
GLPI Version
GLPI CLOUD
Plugin version
1.24.4
Describe the bug
Fields containers are rendered as expected in the classic ticket form
(
front/ticket.form.php), but are not rendered at all in the GLPI 11native form engine (
/Form/Render/{id}).The mandatory constraint, however, is still enforced when the form
destination creates the ticket. The form therefore cannot be submitted,
and the user gets a validation error listing fields that were never shown:
Disabling the Fields plugin allows submission. Unsetting "mandatory" on
each field also unblocks submission, but the fields remain invisible in
the rendered form.
Steps to reproduce
Ticketfront/ticket.form.php→ the container fields are displayed/Form/Render/{id}→ the container fields are not displayedReproduced with a super-admin profile, so this is not a rights issue.
All profiles defined on the container have write access.
Expected behavior
Either the container fields are rendered in the native form engine, or
the mandatory constraint is not enforced for fields that are not displayed.
Actual behavior
Fields are absent from
/Form/Render/{id}regardless of profile, butmandatory validation is applied at ticket creation, making submission
impossible.
Additional context
As this is a managed Cloud instance, I have no access to the database,
server logs or PHP configuration.
Other installed plugins: rename strings, Alerts.