Search Results for 'dequeue'

[Paul]

Hi Brook,

Thanks for the tip, I am now digging deeper into the world of “dequeueing” than I ever expected, but before I go the the point of modifying anything, I am still getting silly issues with the classic header (removing the options for search and limiting views down to list only at this point but would love to make it wider) and users on Ie 9 (on the boss’ system at the moment). When she scrolls down to the bottom of the events page and clicks to view the next events, she gets a blue warning box that there are none available. In her haste she has clicked the “previous events” link trying to get back, and on the second click (and load) she gets a list of events from 2016 -the latest date in our upcoming events) and a list of “previous events in receding date order from 2016. Any thoughts that it could also be related to the item needing “dequeueing”?

Cheers,
Lacey

[Brook]

Howdy magnus,

I am going to take over this thread on Julie’s behalf, since she will not be able to answer promptly.

It looks like your theme is likely conflicting with the Tribe plugins. To test, could you please try temporarily activating the default 2013 theme, and seeing if the issue persists?

If disabling the theme fixes it:

We have narrowed the issue down to a theme conflict. It is likely that one of the jQuery libraries your theme is loading is either causing jQuery to malfunction, or it is conflicting with a Tribe library. I am noticing console errors even on the week view page. The best way to figure out which script is conflicting is try dequeueing your theme’s scripts one-by-one until you find the conflict. Once you have found the conflicting script, you could look into either replacing it with an alternative, or modifying it to work.

You might also check your theme to see if there are any duplicate elements ids. This sometimes causes jQuery to behave oddly.

If this section of steps sounds a bit like to Greek to you, or you are thinking that some of these tasks are outside of your skillset, you might need to hire a developer to modify your theme your theme more compatible with plugins. If you do not know someone whom you can hire, have no fear. We actually keep a list of freelancers who are quite capable of making changes on your behalf. You can obtain this list by emailing [email protected] and requesting it.

If the issue persisted in the default 2013 theme:

Please keep the 2013 theme enabled, and 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, can you let me know which plugin caused that to happen?

Does that make sense? Did that help you to figure this out and fix it? Please let me know. Cheers!

– Brook

[Brook]

You are very welcome Lacey.

I am afraid I am not aware of any similar themes that I would recommend. If you would be interested in getting the current theme to work it would be as simple as dequeueing the ‘jquery-placeholder‘ script. In the default environment it obviously works, but some how I think that is conflicting with your theme. If I were you I would test out dequeueing it and see if you are still happy with the drop in backwards compatibility that removing if would cause. You might have a little trouble dequeueing it, I do sometimes. This generally relates to mismatched priorities, or dequeueing the script before it is even enqueued. Let me know if this gives you trouble and you are not able to figure it out.

I hope the above advice helps. If there is anything more I can do, then shoot a response. Once is working to your satisfaction, would you mind marking this topic resolved, or dropping a short response to indicate that? Thanks!

– Brook

[Rob]

Hi Gina. Thanks for the follow-up here, and my apologies for the delay in getting you a reply here…I’ve been out of the office until earlier this week, but wanted to follow-up since it seems like you’re definitely unhappy with our service.

I can tell by reviewing this thread that Julie did her best to help you out here – and while it’s a shame our documentation wasn’t enough to get you sorted (we’re doing our best to restructure that in a way that makes more sense for users), I will say that you might run into some problems trying the solution you mentioned here: modifying files directly in the /resources/ folder will cause your change to be overwritten next time you update the plugin (unless you’ve properly enqueued the new one and dequeued the old one). You would instead want to follow the procedure of a template override, which we’ve detailed in the themer docs. We also have a tag cloud for (which brings in a ton of relevant threads that cover the template override process) from the sidebar on this page.

My apologies that we failed to live up to your support expectations. Please do let us know if we can do more to help you and hopefully improve your experience down the road. If you have any further feedback you’d like to share or want to continue this discussion, don’t hesitate to email me (rob @ tri.be).

[Barry]

Hi!

It looks like your theme (or perhaps another plugin) is also setting up Google Maps, resulting in this error:

Warning: you have included the Google Maps API multiple times on this page. This may cause unexpected errors.

A good strategy is to determine which component is also making use of Google Maps (and so our standard troubleshooting steps of deactivating other plugins and switching theme are worthwhile here, even or ideally done on a separate test site). From there, one basic strategy you could employ would be to disable or dequeue those scripts when on event pages.

The process for doing so will vary depending on what else is adding Google Maps support and how it is being added. Assuming it follows regular WP conventions though you could conditionally check if the page is an event page and dequeue it from there, something like this (just an example to show the basic concept, it won’t work “as is”).

You would need to determine what else is adding Google Maps support and determine the script handle they are using (and indeed the point in time at which they add the script) to complete this solution, so touching base with the relevant plugin/theme author isn’t a bad idea.

Does that help?

[Barry]

Hi Andreas: I just wanted to check in with you.

Can you confirm if you (or perhaps a developer you engaged to work on your site) might have dequeued the Google Maps scripts our plugin sets up, swapping it for a Germany-specific version? We’re just exploring why this might have occurred in the first instance – any feedback or insight appreciated!

[ausagventures]

Hey Barry,

Turns out you are correct! This was their response

“Hi Stephanie,

As a matter of fact we do use such a script. Please try this, first create a file named “custom-functions.php” in your theme’s root directory and then add this bit:
<?php

function custom_theme_enqueue_scripts() {
wp_dequeue_script( ‘theme-script’ );
wp_enqueue_script( ‘theme-script’, THEME_URI . ‘/js/themify.custom.script.js’, array(‘jquery’), false, true );
}
add_action( ‘wp_enqueue_scripts’, ‘custom_theme_enqueue_scripts’, 12 );
Now make a duplicate of js/themify.script.js file and rename it to: themify.custom.script.js and open it up. Find:
// HTML5 placeholder fallback
Remove every line after wards until you reach the comment block for the next script which is highlighted as:
// Scroll to top

Hope this helps ;)”

So now I just need to hire a tech to do that for me (my CSS is as advanced as changing font colour and size) and then it should be happy days!

Cheers!!!!

[Brook]

Mathias! I am sorry for this delayed response. There has been a hiccup on our end and I did not see your post.

I guess I was not clear in my recommendation. I was stating that you should should dequeue/deregister  tribe-events-pro-photo as well, specifically because of its dependency. Once dequeued, enqueue your own custom version of tribe-events-photo.js without any dependencies. Ideally you would edit the custom js file to fully remove its isotope calls so you will not see any reference errors in the console. It sounds like you found an alternate method though.

I do appreciate the feature recommendation. We generally only implement an option if there are multiple users in need of it. I searched through our forums and so far you are the only one requesting it. I will definitely keep my ear to the ground to see if others are interested. If you would like to make an official feature recommendation, please add it to our uservoice page — which will allow future users to voice their support as well.

Thank you for posting your resolution. I really appreciate your contributions to our community. Let me know if I can assist you further. And again, sorry for the delay.

– Brook

[Barry]

The problem with removing entire scripts is that other facets besides ajax refreshes may be affected. The snippet you referenced is pretty old and I’m not sure it is still current – we don’t use pjax any longer, for example. You could try dequeuing tribe-events-calendar, though, if you want to explore this approach further (so essentially remove the pjax dequeue statement completely and update the other one to tribe-events-calendar.

Does that help here?

[Brook]

Howdy again,

There is no option for it. If you are feeling adventurous you could certainly dequeue our frontend scripts, then enqueue your custom ones with ajax features removed. It would probably be far easier to just find the conflict though. Usually your Javascript console will show a few errors and help you find the problem, it might even give you something you can check with Google about.

– Brook

[indizio]

Hey Brook,

unfortunately dequeing does not work, because the photo-view is queued as dependent to the isotope file:

tribe-pro-template-factory.class.php
Line: 51
wp_enqueue_script( ‘tribe-events-pro-isotope’, $path1, array(‘tribe-events-pro’), null, true );
wp_enqueue_script(‘tribe-events-pro-photo’, $path2, array(‘tribe-events-pro-isotope’), null, true);

So if I dequeue the isotope file, the tribe-events-pro-photo is also not loaded. Another option would be to detect (wp_script_is) if photo-view.js is loaded and then dequeue and enqueue everything again. But I think this would be a ugly hack in terms of performance, because I also have to localize the script then again.

So my (very) dirty hack by now is modifying $wp_scripts and remove the dependency: https://gist.github.com/anonymous/8299397

As a feature-suggestion:
Option in the backend for “Loading isotope js for photo view” and simply editing the load dependency in tribe-pro-template-factory.class.php accordingly to this option.

Best regards,
Matthias

[Brook]

Howdy Indizo!

Your dequeue script should work perfectly. If you want to overwrite tribe-events-photo-view.js with your custom version I would just take your dequeue idea one step futher. Dequeue tribe-events-photo-view.js as well, then upload your custom version to your theme directory and enqeue it instead.

Does that make sense? Would that work for your situation?

– Brook

[Barry]

Hi ckangell.

That all sounds achievable: your first port of call should be our Themer’s Guide which explains much of the basics.

Prevent user from being directed to events page when they click on

The events are linked to from within the month/single-event.php template … you could simply strip out the <a> link elements that surround the event title.

Display the tooltip onclick rather than on mouseenter

So you’d need to write some custom JS to do this, either building on and working around the existing code or else you could, potentially, dequeue our own Javascript first (however you would lose other client-side behaviours in the process).

[Kelly]

Hi, luckywebs. Unfortunately, I don’t have good news for you. Here are the notes from our developer who took a look:

I logged in with the info you posted and unfortunately, that site doesn’t have the permissions correct for the theme editor to work, so I couldn’t see if they had the gist installed.

There’s not much we can do in these cases, because other plugins or themes enqueuing the Google maps API, alongside ours. The snippet will dequeue ours, but they may even have more than one other plugin enqueuing it, in which case it could still be enqueued multiple times, even when ours is dequeued.

The Google maps API can only be included once in the page, for any maps to work. This isn’t a problem with our plugin; it’s just how google maps works, and they’ll have to make sure their combination of theme and plugins play nice together.

—

I’m sorry we couldn’t make it work for you. Best of luck in your further testing!

[Kelly]

So, it looks like the Google Maps API is loading on the page twice: our plugin adds it, and you have either another plugin or your theme adding it again. This is what’s causing it the image not to display.

Ideally, your other plugin or theme wouldn’t load the google maps api on our pages, but since we don’t know where or how it’s being loaded, we can’t write a snippet to dequeue their include. Here’s one that dequeues ours:

https://gist.github.com/jazbek/7440874

Please add that to your theme’s functions.php file and try it out. That should get you back in business. 🙂