Spry radio group validation not being added by CSS Form Builder

I'm using CSS Form Builder (2.0.0 Build 027) to create a form.

It has two pairs of radio buttons which represent a yes/no answer to two separate questions.

I have selected both of them to validate, however no error message is added near the radio buttons or group and no script is added at the bottom of the page which references to buttons.

However there is a link to the script at the top of the page:

<script src="SpryAssets/SpryValidationRadio.js" type="text/javascript"></script>

Could someone tell me how I can get these radio buttons to have validation?

Thanks.

I have created a support ticket so we can look into this issue further.

To view and edit your support ticket, please log into your support history:
supporthistory.php

If anyone else is experiencing this same issue, please append to this thread.

I have exactly the same issue. Did you find a solution for it ?

Regards
Rune

I'll need to troubleshoot directly, see the private message section.

See private message

There is server validation in place for radio groups.

form builder will not add spry validation for the radio groups.

you can force that manually by selecting one of the radio buttons, then go to Insert -> Spry -> Spry Radio Group to convert the radio group to a spry radio group.

I'm not able to force it manually by selecting one of the radio buttons, then go to Insert -> Spry -> Spry Radio Group to convert the radio group to a spry radio group, But it works when I delete the radio group first and then insert a Spry Radio Group with the same name.

Are there any reasons why form builder does not add spry validation for radio groups ?

It is a bug that i have logged in our system to be corrected in the next update.

Has the Spry validation on radio groups been corrected yet?
When selecting validation on a radio group in Form Builder, there are checkbox options for Empty Value & Invalid Value that are specific for Spry validation.

There has not been an update released to correct this bug, it will be corrected when the next update to Data Bridge is released.