Phil Ewels

Hi siemslikelynn,

If there is a grey bar on the right hand side of the slider, I can assure you that it is because your image is too small. If you’ve uploaded a large image, it’s probably because you have selected a downsized version in the Feature Image selection. Make sure that the drop down box on the bottom right says “Full Size”, and not “Medium” etc..

The default behaviour of the carousel is exactly the functionality that you request – it fills the available space, shrinks (but doesn’t stretch) the image to that width and shows the entire height. There is no option to cap the maximum width of the carousel within the carousel settings as that is a styling design – the plugin simply provides an easy way to manage images and generate the correct HTML, styling the way that the HTML is laid out and looks is up to you / the theme that you use.

The background-image feature is new in the latest release and is still a fairly experimental option that I included at the request of some users. Having different heights for the different bootstrap responsive breakpoints is a nice idea, I’ll look into writing that into a future release. This won’t be very soon though as my work on this plugin is entirely voluntary, I simply wrote the code for myself and thought that others might appreciate it as well.

If you have a link then I’d be happy to have a look for you to see if I can suggest ways that you can configure the plugin to work for you. Otherwise, it sounds like it’s working as it should.

Cheers,

Phil

Ah ok – if you’re not using the background images mode then the height value doesn’t do anything (apologies, this isn’t very clear – the settings page has been rewritten in the new dev version to help with this). On the default mode the images show as they are – if they’re narrower than the carousel they won’t stretch to fit the width, and the carousel height will change according to the varying heights. In other words, you need to adjust your images to fit the carousel before uploading.

The background-resize mode aims to get around this by using a different technique. The height is set manually and fixed, then the images are stretched / cropped accordingly.

Does this make sense?

Phil

Hi Jason,

Glad you tracked the problem down, good luck with fixing it. Regarding the background images issue, that feature is new and relatively untested at the moment, so if it’s doing weird stuff let me know and I’ll look into it.

Cheers,

Phil

Hmm, how strange. I’m afraid I can’t be any more help on this – the markup that the plugin is generating looks fine, so something else weird must be happening. I’ve never seen this on any other sites with the plugin installed. Maybe ask on stack overflow or somewhere? Would be interested to know what’s causing this behaviour if you figure it out!

Sorry..

Phil

Hi Jason,

When you say image href, do you mean the “Image Link URL” field in the WordPress admin carousel image page? What URL have you put in this field? I’ve just tested it and it’s working fine for me, so if you could provide as much info as possible to help me replicate the problem, that would be great.

For reference, it’s better if you can create a new topic in the future, rather than tagging on to the bottom of a different support request.

Cheers,

Phil

Hi wilchrisalex,

That’s weird, the code looks correct and it should show up if it’s in your header.php. Have you checked the simple stuff – having carousel items added with images, making sure that the header.php file is the one that’s actually in your theme, adding in a `<?php echo “Fubar”; ?> in to make sure it shows up, that kind of stuff?

Phil

Hi runlos,

Usually when you get this error in Chrome devtools it’s because jQuery isn’t present. Can you make sure that it is being loaded properly? Also note that WordPress uses jQuery in noConflict mode with jQuery instead of $, so if you’re doing anything non-standard it could be struggling to find the jQuery namespace. Does that make sense?

Cheers,

Phil

Hi BdN3504,

Thanks for your contribution – much appreciated! When I first released the plugin I relied on the data attributes only, but due to a number of reports of the carousel not animating, I chose to include the javascript. Whilst in theory this shouldn’t be necessary with the data attributes, in practice it seems to help in some cases. The presence of the javascript shouldn’t do any harm, so I’ve left it there ever since.

The output buffer bug has also been reported and I’ve marked it as a bug to be fixed for the next release, though thanks for letting me know.

Your suggestion to include an option to not animate on load by default is a good one though – I’ve marked that up as a future enhancement. I might also pop in the option to remove the javascript for those who would like to avoid that.

Cheers,

Phil