Hello, I’m here today to suggest a new feature. Well, new to me, anyway—I’m not completely familiar with Discourse, so if it’s not new, please let me know. I’m familiar with the components that encourage people to register on a Discourse site for certain categories or under certain conditions. I wanted to suggest a similar component, but based on a different condition, which is this: a setting would be configured by the administrator, for example, topics less than three days or less than four days old, would not be visible to unregistered users. There would be a message encouraging them to register. What do you think of this, if it doesn’t already exist, of course?
Are these the components you’re referring to here?
Are you already using any of them? If so, can you describe your current usage? If not, can you share why not?
I could imagine this being a new feature for one of those existing components, rather than a new component. Is there a reason why you think this should be a separate component instead?
1 like
I agree here with @mcwumbly : it seems like a better fit for a feature request for the Gated Topics component, which already has most of the needed features in place.
1 like
Yes, exactly, thank you for mentioning the links.
I use both of these components effectively. The first to give greater value to certain categories. The second to encourage people who visit my site frequently enough to sign up, even if they don’t necessarily understand the benefits of doing so.
I would prefer it to be a new component. I don’t see this as an option for the first component since its purpose is to act by category. And my suggestion is not by category, but for all categories based on the creation date of the topics. So it’s a very different basis. As for a possible option for the second component, I don’t think that’s a good idea either. Its purpose is not at all to act according to the creation date of the topics. For this reason, I suggest creating a new component.
1 like
I don’t think it’s wise to mix the two concepts. My idea is for people who have been brought to my site, quite often through social media, to sign up, actively participate in the site, react and comment on articles. People who have been brought to my site this way have been through topics which have been posted most recently on social media. And this has nothing to do with the concept of categories. The barrier based on categories is a content type feature. This is not at all my suggestion, which is based on the freshness of the topics whatever the categories.
1 like
But that’s not the point.
The gated topics component already has all the necessary components (the locked page, the logic,…) to do what you want, it just needs to add a new condition to use “days old” instead of categories.
That’s way easier to do, than having to essentially duplicate the entire component, but switch out the trigger.
2 likes
Yes, I understand from a programmer’s point of view, but from a user’s point of view, I’m afraid the two concepts are different. Would there be two options, a filter by category and a filter by date? Would it be possible to combine them? I’m afraid that this would add complexity to a component that was fairly simple and easy to understand. That’s the nature of my reservations, which are that the concepts are mixed up.
1 like
I really fail to see this as 2 different concepts tbh. To me, this really fits as a new setting for the existing component.
Yes, that’s exactly what I think it could be. Just a dropdown to choose your preferred type of filter.
1 like
That would be fine to me. Provided the two types can be selected and not one or the other.
Why not one or the other? Your OP describes
But are you now saying you’d want both time based and category based working together?
I would like to have both features, the one that already exists and that I use, and the one I am requesting. However, unless it is easier for the programmer, I do not want them to be combined in the same component, as the purpose of the two components is not the same (fearing the user confusion I was talking about). If the decision is made to present these two features in the same component, it should be possible to select both features without one replacing the other.
Ok, so let’s see if I get it:
You’d want to be able to say for example:
in category X I want to hide topics if they are newer than [time] ?
if you’d want them to work in tandem, then that’s even more reason to implement it in the same component. Because how else would two different components know what the other is doing?
I highly recommend closing this out and making your request on the page of the theme component.
Ignore me, I forgot Gated Topics was an official component
1 like
No 
I want to hide all topics newer than this number of days, regardless of category, for users who are not logged in.
2 likes
We should keep this as separate topic no matter the implementation:
I don’t think we even need to be debating the implementation here, unless/until someone is ready to start working on this.
Let’s keep the conversation focused on defining the functional requirements and nail those down first.
1 like
Okay, I see, and you just want to be able to choose both types simultaneously so you can do:
- all topics newer than this number of days, regardless of category
- &
- all topics, regardless of age, in this category
2 likes
Yeah, I guess, fair enough.
2 likes
Exactly that, thanks.
2 likes