Steven Gliebe

Hi Kevin,

I appreciate your work on this plugin. Is there any chance you’ll make it work again with PHP 5.2? Many servers still run that version and WordPress itself supports it. That would make things smoother for a lot of users.

Hello,

I’m the author of the Risen theme. I took a look at Captain Slider and it looks like what is happening is that both the plugin and theme are enqueuing different versions of Flexslider simultaneously. Risen uses the handle “jquery-flexslider” while Captain Slider uses “flexslider”. The plugin loads Flexslider on every page which means it is being loaded on the homepage when not necessarily needed.

The easiest thing to do is use a different plugin that either does not use Flexslider or does not load Flexslider on pages where it is not needed. Otherwise, you can deregister Captain Plugin’s Flexslider on Risen’s homepage.

https://codex.www.ads-software.com/Function_Reference/wp_deregister_script
https://plugins.trac.www.ads-software.com/browser/captain-slider/trunk/captain-slider.php#L50

You may also want to contact the plugin author to see if they have any advice.

I’ll third that. Any support planned with CL 2.0 for this: https://core.trac.www.ads-software.com/changeset/22346?

I’m also using a self-signed SSL certificate and forcing SSL on admin. I’m not sure if that would cause an issue (wasn’t using SSL when first reported this on the older version of the plugin).

Maybe it’s also helpful to note that the server uses PHP 5.3.

Thank you for looking at this.

I tried now and on first submit nothing seems to happen. When I clic again it says “No file was uploaded”. No PHP or JS warnings.

IE 9
WP 3.5.1
Plugin 1.1
Multisite (fresh install of a site, using Twenty Twelve)

I will be happy to help you troubleshoot if the problem remains after the plugin is updated to properly enqueue WordPress’s jQuery library.

Hello,

I’m the author of the Risen theme. The theme does not hard code jQuery. It uses the version of jQuery bundled with WordPress in no conflict mode. The script is properly enqueued.

What I am seeing in the HTML5 jQuery Audio Player plugin in index.php at line 146 is that a version of jQuery bundled with the plugin is used instead of the version included with WordPress and that it is not properly enqueued but rather it is hard coded.

<script type="text/javascript" src="<?php echo $pluginurl ; ?>player/js/jquery-1.7.2.min.js"></script>

This can cause the JavaScript errors that are being seen. I assume this is a remnant left over from an old version of the plugin since this is inconsistent with what is correctly stated in the plugin’s FAQ.