Conditional visibility for blog posts

Design help General
1

Hey gang! Has anybody found a way of using conditional visibility for blog posts? Using one CMS list, some posts are only visible when the user is logged in, the rest stay visible whether the user is logged in or not?

2

Hey Max, thatā€™s that conditional visibility is for.
Just apply it to the elements you want to show or hide based on login state.

3

Hey Michael! Thank you for replying. The example I am thinking of is within one CMS list, I want some items from the list to be visible for member only. Is that possible?

4

Ah thanks Max, I misread your post.

There is only one set of ā€œelementsā€ within a collection list, so they all have the same settings. For element-level CV, you are gating all of the elements in the Collection List the same way.

What youā€™re looking for is Collection Item-level gating, which would be configured in the CMS manager, per-item. It is not yet a feature of Memberships.

5

Thanks Michael! Hopefully theyā€™ll put it in soon, seems basic to be able to mix ā€˜freeā€™ and ā€˜paidā€™ articles.

6

Agree. You can sort of achieve that with script now;

  • Two collections, one for free, one for paid.
  • Gate the collection pages accordingly, to free & paid access groups

Home page, or catalog page;

  • Create two collection lists, one bound to each
  • Use script to stitch and sort them together.

That will achieve a mixed free-paid view, and actual free-paid content gating as well.

7

What are you using to log users in & out? Memberstack, Webflow Memberships, something else?

8

Thanks Michael. I did indeed go down this road, using the Finsweet combine script. Although managing two separate collections has already gotten a little frustrating. Hopefully theyā€™ll add this feature to Webflow natively soon.

1 Like
9

Hi Chris! Iā€™m using Webflow Membershipsā€¦ and using a bit of what I learned following your lessons too. Thanks!

1 Like
10

How important is content security to you on these paid articles?
I have a script technique I use for CMS-item-level gating by access group, but if someone were determined enough they could get around the scripts and access your articles.

11

Based on what youā€™ve said, I usually opt for simplicity. This isnā€™t exactly your ask, but itā€™s food for thought none the less :smile:

  • Create 2 pages, one thatā€™s public, one that is not.

  • On the public page add a CMS Collection list.

  • Set the filter on the Collection list to ā€œpublic=trueā€.

  • For all Collection items that you want publicly visible, tag them in the CMS as such.

  • On the gated page, add a second CMS Collection list.

  • Either set the filter to ā€œpublic=falseā€ or nothing, just displaying all articles.

It sounds like you were wanting this all on the same page, using only 1 CMS list, but I donā€™t think you can set that for individual CMS Collection List items, unfortunately.

At some point Iā€™d assume Webflow Memberships will have this ability and you could swap this out for that when they do.

Hope that helps!

12

Chris, Michael ā€“ thank you for the responses. All really helpful and interesting, you guys are great. I think for this one I am going to wait it out and hope Webflow add this and a basic function soon enough!

1 Like
13

I added this to the Wishlist https://wishlist.webflow.com/ideas/WEBFLOW-I-5797