PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Radio buttons ignore settings after page break

  1. Dear Gravityforms support team,

    We've use radio buttons with 3 options in it: Like, Neutral and Dislike,
    We gave these's options a value and we've devided those questions with several page breaks, with a total of 4 pages.

    At the first page the radio buttons works great, but at the second, third and fourth page. The buttons ignore the settings.

    At the settings we filled in all the radio buttons should start at the option 'Neutral', but they ignore this and all stand on the option 'Dislike'.

    You can contact us on: for login information.

    Awaiting for your answer.

    Your's faithfully.

    Posted 9 years ago on Tuesday February 26, 2013 | Permalink
  2. Please export this form (Forms > Import/Export then the top center menu item "Export Forms") as XML and email that file to me at - Please include a link to this topic in your email.

    Posted 9 years ago on Saturday March 2, 2013 | Permalink
  3. I created a form on my site with choices pre-selected, and the values hold on each page. You can see my form here:

    The issue with your form is that the values are the same for each radio button choice. That is causing the pre-selected choice to default to the last choice (Dislike) on the pages other than the first page. That is due to how the pages are revealed. For now, you can use different values for each radio button selection, or eliminate the page breaks, and then the Neutral option will always be pre-checked as you set it in the form builder.

    I'll bring this up to the team to see if this is considered a bug or if this is by design and if there is anything we can do to make it work differently.

    Posted 9 years ago on Tuesday March 5, 2013 | Permalink
  4. After hearing back from the development team, the only solution at this point is to use unique values for each selection.

    Posted 9 years ago on Wednesday March 6, 2013 | Permalink