[Brendyn Montgomery]

I was able to turn this off but not with the code you suggested. This was only a temporary fix to enable me to build the SearchWP extra search engine. After that I had to disable my code in order to continue to be able to add events.

Please get the dev team to limit the scope of your select2 library to your own plugin in the backend, not the whole admin interface.

Here is what I used for anyone else with the same issue:

if ( is_admin()  ) {
        wp_deregister_script( 'tribe-select2' );
    }  

[Brendyn Montgomery]

I hear you that the events calendar needs this for the front end to work and I don’t think that will be a problem. However in the WordPress admin this is a major issue for us that HAS to be resolved as soon as possible.

We have an events site launching very soon. We need to be able to use Search WP search fields that search some custom fields and taxonomies that we have added to the venues and organisers post types. On the front end we are using facetwp for searching and filtering so that works but I need to be able to make a custom Search engine for the search facet with Search WP.

Because your select2 library is loaded all over the place throughout the WordPress admin it seems, I can’t use Search WP in the WordPress Admin, the output of the admin screen is COMPLETELY broken. The Events calendar has no need to have select2 loaded across the entire admin surely when I’m not in the admin for the Events Calendar, I’m in the admin interface for a completely different plugin. If I turn off The Events Calendar then I can use Search WP to make a new search engine but I can’t access the CPT’s for venue or organizer to include them or their custom fields in that search engine and as soon as I turn on The Events Calendar I can no longer edit that custom search engine – so that defeats the purpose entirely.

Conditionally loading your select2 library only when in the edit mode for your plugin in the backend would be a solution I think. I’m a bit short of development chops to sort this but it’s a major show stopper for us at this point.

[Brendyn Montgomery]

Found the download dropdown in my downloads and downgraded to 3.11 and that has resolved the issue.

Should I downgrade events calendar main plugin to 3.11 or will I get away with leaving that as is on 3.12?

[Brendyn Montgomery]

I meant to say, I’d be happy to test out code fixes in order to have this working – I do have a staging site on the same environment that I can play with if that helps.

[Brendyn Montgomery]

While the site is not broken as you say, This is a critical bug for the client, a busy theatre in town. They put up new shows and then use the preview functionality to have other members of staff check the entries before publishing the event live on the site.

I can’t disable events cal pro because they run recurring events and also use the photo view. I’ll have to down grade them if the fix won’t appear before Nov – that’s ages for them, they’ll have to publish about 25 shows before then.

At the moment I have to go in for them and save the permalink each time a new show is added so it doesn’t return a 404 before they can even just visit the url, let alone losing the convince of the “preview” button. It’s some major delay for them each time a show is published waiting for me to respond to their request. They are not quite savvy enough to be trained to save the permalink themselves. They’ve expressed their frustration with this process and I’ve assured them that I’m looking into it as fast as I can.

I’m with Jan – where can I get a previous version of the pro plugin please.

[Author]

Posts