kwiliarty

Hello again. I’m sorry to say that the plugin does not have any support for autostart at this time. I’ll look into adding it, but I can’t say when, and it might be a while.

Excellent. Thanks for letting me know.

Adding this CSS might do the trick:

video.external-vfe, div.external-vfe {
	max-width: 100%;
	height: auto;
}

Let me know if that works for you because I might want to add it to the plugin.

It’s here:

https://www.ads-software.com/support/topic/plugin-wp-mail-smtp-useless-for-multisite-network-admins?replies=6

And the short answer is that in the main plugin file there is list of constants (commented out) that you can set in wp-config.php. If the constants are set, then admin pages will not be available for individual sites. It was a great help to me.

The solution shown on this thread other works:
https://www.ads-software.com/support/topic/plugin-google-analytics-for-wordpress-problem-and-solution-with-multisite-network-enabled-site?replies=4

The weird thing is that the readme file in the plugin lists this as an issue that has been fixed, but the problem is still in the code. Maybe it’s a regression?

We had a similar problem: Bookings for every instance of a recurring event closed at the start of the first instance. Here is how we fixed it:

• Update the plugin
• Go to individual upcoming events
• DETACH the individual event so that you do not lose existing bookings (as you would if you editing the recurring event).
• Edit the Bookings cut-off date (in Bookings/Registration)

We love the plugin. Hope this helps someone else.

Do you mean that it takes too long before the video starts to play? Or that playback gets interrupted in order to allow loading? Do you know whether you using the optional VideoJS player? Do you know whether you are looking at an .mp4, an .ogv, or a .webm? (It will depend to some extent on your browser.) Does the problem occur with one file type more than others? Most importantly, do you find that you can view the same file with fewer problems by some other means?

Sorry to have more questions than answers at this point.

Well, thank you for looking at it, Gabriel. It’s helpful to know the results of your test. We thought we understood the problem, but it must be yet something else on our end. We know that changing $wpbd->prefix to $wpdb->base_prefix solves our problem, but if you can’t recreate it, it’s probably due to some even more idiosyncratic aspect of our set-up. We’ll have to figure that out.

Best,
Kevin

Hi Gabriel,

We would not use a null prefix again, and maybe we should find a way to move away from it on the site in question. It has given us a lot of trouble with plugins that work fine on most installs. The issue is almost always $wpdb->prefix versus $wpdb->base_prefix.

We can continue to patch on our own, but I thought it wouldn’t hurt to ask, and it might be of help to a few others in the same situation who might not even know why it doesn’t work. We like the plugin.

Cheers,
Kevin

Hi Gabriel,

We have some installations where it works. The one that does not work has a null prefix. That causes problems with a number of plugins, but the fix is usually the same. It’s probably a small number, but there may be others with the same problem.

Best,
Kevin

You have to edit the file in the plugin folder. The path to the file withing the plugin folder is:

/flightbox/jquery.flightbox.js

The very beginning of the script that works for me (starting right after the commented head-matter) looks like this:

jQuery(document).ready(function($) {
;(function($){
    $.flightboxIsVideo = false;

where the very first line is the one that I added. The very bottom of my file looks like this:

}
})(jQuery);
});

where the very last line is the one that I added. Other solutions maybe be possible or better. At least for me, this does the trick.

Hi timmmmyboy,

I was in fact talking about the jquery.lightbox.js. I wrapped the JavaScript in that file with these lines:

jQuery(document).ready(function($) {
...
});

That change worked for me.

I wonder if we are somehow looking at different versions of the code. (I have 1.5.2). I find the code you mention in flickr-gallery.php around line 1074. I don’t have a line 1431. If I unmake my own change and apply the change you describe the lightbox stops working for me.

I just posted a likely explanation and solution at on a related thread. You can read it at:

https://www.ads-software.com/support/topic/plugin-flickr-gallery-jquery-error?replies=2#post-2507225

I just posted a likely explanation and solution at on a related thread. You can read it at:

https://www.ads-software.com/support/topic/plugin-flickr-gallery-jquery-error?replies=2#post-2507225

I was having the same problem. I believe that the answer and the solution are to be found here:

https://codex.www.ads-software.com/Function_Reference/wp_enqueue_script#jQuery_noConflict_wrappers

Looking at the code in the plugin file jquery.lightbox.js it seems that it is not using ‘no-conflict’ mode. I wrapped the JavaScript as described at the link above. Now the error is gone and the lightbox works.