Support has been upgraded!
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Premium Support
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Free Support
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
Tagged: 8.11, extension, form, plugin conflict, quform
- This topic has 1 reply, 2 voices, and was last updated 8 years, 6 months ago by
Steven Zahm.
-
AuthorPosts
-
02/11/2018 at 8:15 pm #451260
Kate Howarth
ParticipantHi
Address button, and other buttons, not working, Simply goes to top of page. Doesn’t give options for users to fill in fields. This has happened before.
https://southeastarts.org.au/south-east-arts-directory/submit/
Please help ASAP as this directory is crucial to our business.
Thanks02/12/2018 at 1:51 pm #451351Steven Zahm
Keymaster@ Kate
Well, this took the better part of my day to track down. I narrowed the cause to Quform. That plugin unregisters a core WordPress javascript file (which is bad practice as it break other plugins) in which Connections Form requires. I had added a check in the core Connections plugin that checked if it was still registered or not and if it was not it would register it again. That was enough to correct the issue for you last time.
I suspect they made a change between last time and now which caused that fix to no longer work. I added an additional check to Form which should hopefully prevent this from happening again.
Another workaround that would have worked… on the QuForm admin settings page under the Performance tab if the “Combine JavaScript” option was disabled that would corrected it too. The reason is that Form would happily use the Quform version of the script that it loads. I suspect changing the “When to load…” option to “Auto” would have also corrected the issue but I did not test that.
Apologies for the trouble! If this does happen again in the future at least we know the first place to look now.
-
AuthorPosts
You cannot reply to this support topic. Please open your own support topic.
