RichardBest
Member
Hi Guys
I've tried to get v 1.4 Beta 1 going but I'm afraid I can't edit my form fields. I've emptied the cache as suggested but that doesn't help. My test site is password protected but I'm happy to give you an admin logon via email if that would help.
Cheers
Richard
An admin login would be good. However, anytime the form fields aren't working and it's not a browser cache issue it is always a plugin or theme conflict. So I would start there. But double check that your browser cache has been cleared first and test it in another browser too before running a conflict test.
RichardBest
Member
Hi again - I've figured out that the plugin conflict is with the Universal Post Manager (UPM) plugin. However, I've never experienced a conflict between UPM and earlier versions of Gravity Forms, including the current release version. It's a plugin I love and rely on. Is there any chance you could take a look at what might be causing the conflict please?
Many thanks
Richard
I'll install that plugin on our end and see if I can replicate the issue. If not, we will be in touch to see it happen on your site.
Can you do me a favor, can you try editing a form with FireBug active to see if there are any Javascript errors on the page? This is most likely the cause.
Here is the issue, Universal Post Manager isn't using best practices and is outputting jQuery on the page when it shouldn't be. This is causing a conflict with the existing jQuery instance that is being output on the page. There are a variety of things wrong with this.
1) Plugins should always enqueue jQuery which detects to see if jQuery has already been included on the page. UPM is not doing this.
2) Plugins should always use the built in version of jQuery rather than bringing their own version of jQuery from within their plugin folder. UPM is not doing this.
3) Plugins should ONLY output Javascript, CSS and Code on admin pages associated with their plugin and NOT on every plugin admin page. UPM is not doing this.
So it's a triple whammy of ignoring best practices when doing WordPress development. I'm honestly surprised Gravity Forms worked at all with UPM because of the issues above. It shouldn't have given what UPM is doing.
There is nothing we can do to Gravity Forms to prevent this from happening as we can't prevent a plugin from outputting code. The change/fix for this would have to come from within UPM and it would have to correct the 3 issues above. At the very least it would have to fix #3.
You will either need to contact the UPM developer or edit UPM yourself (or have someone modify it for you). Ideally the UPM developer would correct their plugin so it uses best practices.
I can try getting in touch with the UPM developer... but it may help if multiple people do as well.
I have received a reply from the developer of the UPM plugin and they claim they are going to make the necessary changes to prevent this from happening.
He replied and said they would take care of it. He thanked me for pointing it out and said they would fix it... that is all I know.
