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.

Web Form Not visible on Page!

  1. Hi,
    We are using Gravity Form Version 1.6.10.1, last week we crated we 3 Web forms to make registration. Out of three 2 get stopped work on page, if I am opening FORM directly from WP-Admin , its opening!, But when we placed it on Page its not Visible, Wondering if you know why So?

    3rd one visible on Page, I put some calculation in Total field those calculation not working..however this control able to visible on page.

    Really appreciate for your help!
    Thanks,
    Ken

    Posted 11 years ago on Monday December 17, 2012 | Permalink
  2. David Peralty

    Can you link to your forms on your page that aren't working?

    Posted 11 years ago on Monday December 17, 2012 | Permalink
  3. There are two JavaScript errors on that page which prevent Gravity Forms' jQuery from running and displaying the form:

    Timestamp: 12/17/2012 1:57:35 PM
    Error: TypeError: $(...).dropdown is not a function
    Source File: http://kimbodo.net/lajollaconcours/wp-content/themes/OpenDoor/js/custom.js?ver=3.5
    Line: 5
    Timestamp: 12/17/2012 1:57:35 PM
    Error: TypeError: $(...).unoslider is not a function
    Source File: http://kimbodo.net/lajollaconcours/exhibitors/la-jolla-concours-delegance-registration/
    Line: 201

    Additionally, the page is not valid XHTML and could not be validated. Looking at the source I see a lot of invalid markup. Please fix that as well.

    http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fkimbodo.net%2Flajollaconcours%2Fexhibitors%2Fla-jolla-concours-delegance-registration%2F

    Posted 11 years ago on Monday December 17, 2012 | Permalink
  4. bluewavemedia
    Member

    Hello, I am having the same issue but it is only with one form that has the user registration added to it - all the other forms work perfectly. It is at http://www.breakfastmeetingforwomen.com/membership-application/ - the page is just blank and I have no idea why. Tried deactivating all the plugins one by one - so I know it is not that - just this form - even trying to use the beta user registration to see if that would solve it and it has not - drawing a blank (sorry for the pun ha ha)

    Posted 11 years ago on Wednesday January 9, 2013 | Permalink
  5. Nice pun :-)

    This page loads fine for me:
    http://www.breakfastmeetingforwomen.com/membership-application/

    Screenshot: http://minus.com/l5eD8qa7KThk2

    Are you saying that page comes up completely blank for you?

    If so, you should be able to check the web server error logs and find an error logged which would explain the blank screen.

    Can you try a completely different browser just to be sure that you don't have a cache problem?

    Posted 11 years ago on Wednesday January 9, 2013 | Permalink
  6. bluewavemedia
    Member

    wow that is weird -that is the only form that does come up completely blank for me. All other forms show. Using Mountain Lion with Firefox 17.0.1 - will check in Safari and see if it does come up. Not sure what the heck Firefox would be doing but will check. Glad you enjoyed the pun - need a little humour when the code can drive you crazy.

    Posted 11 years ago on Wednesday January 9, 2013 | Permalink
  7. bluewavemedia
    Member

    okay too weird it does show in safari so firefox is having an issue suddenly. Will check error logs to find that darn gremlin. Thanks so much for your assistance :)

    Posted 11 years ago on Wednesday January 9, 2013 | Permalink
  8. bluewavemedia
    Member

    what I see in Firefox 17.0.1
    https://www.evernote.com/shard/s2/sh/db8ecfd8-4cd6-460b-88ca-d9ad02f52c70/6d9c785f895fd1ed8223a57f5501a250

    Posted 11 years ago on Wednesday January 9, 2013 | Permalink
  9. There is an update to Firefox 18 available (on Windows 7 anyway). Maybe updating will help? Or it's a persistent cache issue. I didn't have a problem with Firefox 17.0.1 and I did not see any JavaScript errors which could be causing the issue either.

    Posted 11 years ago on Wednesday January 9, 2013 | Permalink