Every time I try to change a checkbox name or radio choice value so the client will know what is being submitted via the form, the name reverts back to “checkbox 1, checkbox 2, etc.” I change the name, navigate away, go to recheck the name it it reverts back immediately.
Hi @outerwhitespace! This could be happening because you are viewing the site in “Read-Only” mode. Any changes made to the site in read-only mode will not be saved.
I’ve created a short video to further clarify: https://cl.ly/7e7bc6702999
Here is more information within the Webflow University on the ready-only link: https://university.webflow.com/article/sharing-your-sites-read-only-link
Hope this helps!
@johnramos No I am definitely not in read only mode, but thank you. It asked me to post the read only link so i turned it on and did so.
Interesting. Is this issue still occuring?
If the issue persists would you be able to try the following and then trying to change the name of the checkboxes and radio names:
@johnramos It’s sadly still happening. I don’t see any errors in console
Interesting. I am not able to reproduce this on my end. Would you be able to record a short video of what is happening?
I like to use CloudApp to take screenshots, make GIFs, and Screen recordings — makes it super simple!
I have also tried using Safari (which I NEVER use) as well as my normal Chrome with the same issue.
So I was able to find a workaround. If I click on the text part of the checkbox, the name change will stick. But if I click on the checkbox itself it will not stick. I would have assumed, just like fields and labels, that you had to name the input itself (checkbox or radio in this case).
@outerwhitespace. Ah yes, I see what you mean! I was able to reproduce this on my end as well. I will follow up with the team on this and see if it is expected behavior.
Thanks, @johnramos. I would really think that shouldn’t be expected behavior when a user is used to clicking on the fields rather than labels for the other form inputs. So if it is a known issue, hopefully they will look into changing it. Thanks again.
@outerwhitespace For sure, totally agree. I was able to look into this further, and it looks like this is a known issue and it has been reported to the team.
I can’t provide a timeline for when a fix will be available, but someone from the team will reach back out as soon as we know more.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.