Search Results for 'dequeue'

[Nico]

Hi there @ Wire,

Thanks for reaching out to us! Unfortunately we are not able to provide support in the pre-sales forum 🙁

We are happy to assist our premium users with support issues via our premium forums, please log into the account that has been created when the purchase was made. If you have not purchased one of our premium plugins, you can post in our open source forum. We review that forum weekly and mainly for bug reports.

Regarding the specific issue, you’ll need to dequeue one of the gmaps include. You can do so by using the wp_dequeue_script function.

I’ll go ahead and close out this thread, but please do post in the appropriate forum and we will assist you.

Best,
Nico

[Nico]

Hi Samuel,

Thanks for reaching out to us! I’ll help you on this…

Try adding the following snippet to your theme’s functions.php file:


add_action('wp_print_styles', 'dequeue_tickets_style', 20);

function dequeue_tickets_style ( ) {
wp_dequeue_style( 'event-tickets-rsvp' );
wp_dequeue_style( 'TribeEventsWooTickets' );
}


That should do the trick, let me know about it,
Best,
Nico

[Nico]

Chris,

Sure, I guess that’s the simplest solution. To ‘turn off Ajax’ you’ll need to dequeue some of the scripts that make that work, take a look at this thread that provides a code sample on how to do so for month view.

Best,
Nico

[Josh]

Hey Christofer,

To start, I would like to set expectations for customizations such as these. We’re happy to help point you in the right direction for some of these. However, many times we aren’t able to give full snippets or full details on how a customization could be accomplished.

For the search feature, the simplest approach may be to disable the search bar within the Event Settings > Display tab and use the classic header. You could then use the “‘tribe_events_bar_before_template'” filter to add a new search form or the necessary form from the search everything plugin.

For modifying the format there, take a look at the tribe-events.js file at the “tribe_ev.data” and the “datepicker_formats”. You can copy this file into your theme and modify the “main” to match the “month” there. From there you can dequeue the plugin’s version of this file and enqueue your modified one.

Let me know if this helps.

Thanks!

 

[George]

Good call on the Private Reply, there – and thank you for sharing these files!

I’ve been taking a look through them, and have found that ACF’s loading of its own version of Select2 is pretty straightforward. It labels its script simply ‘select2’, so to make it load everywhere it seems like copying and pasting its enqueue functions into the dequeue function I wrote above would do the trick here.

So, like this:


if ( function_exists( 'acf_get_dir' ) ) {

add_action( 'wp_enqueue_scripts', 'tribe_events_disable_select2', 999 );
add_action( 'admin_enqueue_scripts', 'tribe_events_disable_select2', 999 );

function tribe_events_disable_select2() {
wp_dequeue_style( 'tribe-events-select2-css' );
wp_dequeue_script( 'tribe-events-select2' );

wp_enqueue_style( 'select2', acf_get_dir( 'assets/inc/select2/select2.css' ), '', 'TribeTempFix' );
wp_enqueue_script( 'select2', acf_get_dir( 'assets/inc/select2/select2.min.js' ), array('jquery'), 'TribeTempFix', true );
}
}


I hope this does the trick – note that is a replacement of the original function I shared, so try deleting the old; adding the new; and seeing if anything improves. I apologize in advance if it doesn’t. Let me know!

Thank you for your patience with this bug,
George

P.S.
The bug has been reported in another, separate thread, which means we can bump the priority of the bugfix. I’ve done that, so hopefully it will lead to some more urgent allocating of attention on this bug.

[George]

For sure, Mark – it’s a great tool and one I’m happy to share. In our Non-Profit Partnership Program email exchanges, from time to time folks will ask some general WP questions and that guide is bookmarked as a tool for those situations.

As for the fix, thank you for being patient with it! I’ve bumped the priority on our bug ticket. And while our next release, 4.1, is in its final pre-launch stages–which means that fitting in a bug fix or other small tweaks is very unlikely, save for security-related issues–hopefully we can get this fixed in the releases following that one.

Dequeueing scripts may indeed be a helpful, if temporary, solution. Check out the other thread about this bug if you’re interested in this; I shared some code there that you might be able to copy-and-paste to save some time.

For now, mind if I close up this thread? I’m inclined to close both this and that other bug-report thread to contain the issues, and to make it so that if others have the issue they make a new thread which will only add even more urgency to the fix.

Let me know what you think and if there’s anything else I can help with in this thread!

Cheers,
George

[mrwweb]

Can there be a bad place for a compliment like that? I’m thrilled you knew about Nonprofit WP already, and I would love for you to share it with customers, colleagues, and others looking for helping building out their sites. My goal with that site is [unsurprisingly] to help as many people make good WP sites as possible, so the more people know about it the better.

I’m glad this can help increase the urgency of the fix, and I hope to see a fix soon. If needed, I’ll probably dequeue the script if we really run into troubles.

Thanks again for your help and sharing Nonprofit WP in the future!

[ejimford]

Thanks so much for the reply and for looking into this. I have currently rolled my version of ACF back to 5.3, as suggested by Matt in the initial post. But, of course, not upgrading plugins is not really a long-term solution.

I posed the same question to Eliot over at ACF, but maybe someone here can offer a suggestion: Can you think of a way to, in addition to dequeue-ing the select2 from tribe, doing an enqueue that uses the version of select2 from ACF or another more modern version? Just wondering if there is a fix that we can implement before the new release gets pushed out.

Thanks, again, for you attention and your help with the dequeue-ing funciton.

[George]

I’m sorry to hear about this @ejimford – I made a bug ticket last night for this and it’s something we can hopefully address officially in the release after next, or the very next release if time allows (but, just to be frank, that is not likely because it is fast-approaching).

To prevent The Events Calendar’s versions of Select2 from loading, you can add the following code to your theme’s functions.php file:


add_action( 'wp_enqueue_scripts', 'tribe_events_disable_select2', 999 );
add_action( 'admin_enqueue_scripts', 'tribe_events_disable_select2', 999 );

function tribe_events_disable_select2() {
wp_dequeue_style( 'tribe-events-select2-css' );
wp_dequeue_script( 'tribe-events-select2' );
}


If all you do is use this code to remove the Select2 library from The Events Calendar, and do not then also offer your own version of Select2, the JavaScript on many pages will break. This is because many pages load JavaScript that calls Select2, so if you remove Select2, then this will cause a “not defined…” console error and break JavaScript on the page.

I hope this help, though.

Thank you for your patience with us as we work on an official fix for this!

Cheers,
George

[Josh]

Hey Aaron,

Thanks for reaching out to us!

Unfortunately there doesn’t appear to be a straightforward way to modify this. It looks like you may need to duplicate the “tribe-events-ajax-maps.js” into your theme and customize the map market that gets created within that file. You’ll then need to dequeue the javascript file coming from the plugin and enqueue the customized version within your theme.

Let me know if this helps.

Thanks!

[Brook]

That’s a good question. Enqueueing scripts is a good practice for theme and plugin developers. The main reason to use the enqueue system is because it prevents plugins/themes from loading the same script twice, and allows the site owner (you) to dequeue and make changes as needed.

Using the enqueue system is generally an unnecessary step for site owners like you in this sort of situation though. You already know this script is not going to be loaded by a third party plugin. And any modifications you need to make like choosing when to enqueue and dequeue you can already do since you are the site owner. So it’s up to you. You can learn the enqueue or just plop it in the footer. Both are good options. 🙂

• Brook

 

[Geoff]

Thanks for the feedback and extra info, Francisco! That is indeed helpful and hopefully gives Dylan something to work with as well.

Dylan, I’m afraid it’s tough for us to correct an issue that is coming from the codebase of another plugin. Is there perhaps another sermon management solution that might be able to replace the one currently being used?

If you are able to dig into the conflict a little deeper and see which javascript file(s) are causing the conflicts, then you could use the wp_dequeue_script() WordPress function to remove them from calendar pages. That might look something like:

function dequeue_sermon_scripts() {
if (class_exists('Tribe__Events')) {
wp_dequeue_script( 'ADD SCRIPT HANDLES' );
}
add_action( 'wp_print_scripts', 'dequeue_sermon_scripts', 100 );

Cheers,
Geoff

[Geoff]

My pleasure–happy to help!

I’ll go ahead and close this thread, but it might be worth reaching out to the theme developer before ditching the theme altogether. It looks like theme uses Javascript for loading pages and my bet is that the conflict is somewhere near there. If the theme developer is able to isolate the error and provide a way to perhaps dequeue the script for calendar pages, then you may be able to keep the theme and the plugin together–win, win. 🙂

And, of course, feel free to hit us with a new thread if any other questions–including any from the theme developer–come up and we’d be happy to help as best we can.

Cheers and thanks again for reaching out!

Geoff

[Geoff]

Hey @CDC, thanks for following up!

Yeah, select2 is an integral part of the the calendar and unfortunately cannot be dequeued on it’s own. You could dequeue the script that calls it using a snippet like this:

https://gist.github.com/geoffgraham/22eaf88a8fc1e35f8cdd

I have to warn, however, that it will likely have an effect across the entire plugin as this will deactivate the AJAX feature when filtering events.

If that does not seem to do the trick, then I would suggest trying to dequeue the select2 script on the theme side of things so that it does not interfere with the calendar.

Thanks!
Geoff

 

[George]

Hey Diane,

We unfortuantely cannot provide much help with code tweaking and such, but I’m interested in why the code you shared did not help with this…it looks fine to me. To be clear, did you also add the corresponding and required line of code that looks like this:


add_action( 'wp_enqueue_scripts', 'dequeue_tribe_events_scripts_and_styles' );


If you did not add a line of code like this in addition to the code you shared above, then I would recommending adding both the original block of code and the line of code above to your theme’s functions.php file.

See how things behave.

If issues continue to persist, try setting a different priority on the line of code I shared in this reply – for example, you could tweak the code to have a priority of 99 like this:


add_action( 'wp_enqueue_scripts', 'dequeue_tribe_events_scripts_and_styles', 99 );


I hope this helps!

— George