CMS Display Limit "Start From" Option Not Appearing

Hello all!

This should hopefully be an easy one to answer: I have a slider connected to a collection. It has everything in there fine, and I can limit each slide to display only 1 item fine. I don’t see the option for “start from” that people use to tell each slide which item to actually show instead of just the first.

I’m presently on a free account while I get things set up. Is that why?

Thank you all in advance!

You’ll find it in the right-side settings tab when you have the collection list element selected. Make sure to select it in the left-side navigator so that you know you’re selecting the collection list itself and not its contents.

Hi there! Thanks for the reply.

I’ve selected each different element in the list. I don’t have the option at all. I can limit to a single item, but not select which item.

The start from option you’re asking about is right next to the limit option.

There is no option to select a specific item, though you could probably filter to slug = (item slug you want).

To be clear though you would not normally build a slider with collection lists inside of it, that’s “expensive” in that you have only 20 collection lists per page total. Instead you’d use Finsweet’s CMS Slider toolkit, or setup a custom slider using a library like swiperjs.

So the start from option literally does not appear. I know exactly where it should be. It is not there. That’s the issue I’m trying to find out more about.

I’ll look into the toolkit you mentioned. I’m brand new and don’t know what that is or how it works, but I will go figure it out.

Readonly designer link?

Hi Michael!

I’m actively playing with the site - that’s not the correct project link.
The issue I’ve discovered is that using a multi-image field in the CMS won’t allow that option; it has to be items in a separate CMS. That doesn’t work for me as I’m setting this page up for a CMS that has other content, and then want a gallery of images to show.

So, sadly, this image has no bearing on what I’m doing.

BUT! I did figure out a workaround, which is just adding images instead of a multi-image. It’s more annoying in some ways, but it’ll get things done.

Thank you for sticking around and trying to offer advice, even if it wasn’t quite what I needed.

:laughing: Ah it’s difficult to help you without an actual project link.
But you can see where Start at is now.

If you’re playing with nested collection lists, they follow different rules.

I’ve run into this issue a couple of times. It essentially renders the multi-image field useless for sliders, which would be the ideal use case in my mind. The group of single images method is the best workaround but you can’t have sliders with n number of elements in a content-type.

Hi @staypuftman , yes these limitations are a pain, but I think I have some ideas for you that might help-

I think what you’re doing is emitting one image at a time using a collection list per-slide? I avoid that because it would use up 5 to 10 collection lists, and lock me into a fixed N slides that the client couldn’t change easily.

I generally prefer to use Swiper.js for any CMS-driven sliders, which eliminates this problem- I just emit one collection list and turn it into a slider.

However I think you might be able to use the Webflow Slider with a CMS multi-image field in 2 ways-

  1. If you’re on the collection page itself, then you don’t need to nest your CLs and you should have the “start from” option for your multi-image-field-bound list.
  2. Finsweet’s CMS Slider should work here also.

Yeah, I tried the Finsweet Slider. It’s ok. The granularity on the settings for slider displays is very poor and it makes me think all the really slick Webflow sites I’m seeing are just custom coded slider elements placed into a Webflow site.

The advantage of Webflow is that I’m not supposed to have to think about the code layer. And I’m a programmer, so if I wanted to build a custom site I’d just go do that. This is the worst of both worlds as is.

100%. Webflow components are designed to be nocode which by definition means simplistic and with minimal configuration / customization options. That goes for navs, sliders, richtext, tabs, forms, video elements, even buttons. None of these have client-side APIs to extend them. From my perspective as a dev, nocode land in general is a lego set where it’s easy to build simple things, but you’re locked in to a limited set of pre-designed shapes.

All of the cool things you see like Timothy Ricks work uses external libraries like swiperjs or splide instead of Webflow’s Slider, and often GSAP instead of Webflow interactions. The Webflow designer itself is Webflow’s strength, everything else is legos, including the CMS, Ecommerce, User Accounts, and Logic. They’re designed to provide basic functionality but it’s very limited and they have very thick walls that make them difficult to extend.

It’s frustrating, but in my experience the problem is more about the expectations around no-code. Webflow’s efforts towards apps is a huge step in the right direction that I hope will ultimately allow devs to build drop-in components that cover every conceivable need.

But there are always tradeoffs. Opening the system means complexity, bugs, incompatibilities and updates, and before long you’re struggling with many of the same issues Wordpress has.

Hi! I’m having the same problem.

I’m in a CMS Collection Template Page and I added a Slider component. To the first Slide I added a CMS collection that has a Multi-Image Field but I can’t set “Start at”, it doesn’t appear (see attached image).

How did you set up this page so you could see the “Start at” option?



That’s a bit surprising, I’d only seen nested-list restrictions on list settings before, there appear to be field-type restrictions as well.

It looks like you can’t. If you’re trying to build a CMS-powered slider, I’d recommend using Finsweet’s CMS Slider lib, or replace the entire slider with Swiper JS.

Thanks for the reply!
Sadly I can’t use custom code since I’m on the free plan. I’m just learning at the moment.

I think I managed to get the result I want with a workaround.

I’ll consider using your recommendations in the future.