Hi Mike,
It looks like those images are cropped. Make sure that you don’t have the crop checkbox checked when using the Auto-width feature. They don’t play well together 😉
I do see the extra pagination dots. I’d make sure you turn off the cropping, then clear your cache, and resave the gallery again.
Also, it doesn’t look as if the autoWidth setting is being output onto the page for that carousel instance. I really think there’s a caching/saving issue here overall. Keep me updated on progress there and let me know if you find anything fishy.
Hi Matt:
Indeed, unchecking the crop thumbnail to exact dimensions box did allow the portrait images to display. The pagination dot issue remains, however, and galleries with auto-width load slowly.
I’m checking into the caching issue. My CDN is set to development mode, and I haven’t set up any other caching for this page. I’ll load it a few times on another machine, while not logged into WP and see if that makes a difference.
Another oddity I notice for that top carousel with the auto-width is that the settings for the “Responsive break points” is set, but they are all set at “5”, which defeats the purpose. Can you try disabling the responsive break points feature for that carousel?
Tried a few more loads. Interestingly, it still stacks the pictures on page load using iDevices.
I did note that despite the pagination dot issue, the responsive touchscreen swipe still moves the gallery by one stage rather than one thumbnail. Each swipe moves 5 thumbnails, and the darkened, active pagination dot moves 5 dots.
I’ve had some limited success playing with the margin setting so that auto-width won’t cut off thumbnails halfway. This might need some extra code to automagically adjust the margin so that the stage is justified with only complete thumbnails showing, even when thumbnails are various widths.
I’ll take a shot at it when I have some time.
Mike,
The auto-width feature can’t ensure that parts of an image are cut-off. That’s a necessary by-product of the auto-width feature. Otherwise, it would unnaturally stretch some images depending on different number of images and stages.
You can see on the auto-width example here, specifically between tiles 7,8, and 9, that the original Owl JS does that as well:
http://www.owlcarousel.owlgraphic.com/demos/autowidth.html
So, that is not a bug. It’s just the way it is.
Regarding the pagination, did you disable the Responsive feature? Also, how many items do you have set there? If possible, can you take a screenshot of the settings of that gallery and post a link to it?
Hi Matt;
No, it’s not really a bug. But it could be better, and it does seem to be already stretching the images – my thumbnails are set for 120×100, but with auto-width enabled it seems to create a cached, resized picture and use that instead, resulting in a blurry thumbnail and long load times. Without auto-width enabled it really quickly picks up the pre-sized thumbnails and loads like lightning, at the price of forcing every picture to the same size. Sigh.
I did see the demo. Yep, I’m a fussy, anal-retentive triathlete – half a picture is going to drive me batty.
I’d suggest some code that dynamically sizes the margin as opposed to stretching the images. To elegantly do it, I see having to animate margin widths, since auto-advance set to 1 would mess with pre-set stages.
As for the responsive, I meant that the responsive bit works – whatever’s messing with the pagination dots isn’t affecting the proper functioning of the responsive swipe. It’s just a clue as to what’s going on – since one swipe = 5 dots, (the width my stage is set to).
I did try the advanced setting for number of thumbnails per stage on different screen widths, without luck. As expected, the auto-width setting seems to override this, since it shouldn’t be needed.
For now, I’ll set it all back to fixed width, which works nicely, and see if I can hack a fix for the half a picture. If I have any luck I’ll send you the code.
Since this isn’t technically a bug, but a feature request, I’ll close this ticket. I’ll keep the thread updated with progress on feature updates and whatnot.
Thanks!
