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.

Forms disappearing after upgrade to WordPress 3.5

  1. Hi,
    I'm having what seem to be similar issues to some others in the forum. After upgrading to WP3.5, some of my forms are no longer visible in Chrome (v23.0.1271.97), Safari (v5.1.7). The form is present in the page source, but has inline CSS setting "display:none".

    The form does appear as before in Firefox (17.0.1) and Internet Explorer (v9). The form in question is on this page: http://sptc2.the-graphics.net/about-sptc/membership/application-form/
    (For comparison, here is the same from before upgrade to WP3.5: http://sptc.the-graphics.net/about-sptc/membership/application-form/

    The affected forms appear to be those with conditional logic. Other forms, such as this one
    http://sptc2.the-graphics.net/about-sptc/contact-us/ are not affected.

    Hope you can track down the cause of the issue!

    Thanks
    Chris

    Posted 11 years ago on Wednesday December 12, 2012 | Permalink
  2. Should also have said that Gravity Forms is Version 1.6.10

    Posted 11 years ago on Wednesday December 12, 2012 | Permalink
  3. Same to me. Forms aren't shown anymore, even in Firefox 18. I'm using Gravity Forms 1.6.10.1 with Wordpress 3.5 and Suffusion theme framework 3.4.4.

    Also the mask to create new forms won't appear anymore (also on theme twentyten). That's why it isn't just a theme problem.

    Same issue with CSS setting "display:none".

    Here is my link to the form: http://neu.vfmg.ch/bestellformular/#gf_1

    Any help is appreciated. Otherwise we have to downgrade to wp 3.4 :-(

    Posted 11 years ago on Thursday December 13, 2012 | Permalink
  4. My issue seems to be resolved with the v1.6.10.1 update. Many thanks for getting this out so quickly!

    Posted 11 years ago on Thursday December 13, 2012 | Permalink
  5. It is the plugin: WPML String Translation which causes the problem on the admin panel.

    Posted 11 years ago on Thursday December 13, 2012 | Permalink
  6. Thanks for the update Chris.

    Don, were you able to resolve your conflict?

    Posted 11 years ago on Thursday December 13, 2012 | Permalink
  7. I'm having the same issue on one of my client sites that I upgraded to WP 3.5 yesterday. In this site's case it is only the multi-page forms that are not working. All of the single page forms appear to be working correctly.

    You can see the entire list of forms that my client has at http://englishrowseyecare.com/forms/

    I also looked real quickly and it appears that the plugin WPML String Translation is not visibly installed. So where would I go to either disable this plugin or make an adjustment to fix this issue.

    Posted 11 years ago on Thursday December 13, 2012 | Permalink
  8. @sayingitfirst, looks like this JavaScript error on the page is preventing your form from working:

    Timestamp: 12/13/2012 1:27:47 PM
    Error: TypeError: $mainmenu.parent(...).get(...) is undefined
    Source File: http://englishrowseyecare.com/wp-content/themes/parallelus-mingle/assets/js/libs/ddsmoothmenu.js?ver=1.5
    Line: 58

    This is for a dropdown menu on your site. If you can resolve that conflict, and there are no other JavaScript errors, I think your form will display fine. Please post when you have resolved this conflict and we'll look for others.

    Posted 11 years ago on Thursday December 13, 2012 | Permalink
  9. Hi Chris
    I finally downgraded to 3.4.4, since we use this plugin wpml string translation. Our website is in two languages.

    There seem's to be a lot of other problems in other plugins :-(
    So I'll wait a while and will retry in a couple of weeks.

    Posted 11 years ago on Friday December 14, 2012 | Permalink
  10. Sorry for the inconvenience, and thank you for the update.

    Posted 11 years ago on Friday December 14, 2012 | Permalink

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