Search Results for 'dequeue'

[Barry]

Hi – I’m sorry you’re experiencing difficulties.

If this is occurring on single event/venue pages (in addition to map view) then I think it’s going to be easiest to approach your theme vendor and ask them the same question – then remove their inclusion of the Google Maps API.

The reason I’m suggesting this is that – in our current releases, though a change is in the works – the Google Maps API cannot simply be dequeued the way many other scripts can, nor can the template that loads Google Maps be easily overridden as most other templates can.

With that in mind, if your theme’s author can give you a path forward that’s likely to be the cleanest and safest route here.

Does that help?

[Barry]

Please do feel free to make a feature request – we’d love to hear from you 🙂

An alternative approach though could be to add a stylesheet to your theme (tribe-events/filter-bar.css perhaps) and set it up with the following snippet – which you might add to your theme’s functions.php file:

add_action( 'wp_enqueue_scripts', 'add_filter_bar_stylesheet', 100 );

function add_filter_bar_stylesheet() {
    $custom_stylesheet_path = get_stylesheet_directory_uri() . '/tribe-events/filter-bar.css';
    wp_enqueue_style( 'custom_filter_bar_stylesheet', $custom_stylesheet_path );
}

The slight advantage this would give you is that you would not need to dequeue the existing Filter Bar stylesheet or copy its rules across to your custom version (which would arguably be a more future-proof way of handling this).

I hope that helps and please do post a feature request 🙂

[Brook]

The team just discussed making a list of these and posting it to the website. We are going to do it here soon when we start updating our tutorials for this release. I am glad you brought this to our attention, it was a bit of a pain to track those names down. We certainly don’t want our users to go through pains!

If you have a minute or two, we would love it if you could write a few words about the plugin here. Happy developing!

– Brook

[Marty]

Hi these did the trick, thanks!

I do expect there’ll be more scripts I’ll want to dequeue — I’ve only been looking at the List and Single templates so far, and Grid’s still on my list. I’ll follow your advise and search using “getMinFile.”

That said a comprehensive list in the docs would certainly be helpful.

[Brook]

Howdy martyspellerberg,

Those are a bit of a pain to find. I was able to find each of them by searching the plugins directory for “getMinFile”, which is the function we use to find the minified versions of our scripts. Here are your requests:

1. /the-events-calendar/vendor/jquery-resize/jquery.ba-resize.min.js
2. /the-events-calendar/resources/tribe-events.min.js
3. /the-events-calendar/vendor/jquery-placeholder/jquery.placeholder.min.js
4. /the-events-calendar/vendor/bootstrap-datepicker/js/bootstrap-datepicker.js
5. /the-events-calendar/resources/tribe-events-bar.min.js
6. /the-events-calendar/resources/tribe-events-ajax-list.min.js
7. /events-calendar-pro/resources/tribe-events-ajax-maps.min.js
8. /events-calendar-pro/resources/tribe-events-pro.min.js

Their corresponding handles:

1. ‘tribe-events-jquery-resize’
2. ‘tribe-events-calendar-script’
3. ‘jquery-placeholder’, or if the WooCommerce plugin is active  ‘tribe-placeholder’
4. ‘tribe-events-bootstrap-datepicker’
5. ‘tribe-events-bar’
6. ‘tribe-events-list’
7. ‘tribe-events-pro-geoloc’
8. ‘tribe-events-pro’

We ought to put together a list of script and style handles for users like you. I will bring it up to the team.

Did that work for you? It is possible that I misspelled one of these or grabbed the wrong handle. If so you can double check the code by performing that search, or post back and wait for me to respond. Thanks for posting! If the issue is now resolved, would you mind marking the topic as such? Cheers!

– Brook

[Marty]

PS. Looking at the List view, there’s a few more I’d like to dequeue:

/the-events-calendar/vendor/jquery-placeholder/jquery.placeholder.min.js
/the-events-calendar/vendor/bootstrap-datepicker/js/bootstrap-datepicker.js
/the-events-calendar/resources/tribe-events-bar.min.js
/events-calendar-pro/resources/tribe-events-ajax-maps.min.js
/the-events-calendar/resources/tribe-events-ajax-list.min.js

Thanks!

[Casey]

Thanks for your reply. Let me try to tackle these one at a time.

1. It would seem that the first issue I outlined (spinning/loader just continuously rotates on map view) is being caused by a conflict with the following official WooCommerce extension:
http://www.woothemes.com/products/ajax-layered-navigation/

How can we resolve the issue so both can co-exist together?

Unfortunately, due to our limited support team we’re unable to provide support for specific plugin conflicts such as this one. I would suggest that you reach out to the plugin developer to see if they can help identify the issue further.

2. Even after disabling every plugin (except Events Calendar) I still get the following error on every page:
‘Warning: you have included the Google Maps API multiple times on this page. This may cause unexpected errors’

How can that be resolved?

It’s possible that your theme is also including the Google Maps API. One possibility is to dequeue the extra Google Maps javascript. Take a look at this thread, which outlines the general direction for you to take.

3. The google map issue where the zoom bars and little man are being distorted is still prevalent even when all the plugins are deactivated. So this is obviously a conflict with the premium theme I am using.

How can we isolate what the exact issue is there?

I believe this is also related to #2, so try my suggestion there and see if that gets you started in the right direction.

Thanks! 🙂

-Casey-

[Brook]

Howdy josiah,

If you look at your browser console you will notice the following error “Warning: you have included the Google Maps API multiple times on this page. This may cause unexpected errors.”. What this means is that our plugin has included Google Maps, but so has one of your other plugins or perhaps your theme.

You might try using the WP API to dequeue the other Google Maps script on The Events Calendar pages, as it is most likely not used on these pages. If that is not an option, you would try dequeueing the script ‘tribe-gmaps’. However, some scripts like ‘tribe-events-pro-geoloc’ use that as a dependency so you will likely face some issues.

Finally, you could isolate what bit of code is causing this problem by following these steps:

Try temporarily activating the default Twenty Thirteen theme, and seeing if the issue persists.

If disabling the theme fixes it, we have narrowed the issue down to a theme conflict.

If the issue persists in the default Twenty Thirteen theme, then also disable any plugins other than the ones from Modern Tribe to see if that fixes it. If it does, please try reenabling the plugins one at a time until the issue resurfaces. When it does resurface, which plugin caused that to happen?

Once you have isolated the code down to a plugin or feature of your theme, you can investigate if you are actually using that plugin or feature. If not, disable it!

Please let me know if you have any more questions or if we can be of further helps. Cheers!

– Brook

[Barry]

It may also be you can work around this problem by adding the following code to your theme’s functions.php file – can you give it a shot and if it doesn’t work, reply re my question about the login details?

function limit_range_of_tribe_admin_styles() {
    if ( ! class_exists( 'TribeEvents' ) ) return;
    if ( false === strpos( $_SERVER['QUERY_STRING'], 'tribe' ) )
        wp_dequeue_style( TribeEvents::POSTTYPE . '-admin' );
}

add_action( 'admin_enqueue_scripts', 'limit_range_of_tribe_admin_styles', 20 );

Thanks!

[Barry]

Apologies for the inconvenience.

We’re looking into some changes here, but in the interim could you try adding something like this to your theme’s functions.php file and see if that provides a measure of temporary relief?

/**
 * Crude means of removing events-admin.css from all screens that are
 * not "owned" by The Events Calendar.
 */
function limit_range_of_tribe_admin_styles() {
	if ( ! class_exists( 'TribeEvents' ) ) return;
	if ( false === strpos( $_SERVER['QUERY_STRING'], 'tribe' ) )
		wp_dequeue_style( TribeEvents::POSTTYPE . '-admin' );
}

add_action( 'admin_enqueue_scripts', 'limit_range_of_tribe_admin_styles', 20 );

[libertyme]

Thanks Brook. I’ve gone the dequeue and deregister route, as you’ve suggested, and will look to update our custom enqueued script on major plugin updates. I imagine it’s too niche a request to warrant a theme setting for the datepicker’s format, but throw my hat into that ring anyway. Maybe one day it will be a worthwhile setting to implement.

[Barry]

I do apologize Dan, that should have been visible to you – let me re-post:

OK, so one or other needs to stop enqueuing their copy of the scripts used to interact with Google Maps. Not knowing which version etc is in use by Avada I highly recommend that – at least within the context of event-related pages – you dequeue the libraries set up by Avada.

With that in mind, can you reach out to the theme author and ask for some code to prevent the Google Maps API scripts from being enqueued? Once you are armed with that we can probably complete the puzzle by giving you some code to detect if you are on an event-related page.

Would that work?

So, basically, I can’t give you a snippet to stop Avada from enqueing Google Maps (I don’t have their code in front of me). It seems like a reasonable request you could make of their own support team/author, though, as it’s a fairly simple procedure.

[Brook]

Howdy Kevin!

That’s a good question. Unfortunately the answer is that you can not do this without modifying the script. Personally I prefer to dequeue & deregister scripts like that using WP’ API, then enqueue my own custom version. This allows you to keep your plugin up to date more often, without needing changes. We do modify our tribe scripts though pretty frequently, but mostly in major updates. So if had followed the above advice while running version 3.3 of our plugins then updated  to 3.4, you would likely need to copy over our new JS file and redo your change within. That’s the unfortunate part of the answer.

Does that make sense? Will that work for you? Please let me know. Cheers!

– Brook

[Barry]

Hi – I’m sorry to see you are having problems. Your theme adds the following script:

yoo_master_wp/warp/js/warp.js

My suspicion is that this is causing the problem, but what I don’t know is if it is essential to your theme’s operation or not. With that in mind, can you reach out to the theme author and ask:

• If it is indeed essential and if it can be dequeued (removed)?
• Or, if it does need to be enqueued (available on all pages), can the section of code within it relating to placeholder attributes be removed/stopped from interfering?

Let us know how you get on!

[Brook]

Howdy vserrano,

I am not sure which script you are refferring to. My installation does not have an archive.js.

That said, to dequeue any of our scripts you would use wp_dequeue_script, a built in function of WordPress. They have a good example in that link for dequeueing jquery.js, which is enqueued with the name ‘jquery’:

add_action( 'wp_print_scripts', 'de_script', 100 );
function de_script() {
wp_dequeue_script( 'jquery' );
wp_deregister_script( 'jquery' );
}

This snippet contains a bunch of if{} statements for detecting the various pages. For instance if you wanted to detect if this was a single events page you would use:
if ( tribe_is_event() && is_single() ) { ... }

I hope that helps! Please let me know.

– Brook