I'm having an odd experience with radio buttons. Goes like this:

Field 1: Short Presentation / Full-day Seminar

Field 2: (Hidden until Short Presentation is selected)
90 minute / 180 minute

Field 3: (Hidden until Ful-day Seminar is selected)
Day one / Day two

Two question events handle the revealing of Fields 2 & 3. That works fine.

The scenario: User selects Presentation from field 1 and selects a length. Then they change their mind and set field 1 to Full-Day which hides field 2 and reveals field 3. This is fine. It works.

The problem: If the user switches the other direction (from Full-day to Presentation), Immediately after that, field 1 snaps back to Full-Day.. Field 2 remains, as if field 1 hadn't snapped back. If the user clicks it again, it stays where it belongs. Confusing.

Any suggestions?

Yes, both were hidden undil forced visible. and field 2 and field 3 follow field 1.

I found I could make it work in one of two ways:

1) I could create a "set default" event using field 1 to set itself!

2) I changed one of the fields to be not hidden. Then use a "hide" event to hide it. Another event reveals the other field. This creates a more intuitive experience for the user, anyway, since it's better to have one of the fields revealed for a default value on field 1. Previously, neither one showed up until a value had been entered in field 1. Because of how long it takes the form to reload, that was confusing for users.

By the way, the user doesn't see this module until after registration (a different DR module). Is there any way to get the field 1 radio button to default to some value? Right now, it comes up with no choice selected and no setting that I see will change that. I'm assuming that's because we are actually doing an update and there was no value entered in the first place, since the "real" registration form is a different module.

Hi... Yes the default will not default for them if they are authenticated.

Possible solution... ***drum role please****....

Create a hidden field during initial registration called 'SomeField'. Link this field to a core extended field called 'SomeField'. This is added under Admin, User Accounts, Manage Profile Properties. When they register they will automatically set the value of 'SomeField' because the hidden field is set. Lets assume its set to 'No' or 'Yes' etc... Then, during the next page (the update page that is seperate) link that field as well to the 'SomeField' core field. This will then work as the default value you are wanting.

This idea works in theory (in my head) but you would need to test the solution to make sure its working as you need it. As long as you have both the initial hidden field and updated registration linked to a core extended field I don't see why it wouldn't work.


-Chad