[Plugin: liveTV Bundle] Does LiveTV cause jQuery to load differently? (other plugins break)

jQuery to load differently?

No. The plugin uses a maximum of wordpress standard for all php script and the default wordpress standard to enqueue/register all scripts.

wp_register_script('script', 'src_to_the_script', array('dependance'));

where dependance is attached to the default jquery version includes by wordpress and in wordpress.

and after all wp_enqueue_script are loaded only if it is necessary and in the page where shortcode is.

A better way to view where the problem comes from, it’s to make a search on cycleW for all your files in your wp-content folder and looks if one javascript library is loaded maybe two times (your theme, one plugin, and this plugin).

https://tubepress.org/demo/ (same result pagination). Maybe tubepress used the same JQuery extension for pagination.

If it’s the fact, you may stop the load of JQuery extension for pagination and makes test to view if the pagination yet works after this stopping.

you may delete in /page-frontend/page-livestream.php ~line 293

wp_enqueue_script('livetv-pagination');

cycleW comes from a JQuery extension and it’s loaded for the slide effect between the div share/div Chat.

A maximum of the necessary JQuery code/JQuery extensions/JQuery dependancies for my plugin are loaded only if it’s the page where the shortcode is.

(except q-tip because it is necessary also for the widget)

Hi,

Commenting out didn’t break anything, but it didn’t fix it either. Error remains the same. I searched for cycleW as you said. This is the output:
https://pastebin.com/raw.php?i=c1vZzLKF

Looking at this, it seems that NextGEN is interfering? Though is there anything that can be done to fix that?
I don’t need the slider on the top (IRC/Share) so I did delete that in the php code as you suggested in another thread. It didn’t fix the problem though. (I have the widget completely disabled as well, so it’s probably not that either)

Thank you in advance,

frontend.js is an extension for JQuery

/*
* jQuery Easing v1.3 – https://gsgd.co.uk/sandbox/jquery/easing/
* TERMS OF USE – jQuery Easing
* Open source BSD License.
* Copyright ?? 2008 George McGinley Smith
* All rights reserved.
*/

comment in /page-frontend/page-livestreams.php @line ~ 55

wp_enqueue_script('livetv-beautiful-effect');

to stop this load for the plugin (but it’s preferable, to stop the load of your slider/Lightbox if the slider/Lightbox isn’t displaying on that page…).

why the php code for the sliderpost/Lightbox, loads its js file everywhere while there are needs that only where the sliderpost/Lightbox is displayed ? Now you must changes the liveTV code (@risk for css bugs) for another plugin…

Thanks, – however nothing changed when I commented it out. I did clear the cache.

If it helps to see the error yourself:
Add this in the hosts file, the site is not online yet so need to manually set the IP/hostname:
178.79.129.186 obeygaming.com www.obeygaming.com

The site is: https://obeygaming.com/community/
You can see the Livestreams, Videos (TubePress) and screenshots there. You’ll see that the thumbnails under Videos aren’t clickable, and when opening screenshots it doesn’t open in a Lightbox.

Thank you,

I have editing my previous message when you answered. View the previous message.

I’m sorry – I’m a bit confused:

From what I understand the actual issue is that NextGEN Gallery loads its .js files on all pages, so including the ones where it is not needed/shouldn’t be loaded. This messes up LiveTV, which needs some of the same functionality from certain files, thus messing up because it’s being used twice. Correct?

Now the workaround should be to comment the following, even though it’s kind of a “hack”, and not the best solution:
wp_enqueue_script('livetv-beautiful-effect');

I did comment this out, but the issue was not fixed. So can we be sure this is the problem?

I agree that NextGEN shouldn’t load when it’s not needed, and I will also make a support thread there. However, if there is a temporary fix possible that would be great.

Thanks ??

Hi,

It seems that there’s actually a plugin to let NextGEN Gallery only load when required: NextGEN Gallery Optimizer. This seems to have fixed the issue partially. Another problem now occurs: On other pages (not LiveTV)I get the following error:

[cycle] terminating; too few slides: 0 frontend.js:8

Uncaught TypeError: Cannot call method 'hide' of undefined jquery.fancybox-1.3.4.pack.js:18
H jquery.fancybox-1.3.4.pack.js:18
C jquery.fancybox-1.3.4.pack.js:19
a.fn.fancybox jquery.fancybox-1.3.4.pack.js:38
f.event.dispatch jquery.js:3
f.event.add.h.handle.i jquery.js:3

On the following page for example: https://obeygaming.com/community/media/screenshots/
The error occurs once you click a screenshot. The frontend.js there points to a LiveTV file, even though this is not a LiveTV page. Could that be causing the issue now?

Thanks!

Alright I’ve been trying stuff out again and got something that might(?) help…

The Uncaught Call method ‘hide” error was a side-effect of the new plugin: NextGEN Gallery Optimizer. I’ve now fixed this error (though it did not fix my gallery with LiveTV enabled)

I’ve disabled plugins one-by-one to figure out which one specifically was causing it.
I think there’s 2 different addons combining multiple problems for other addons:

Once I fixed the Uncaught TypeError, the cycle remained, and it’s caused by LiveTV Team – 2 – Display Lives. I believe it is loading on all the pages while it should only load on the LiveTV page. So that’s one.

The other issue is probably TubePress. This is also loading on all pages, while it should only load on one of them. I tried renaming the frontend.js file to see if it’d make a difference, only to see it replaced by another error caused by Tubepress. So that’s probably the second problem.

Hoping this’ll help with fixing the problem. I really hope it’s possible to run both the plugins at the same time, heh.

Thanks again,

Hi,

As an update – I’ve changed some things around addon wise. The “[cycle] terminating; too few slides: 0 frontend.js:8” error remains now, but this doesn’t seem to interfere with how the site works. It seems to work fine now.

So – thank you for all the help. Glad everything is working now. Thank you!