Conflict with ACF and select2

[Jason Long]

Hello,

This was definately working until recently so an update to either ACF or Events Calendar/Tickets must have caused the conflict within the last month.

We are using a “Post Object” dropdown on our “Events”, the same dropdown works when added to any other post type except Tribe Events so its definately a conflict with Tribe thats come from somewhere.

Here is the field shown alongside the error: https://www.screencast.com/t/lxqasdMfSQH and here is the same field when attached to a Page: https://www.screencast.com/t/3AQ6qvIkUc

If I remove the tribe version of select2 by dequeueing then the ACF field loads but this isnt an option as it breaks the organiser and venue fields.

We are using the latest versions of all plugins involved (event calendar + pro, event tickets + plus, acf pro)

I have searched online and it seems to be a re-occuring problem with a fix mentioned in a Nov 2017 release.

Thanks

Jason

[Jason Long]

Hello,

Just a quick update… Ive had to roll back to an old version of the site as even with ACF disabled, the ticket plugin on latest version was causing problems. I couldnt add new, or edit existing tickets.

Ive gone back to

ACF: 5.6.10
Event Cal: 4.6.19
Event Cal Pro: 4.4.28
Event Tickets: 4.7.4.1
Event Tickets Plus: 4.7.4

And on these versions all functionality is working as expected.

Are you having problems with adding and editing tickets on latest version?

Thanks

[Sky]

Hi Jason!

Thanks for reaching out. I’m sorry to hear that you’re having issues with the events interface. I will try to help you get this sorted.

Regarding Select2: Our plugins use an older version of Select2 than some other plugin developers, and this has been known to create conflicts.

There is a snippet that has been helping with this issue, but what it does is to only enqueue the older version on events pages. It looks like you may be using ACF on the events admin pages, so I’m not sure if this will be a solution for you.


// Disable tribe select2 function when not in tribe admin screens
add_action( 'admin_enqueue_scripts', 'tribe_select2_conflict_fix', 11);
function tribe_select2_conflict_fix() {
$admin_helpers = Tribe__Admin__Helpers::instance();
if ( ! $admin_helpers->is_screen() ) {
wp_deregister_script( 'tribe-select2' );
}
}


As to your second problem with the tickets, I am not aware of any other reports of this. Do you have a staging site where we can troubleshoot the problem? Do you know specifically which plugin is causing the issue when you update to the latest version?

The first step in troubleshooting would be to update to the latest versions of all Events Calendar plugins. Then, temporarily switch to the twenty seventeen theme and disable all other plugins. If the issue still persists in this state, we can investigate further into why it is happening. If the issue is not present, it means that there is a plugin or theme conflict. To identify the source, you would then enable plugins one at a time until the problem returns.

There is a handy plugin for this, the Health Check Plugin. This will allow you to switch to the default theme and disable plugins for testing, but have it only affect the site for you, while your visitors see everything as normal.

Let me know if you are able to perform those steps, or if you have any questions about it.

Thanks,
Sky

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts