Open icougil opened 7 months ago
hi @icougil , thank you reporting this bug: I'm able to reproduce the issue in the main branch.
However I'm not able to reproduce the '&' issue.
As a fix, we will do something similar, as it goes further than simply hide a field on the client side:
On the client side: we should hide if there was no value already pre-set, else we display it gray. On the backend: we should allow to re-send disabled value only if the user had already set that value.
This bug affect: checkbox and radiobutton. Select seems to be handled more correctly, but the proposed improvement should allow a more user intuitive flow.
Describe the bug After disabling one of the fields you can include in the "Attendees' data to collect" section, it still appears in the reservation / public view (where the users could buy a ticket).
To Reproduce Steps to reproduce the behaviour:
Expected behaviour We expect not to see the disabled element/s
Screenshots
Admin
Public
Desktop (please complete the following information):
Additional context Side note/another bug?: we found that using the "&" as a Text value in the "Multiple choice (checkbox)" made it impossible to continue with the reservation and, therefore, not move to the buying page.