virtualpudding

I’ve also been having problems with this.

I ended up using this for now (which works) but i’m looking into alt method.

global $wp_query;
$cat = $wp_query->get_queried_object();
$thumbnail_id = get_woocommerce_term_meta( $cat->term_id, 'thumbnail_id', true );
$image = wp_get_attachment_url( $thumbnail_id );
echo '<img src="' . $image . '" width="200px" height="200px" />';

hmmm..strange.
have a site i can take a look at?

This was a restriction of the jQuery slider iteself (by Zurb), not the plugin.

Hey,
Currently, you have to do it the following way
https://www.ads-software.com/extend/plugins/wp-orbit-slider/faq/

Read the section “What about the slider size?”
It invloves defining you dimensions in your own theme functions.php file.

Hope this helps

Hey Gary, yes, one per page is the current limitation i’m afraid.

Thanks for the kind words.
We’ve all been there (8am and loaded!) Happy to hear you got a fix.
I’ll review the settings in the next update.

As the slides are custom-post-types they are currently controlled in DATE ADDED order.
So just change your ‘published’ dates to reorganise.
Hope this helps

@glovep

The CSS example I show above was pasted directly at the bottom of my main style.css (none of the plugin css files).

It would really help if I could take a look.
You can email access details to dev (at) virtualpudding (dot) com

As far as i’m aware, the autoplay and timer run hand-in-hand. Disabling the timer disables the autoplay.

I’ll be honest, the cpu isn’t really highlighted in the zurb documentation and it wasn’t something I was alerted to within the development of the plugin.

Its not great, i agree.
I’m sure this will be addressed in future development of the jQuery code.
In the case it is not, I would personally look into an alternative jQuery method for the plugin. New sliders are created everyday. The plugin would continue to operate and no-one loses their slides they have already implemented. It would just be a case that the orbit slider, does no longer include the zurb orbit code.

Sorry i can’t be of any further help on this.

@protohominid
Isn’t that what the example above is doing?
Then in the css for your responisve theme (that will have media queries within the css) adjust the max-height accordingly to fit.

The savage approach would to display:none for the whole slider and show the slider only when the window (all images) are loaded.
This could be hacked into the plugin code or a seperate jQuery trigger. That would offer no fallback for non-js users.

Essentially, if you really (and feel capable) of getting your hands dirty with the jQuery code itself, I would bypass the plugin option altogether.

Essentially, its the orbit slider jQuery and markup combined with a WordPress custom post type. There are tonnes of tuts for this.

Hey both,
If you are referencing the plugin faqs from the Zurb site, please remember, Virtual Pudding are responsible for the WordPress plugin version and not Zurb.

They have a ‘achieving perfection’ tab
https://www.zurb.com/playground/orbit-jquery-image-slider

This documentation was based on their original slider (that wasn’t responsive) so it was a lot easier to keep things fixed using width/height.

In the WordPress plugin, a little more markups was introduced that would enable the using to use css to style specific individual sliders set to a category.

So, where they refer #featured, you’ll need to be using .orbit-wrapper

Try this…

.orbit-wrapper { max-height:250px; overflow:hidden; background:#fff url('ajax-loader.gif') no-repeat center center; }
.orbit-wrapper img { display:none; }

Just tried it out and seems to create the desired result
https://www.virtualpudding.co.uk/dev/playground/wp-orbit-slider/

This all taken into account, setting fixed width/height dimensions will become problematic regarding ‘responsive’. This can be corrected using media queries.

In a nutshell, this slider will only act responively if the theme itself is responsive.
I’m guessing many will have installed this plugin and are not using a responsive theme so the above will be a good fix.

Hope this helps, report back so i can help further.

Hey protohominid,

The CPU usage is a restriction of the jQuery itself and nothing to do with the WordPress plugin code itself.
I’m restricted to the jQuery coding they provide. I have seen some issue tickets regarding this and i’m sure its something they (Zurb) will address in future updates.
As and when they do, they will be updated to the plugin by us (Virtual Pudding).

Hey colourPress,
Just to clarify…. this plugin is by Virtual Pudding. We are using Zurbss Orbit Slider jQuery code.
Although they are no longer supporting the standalone version, they continue to include the slider code inside the framework they support ‘foundation’.

When this plugin was created (by Virual Pudding) we were already using the code from ‘foundation’ and not the standalone.

So in theory, nothing has changed.
Does this help clarify?

hey colourPress,
Thats not a problem in regards to the plugin. The jQuery code currently being used is taken from the Foundation framework already and not the older version 1.2.
Should all be ok for the future.
I’ll keep you updated

Hope this helps

Hey, glad to hear you got your slider working!

As for, slider thumbnails.
If you are refering to the using thumbnails instead of bullets, unfortunately this plugin will not do that at this stage.

You could poke around with the plugin code but will lose all changes in new versions.

If you are looking to really customise the orbit slider a lot, I totally suggest just hardcoding it and bypass using the plugin at all.
Especially useful if you are, say, only planning a nice large slider on your home page.
The original (non-Wordpress) project by Zurb is at https://www.zurb.com/playground/orbit-jquery-image-slider

If you follow their instructions, its not difficult to get a very custom slider up and running.

Hope this helps