You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Go to the admin web
Inside the "Attendees' data to collect" section, choose a "Multiple choice (checkbox)" and deselect one of the elements you have added there previously
Save the changes
Go to the reservation/public view and try to buy a ticket. You will still see the previous values in the checkbox
Expected behaviour
We expect not to see the disabled element/s
Screenshots
Admin
Public
Desktop (please complete the following information):
OS: OSx
Browser: Chrome
Version: 121
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.
The text was updated successfully, but these errors were encountered:
As a fix, we will do something similar, as it goes further than simply hide a field on the client side:
we should let the user that had already set this disabled value to view it and resend it, as the user may simply want to update the email or name, we could also gray out the disabled field, this imply that we also need to change the validation rule, as it must consider if the user has already set a disabled value before.
else we should hide it
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
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.
The text was updated successfully, but these errors were encountered: