fostersimonj
Member
Thankfully, I only upgraded my staging server to WordPress 3.1, as it broke the conditional logic forms I was using.
After some digging, it looks like the problem relates to an upgrade of jQuery to 1.4.4. I copied jQuery 1.4.2 into /wp-includes/js/jquery and my forms displayed again.
I grabbed the jquery directory from a copy of WP 3.0.5
- Simon
I upgraded a few WordPress installations to 3.1 today where I use Gravity Forms with conditional logic, and it still works for me. Maybe the javascript is cached or something?
This is the jquery that's being included in my installation:
wp-includes/js/jquery/jquery.js?ver=1.4.4
Can you post a link a broken form of yours? Or is it fixed temporarily by downgrading jquery?
fostersimonj
Member
I assumed the problem was conditional logic, since the two forms that failed have it - and one that didn't doesn't. However, correlation doesn't always equal causation ...
I tried cache clearing, and it didn't make any difference. I then went looking for differences between my production and staging servers, and isolated the problem to jquery. Downgrading to 1.4.2 solved the problem and doesn't appear to have caused any other problems (yet!)
Unfortunately, since it is a staging server I can't post a link showing the problem.
I also haven't encountered any issues with WordPress 3.1 and Gravity Forms using jQuery 1.4.4 and we already have a few thousand customer sites running the same combination so there may be something else going on.
If you can replicate this on a server we can access via a live link we'd be glad to take a look and see what is going on.
I'm having the same problem, when upgrading to 3.1 the forms do not work unless I disable conditional logic. My website address is
http://www.rcgauto.com/about-rcg/
@rcgroup The reason why your form isn't displaying is because you have a non-Gravity Forms related Javascript error on that page related to something called prettyPhoto which uses jQuery. When jQuery encounters an error your browser quits executing it, which means if it quits executing your form won't be displayed because it can't execute.
See this screenshot:
The error is highlighted in the FireBug area at the bottom. You need to resolve this error and it will fix the issue with the form not appearing.
I verified this by testing your page without the JS file this error message references being present and your form displayed as expected.
diywm
Member
I tried the downgrade from jQuery 1.4.4 to jQuery 1.3.2 (the version in the gravityforms/js folder) but found it difficult to prevent later version of the jquery-ui-core or jquery-ui-sortable being loaded. I could get the 1.7.1 jquery/ui version from the gravityforms/js/jquery-ui folder to load but the jquery-ui-core version 1.8.9. was being loaded as well. There were no javascript erors but clicking on the widgets in the sidebar produced no response at all.
Anyway I downgraded my site to WordPress 3.0.5 and everything is working again.
I will wait for gravity forms issue a release that comes bundled with jQuery 1.4.4 before upgrading WordPress
@diywm We haven't had any verifiable issues with WordPress 3.1 and Gravity Forms. It's working fine on all our test sites and the users issue above was an unrelated Javascript issue and not a WordPress 3.1/Gravity Forms issue.
Testing using the Form widget in my WordPress 3.1 installs works fine. I don't have any problems adding Form widgets to sidebars and configuring them.
The jQuery 1.3.2 that ships with Gravity Forms is not used with the form editor, widgets, or on the frontend form. It's only used one place and that is the entry list page column customizer. So Gravity Forms doesn't rely on the jQuery that exists in the gravityforms/js plugin folder for the functionality you are referring to.
I'm running into no issues with WordPress 3.1 and any of the jQuery being used by Gravity Forms while using the jQuery 1.4.4 that ships with WordPress 3.1 and we aren't having widespread reports of this issue, just those limited to this post (one of which was a javascript error unrelated to 1.4.4 or Gravity Forms) and we have thousands of sites running GF and WordPress 3.1.
If you can provide us with an admin login for a site that actively has this issue we'd be glad to take a look and see what is going on.
You can use our Contact Us form and reference this forum post so we know what it is about.
diywm
Member
Karl - I have another site where the form is no longer working since the upgrade to Wordpress. I am using Gravity Forms Version 1.5.beta1. Is it because I am using the beta version do you think?
The problems are that when a form is completed it now doesn't go to an acknowledgment stage - it appears to not react at all. However a message is sent.
When I try to edit the form, the edit screen is blank. I have sent a login to that site as well if you can take a look.
Liz
1.5 beta 1 is an old development release. There have been a lot of changes and enhancements since then so you will want to update it to the latest development release on the downloads page.
Also have you embedded the form using AJAX or no AJAX?
diywm
Member
Latest update. - Upgraded to Version 1.5.RC4.2.
Now neither preview, save, or adding a widget are working on Safari, Firefox or Chrome on a MAC or on Chrome on a PC.
Please see Jing video at http://screencast.com/t/pbeIrUya.
The test was on a moderately complex form. The same holds true for simpler forms.
Not sure what the next step should be
@diywm We'll look into it with the login we have.
Did you upgrade the petplusvet site? How did that go? It's issues should be resolved by the 1.5.RV4.2 release and it was running WordPress 3.1 also.
@diywm Is everything okay with the web host the pushbuttonwp site is on? It's excruciatingly slow, not Gravity Forms but the WordPress admin in general. It also keeps logging me out. I log back in browse some more and then it logs me back out again.
I actually was able to make a minor change to the "Add Google Profile" field, it saved and then I saved it back (I moved a field, then saved it, and then moved it back and saved it). But your WordPress dashboard is slow it's almost unusable on my end. I think your issues are performance related.
There is nothing in the form preview, widget, etc. that isn't 3.1 compatible. Something else is going on with this site. Not being able to save forms, add fields, etc. can be caused by a lack of available PHP memory.
Are you sure everything is okay with this site? Something appears to be wrong with the way it performs in general.
diywm
Member
I killed off 10 plugins and it is working now. It is just possible that the issue was a timeout - how long does Gravity Forms allow the ajax to run before timing out?
The performance issue was logged with our hosting provider today. The LiquidWeb VPS is at 5% of capacity so the issue seems to be with WordPress and not the hardware/CPU/memory/IO.
Somewhat strangely it is only this domain that is performing badly; all the others are fine, so it is proving difficult to track down exactly why the performance sucks on this site.
If you confirm that the ajax times out after 30 seconds then the whole bugginess thing makes complete sense. It can be put down to performance rather than code issues or plugin conflicts.
The petplusvet.com error was down to our .htaccess file converting all URLs to lower case (it was a migrated site that was on Windows before and there were lots of mixed case/upper case incoming links) and you have a single file in gravity forms installation, jquery.textareaCounter.plugin.js, that is of mixed case. This file ended up with a 404. We have fixed this by making the case conversion more specific. [However you should probably rename this file at some point for sake of consistency]
Anyway, many thanks for your help in tracking down the problem which was down to our server and not Gravity Forms.
@diywm Good to hear. I'm not 100% sure what the timeout is on the AJAX without getting with one of the lead developers, I don't know if that is set in the code or has to do with a server configuration. But i'm glad you got things resolved and are working fine now.
Nelson
Member
All our Gravity forms and add ons have quit working with the upgrade to 3.1. Complete failure. The form editor does not react to any input. We are running the most recent beta version. Guess that is what we get for running beta but we really needed the registration module so now we'll have to look for an alternative.
@nelson All 3.1 related issues we have encountered so far have been theme, other plugin or server issue related. We haven't run into a single Gravity Forms or WordPress 3.1 compatibility issue. We'd be glad to look into this issue for you.
It sounds like a PHP memory issue if you are unable to add fields. I'm guessing WordPress 3.1 has greater PHP memory consumption and you are most likely running out of available PHP memory which is causing the issues you are encountering.
Send us a WordPress admin login for the site via our Contact Us form and we will take a look and see what is going on.
@nelson The issue isn't Gravity Forms, it's the Gravity Forms + Constant Contact Add-On you are using. If you edit a form and then view source and scroll to the bottom of the source you will see the error. It's not displaying the error on the page, but there is an error.
Here it is:
Fatal Error: Call to undefined function constant_contact_create_object() in /home/wbous/public_html/wp-content/plugins/gravity-forms-constant-contact/gravity-forms-constant-contact.php on line 325
If you deactivate the Gravity Forms + Constant Contact Add-On you will see the form editor begins working again. So the issue is this 3rd party Add-On. I don't know if it's a 3.1 issue or if there is a problem with the files for this plugin.
That Add-On wasn't created by us, it's a 3rd party Add-On. You would have to get in touch with it's developer if you are unable to determine what is going on. I would suggest first re-installing that add-on from scratch and seeing if that solves the issue.
I'm closing this forum post as it's been taken over by a few different users now for unrelated issues. Please start a new issue rather than posting on another one. Often times issues sound related, when actually they aren't.
