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.
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.
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.
10/03/2016 at 5:12 pm #394118JoshGuest
The conflict reported here and elsewhere should be gone after updating to Event Espresso 4.9.14.p. The earlier change that was included in 4.9.13.p that conflicted with the Connections plugin was removed.10/03/2016 at 5:12 pm #394119
Ok, it was not what I thought it was, not even close. The latest version of EE4 dequeued
jquery-form. You see it in their change set here. I think it has to do with that we both enqueue a third party library
jquery-validatebut with different dependencies and when they dequeue
jquery-formit takes the dependencies with it so the proper scripts are not being loaded on the page which in turn stops the page from functioning correctly.
I do not see a simple solution other than commenting out their change in their code which I have done. The registrations seems to work fine now. I was able to submit one without any errors. Give it a test.10/03/2016 at 5:22 pm #394120
We cross posted… I see the change your reverted. The an implied compatibility issue in the commit message. What is is the compatibility issue? maybe it can be resolved on my side too.10/03/2016 at 5:22 pm #394121JoshGuest
Or you can simply update to the latest version. The dequeueing of the jquery-form script was an attempt to fix a conflict with the Contact Form 7 plugin. Which worked, but ended up making a real mess of things if another plugin had scripts loading on the checkout page and required jquery-form.10/03/2016 at 5:48 pm #394142NashParticipant
Thank you both so much. I cannot express how relieved I am to be running again. These two plugins have saved me so much work and aggravation.
So the changes that you commented out, Steve, are the ones reverted in the update? I might wait until Saturday to do the 4.9.14p update since my registration period will be closed so I won’t be so panicky if things break again. =)10/03/2016 at 6:03 pm #394151
re: So the changes that you commented out, Steve, are the ones reverted in the update?
Well, I only commented out the dequeuing of
jquery-form, if EE4 4.9.14p has other changes they may be other unrelated changes included in the update. Josh would be in a better position to advise. Generally, I also ways recommend updating, so I’m going to go with that for my answer.10/03/2016 at 6:05 pm #394154
As recommended by Josh, the latest update to EE resolves the compatibility issue. It is recommended that you update.10/03/2016 at 6:10 pm #394155
Hmmm… Connections should not load any scripts on your checkout page. We do unfortunately both register
jquery-validatewhich seems to be loaded instead of the copy included in EE4. Likely this is because mine is registered with WP first. If you can send me over a copy of EE4, I’ll load it in my dev site and see if I can tweak my code to ensure it does not to conflict with your checkout page.10/03/2016 at 7:27 pm #394156BrentGuest
You can clone our repo at
I would just like to comment that part of the issue is also that your plugin is somewhat erringly adding
jquery-formas a dependency for the
jquery-validateplugin which isn’t entirely true, as the latter plugin does not depend on the former. It doesn’t require it in any way.
However, we are speculating that you are likely doing this as a way to solve some existing conflicts between those two libraries, and adding
jquery-formas a dependency for the
jquery-validateto be loaded last, which likely prevents some of its functions that you require, from being overwritten by
jquery-form. I would like to add that this could also be achieved by enqueueing those two scripts on different hookpoint priorities. Although maybe you’ve tried that and it wasn’t as bulletproof as what you are doing now. Anyways, if your plugin didn’t claim this false dependency, then it wouldn’t have triggered the issue with ours. That said, we shouldn’t have de-registered any scripts in the first place.
Fun times eh?
Thanks for all of your assistance with regards to this matter.10/04/2016 at 10:53 am #394253Scott ArenaParticipant
updated to EE4 4.9.14 and new formatting issues began. The first name field does not produce any issues now, however in event post page ticket pricing is not displayed and formatting in venue listed has been changed to a “Stretch” kind of row formatting.
This issue began with the update. Issues remains with connection pro activated/deactivated both.
You must be logged in to reply to this topic.