[SOLVED] Radio buttons erronously grouped together

I have…

  • [ ] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

  • [x] Regression (a behavior that stopped working in a new release)
  • [ ] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

Radio buttons seem erronously grouped together. When one changes the value of the radio button in one row, it sets the value to the same for all other rows.

Expected behavior

Radio buttons should be clickable and operable independent of each other. In other words, selecting one value in one row shouldn’t affect the value of the radio button in the next row

Minimal reproduction of the problem

  1. Log into our CMS
  2. Find the right content under the correct schema
  3. Visit the item in which the bug was found
  4. In the section that contains three rows of radio buttons, attempt to choose a value in the first row.
  5. This selection affects the value in the other rows too, setting them to the exact same value.


  • [x] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: From /api/info: version":"

  • [x] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

See attached avi video for visual reproduction.

Also, this behaviour was also seen in a much older version of Squidex, namely:

Thank you in advance,


Apologies, but the comment function didn’t allow video upload, so I added an image with a textual description insted:

What you see here is that whenever I choose, say “Word1”, all three rows of radio button change to the same value, when independent behaviour is default for radio buttons.

Interesting. I will have a look.

Thank you sir! :slightly_smiling_face:


1 Like

I have pushed a fix.

That’s awesome! Does the push also apply to the docker image "image: “squidex/squidex:7"” ? That is, the noproxy version that is documented on Squidex installation pages and downloadable from here:

No, you have to use the latest dev tag: https://hub.docker.com/r/squidex/squidex/tags

This topic was automatically closed after 2 days. New replies are no longer allowed.