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.

Form won't display after Wordpress 3.5 upgrade

  1. Hi Support Team,

    I have a Wordpress 3.4 site with Gravity Forms 1.6.11 with all forms working.

    My issue is that when I upgrade it to Wordpress 3.5, one very important Gravity form seems to break and will just not show up on the page - http://arch.dyndns.org/kadularissa/idz/idz-book-now/

    All of the other forms (eg http://arch.dyndns.org/kadularissa/whats-on/classes/zouk-lambada-course/) appear fine.

    I am running the Zeux WordPress Theme (found here http://themeforest.net/item/zeux-a-responsive-eshop-wordpress-theme/2514052) and have troubleshooted and found that if I change to Twenty Twelve then the form works.

    It turns out every other piece of the site works fine with my theme on WP 3.5 except this one form (and it just breaks on WP 3.5).

    Can you please help me understand what could be breaking it - any direction would be much appreciated.

    Kind Regards

    Charles

    Posted 6 years ago on Wednesday January 16, 2013 | Permalink
  2. There is something strange going on with the site. I could barely load it in a browser. Once I did, the stylesheets were not present, so I got unstyled content of blue link text on dark grey. Screenshot: http://minus.com/l0shItcyKbAFM

    The page never did finish loading. But in the JavaScript console, I saw nearly a dozen errors, most of which were "jQuery is not defined". Screenshot: http://minus.com/lb22E1y0GQdzV7 When I check the source of the page, I see links like this:

    http://archwebdev/kadularissa/wp-includes/js/jquery/jquery.js?ver=1.8.3

    That's not a fully qualified domain name, so I'm not sure how that could work. Maybe it works differently for you on your machine?

    Also, there is a lot of jQuery functionality going on in that page, and the fact that the form works with Twenty Twelve indicates that the issue is with your theme. However, since I cannot even load the page, I won't be able to help from here. My guess is that your theme is loading multiple copies of jQuery or an older version of jQuery. I just can't be sure because the page barely loads for me, and there are more issues that just a Gravity Forms not showing up.

    Posted 6 years ago on Wednesday January 16, 2013 | Permalink
  3. Hi Chris,

    I can't update the live site (the live form is actually hosted at http://www.kadularissa.com/idz/idz-book-now/) due to it breaking that particular form which is used for commerce so I used the Duplicator plugin to dump off a copy of the site to a local webserver at home which was the previous URL I gave you and upgrade it there to troubleshoot. I have an idea why the copy is looking bad for you externally and will work on that tonight and come back to you to re-request help.

    Thanks - Charles

    Posted 6 years ago on Wednesday January 16, 2013 | Permalink
  4. OK, let us know when it is fully functional online so we can take a look at it.

    Posted 6 years ago on Wednesday January 16, 2013 | Permalink
  5. Hi Chris, please try now - http://arch.dyndns.org/kadularissa/idz/idz-book-now/

    I am able to view it remotely and it looks fine. It is updated to Wordpress 3.5 and the form on this page is now broken but was working fine before the update. Very much appreciate your help!

    Regards,

    Charles

    Posted 6 years ago on Thursday January 17, 2013 | Permalink
  6. The site looks more normal now. Looking at your page, I see this JavaScript error:

    Timestamp: 1/17/2013 8:37:18 AM
    Error: Error: Syntax error, unrecognized expression: #.woocommerce_tabs .panel:not(#.woocommerce_tabs .panel)
    Source File: http://arch.dyndns.org/kadularissa/wp-includes/js/jquery/jquery.js?ver=1.8.3
    Line: 2

    Your theme is including jquery 1.7.1 here:

    <script type='text/javascript' src='http://arch.dyndns.org/kadularissa/wp-content/themes/Zeux-e-Commerce/js/jquery.js'></script>

    in addition to the proper 1.8.3 version here:

    <script type='text/javascript' src='http://arch.dyndns.org/kadularissa/wp-includes/js/jquery/jquery.js?ver=1.8.3'></script>

    Remove the call to the older version in your theme, and so long as there are no additional JavaScript errors, your form will display properly again.

    If you cannot determine where the call to the old jQuery is coming from, you can use our theme and plugin conflict troubleshooting http://rkt.gs/testing

    Based on where it's located, it looks like it's coming from the theme.

    Posted 6 years ago on Thursday January 17, 2013 | Permalink
  7. Hi Chris,

    I found the piece of code that was producing that syntax error in /wp-content/themes/Zeux-e-Commerce/js/scripts.js

    /* Tabs */
    jQuery('#.woocommerce_tabs .panel:not(#.woocommerce_tabs .panel)').hide();
    jQuery('#.woocommerce_tabs li a').click(function(){
                var href = jQuery(this).attr('href');
                jQuery('#.woocommerce_tabs li').removeClass('active');
                jQuery('div.panel').hide();
                jQuery('div' + href).show();
                jQuery(this).parent().addClass('active');
                jQuery.cookie('current_tab', href);
                return false;
    });
    if (jQuery('#.woocommerce_tabs li.active').size()==0) {
                jQuery('#.woocommerce_tabs li:first a').click();
    } else {
                jQuery('#.woocommerce_tabs li.active a').click();
    }

    By removing the # in front of each of the #.woocommerce the error goes away and the form now loads! I'm not sure what the theme writer was doing putting that in there or what else it breaks by removing it but I couldn't find it.

    Thanks again for your help :)

    Charles

    Posted 6 years ago on Saturday January 19, 2013 | Permalink
  8. OK, thanks for the update.

    Posted 6 years ago on Monday January 28, 2013 | Permalink

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