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.

Show or Hide depending on Drop down selection

  1. DeanR
    Member

    I have a dropdown with two options and extra fields.

    When Option A is selected certain fields appear via conditional logic
    When Option B is selected other fields appear.

    The problem I am having is, when Option A is selected and then the user changes their mind and selects Option B, *both* sets of fields appear.

    Is there any way to show fields if the option is selected, but then hide them if another option is selected from the dropdown?

    Thanks.

    Posted 6 years ago on Friday March 15, 2013 | Permalink
  2. Can you please post a link to the form on your site so we can take a look? Also, please let us know what should happen exactly when making the selections. Also, please post screenshots of how you have configured the conditional logic to show and hide these fields. Please use one of the free image hosting sites for the screenshots.

    Posted 6 years ago on Sunday March 17, 2013 | Permalink
  3. DeanR
    Member

    Hi,

    Link is http://www.apinadev.com/feature-requests-and-bug-reports/

    Screenshot 1 http://d.pr/i/x5aE

    Screenshot 2 http://d.pr/i/UaCH

    Select Feature from Feature or bug, text area displays ok. Then change your mind and select bug. Other fields display ok, but the feature text area remains when it should hide again.

    Just noticed there is a jquery error
    Uncaught Error: Syntax error, unrecognized expression: select:not([multiple]
    from the conditional_logic.js file

    Posted 6 years ago on Monday March 18, 2013 | Permalink
  4. David Peralty
    Administrator

    Are you using the latest Gravity Forms and WordPress versions?

    Posted 6 years ago on Monday March 18, 2013 | Permalink
  5. DeanR
    Member

    The latest update seems to have resolved this issue.

    Thanks.

    Posted 6 years ago on Saturday March 23, 2013 | Permalink
  6. Thank you for updating.

    Posted 6 years ago on Sunday March 24, 2013 | Permalink

This topic has been resolved and has been closed to new replies.