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.

Conditional Logic Shows Ramdom Field

  1. hasanilx
    Member

    I have conditional logic on section breaks. It works but for some reason it shows a field (different ones at random times) that I never created (or at least deleted and can't see it in the form admin).

    Though the field that randomly appears is different (email, phone, etc) the description is always the same - "This field is for validation purposes and should be left unchanged."

    I'm on my testing server so I don't want to post a link. Will send link to admin for further checking if need be.

    Please advise. Thx

    Thanks

    Posted 9 years ago on Monday September 20, 2010 | Permalink
  2. What you're seeing is the spam honeypot field. It's supposed to be hidden via CSS, but must be inheriting from another rule that's making it visible. I can only guess without seeing it.

    You can try adding this to your theme's style.css file

    .gform_wrapper .gform_validation_container {display:none!important}

    let me know if that works for you.

    Posted 9 years ago on Monday September 20, 2010 | Permalink
  3. Having this same issue. It actually appears to be a bug. The element has an inline style attached to it saying "style="display: list-item; ".

    Also, the CSS added by the plugin goes to the effort of making so many elements use !important - when really it should not. Why make it so awkward for us to overwrite the styles for things like fonts and colors? That is another issue, but of all elements, .gform_validation_container does not use "!important" when it declares "display:none" (looks like forms.css line 205).

    I am also using conditional fields. Maybe the part telling that section to display is adding the inline style?

    Your fix worked for now though. Thx! Hopefully all the hidden validation fields use that same class name?

    Posted 9 years ago on Saturday October 2, 2010 | Permalink
  4. Glad it worked for you.

    As a note, you do have the option to copy the forms.css content to your theme style sheet and then chane the form settings "output css" to "no". That way you can change all the CSS in your theme files to suit and it won't be overwritten on updates.

    Posted 9 years ago on Saturday October 2, 2010 | Permalink
  5. Overall, I liked what the CSS output did - kept font colors, etc. (although not a fan of the fact that you add font-family info - the theme should determine that).

    I feel like copying the css file is a pain. Why? It should be easy to add a few lines to our theme file and that should work.

    Posted 9 years ago on Saturday October 2, 2010 | Permalink
  6. The "output css" feature is there simply to offer that option to those who want it. Some people prefer to get in there & make a lot of changes and it makes it easier.

    Nothing's perfect and everything's open to revision and refinement as we move along. Thanks for the feedback.

    Posted 9 years ago on Saturday October 2, 2010 | Permalink

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