Gated Topics in Category

Fine, I installed Lilly’s component and after having to change this setting it worked fine !

2 Likes

I’m glad that worked as a solution for you. However, that is not one of my components - it is the fine work of @Don :chefs_kiss: :clap:

3 Likes

hello,

can the font size be adjusted in the display screen? if the message is long then not all of it shows on a mobile device.

Thanks

2 Likes

can’t we redirect users to the original topic url, after logging/registering?

3 Likes

Great component :+1: and a very good start.

Some granularity would be useful, along the lines with options such as

  • Allow full first post read, then *
  • Allow X first post read,then *
  • Allow X number of lines of content be read, then *

*show gated message

Perhaps some options to control the size and maybe even basic style of gate, like Height, maybe even width.

5 Likes

I am interested in same features! I am currently setting up a course on my WP instance which offers locking content for paid users via Wishlist member plugin.

Ideally I would like to use some kind of [gated group=premium] shortcode to wrap the content to restrict it to only to specific group members.

2 Likes

Great idea, disabling scripts in browser completely breaks it though.

Unforunately, that is as good as it is going to get with a front-end component like this (I think).

Anything more robust will take a formal plugin.

4 Likes

This seems like it could be quite a powerful plugin for those who really on any kind of subscriptions or payments. For now categories are either completely visible or completely invisible on a group basis, but it would certainly be nice to have something in the middle to give that sense of “FOMO” and encourage subscribing.

I would definitely recommend turning this into a feature request.

4 Likes

Hi: It works really well. I wonder if anyone has put an image behind it? so that it looks a bit more on brand? Bronwyn

Reading above, “disabling scripts in browser breaks it though” - I presume that means someone gets free access that point? Could you let me know as that would be a problem.

Have you tried adding something via css?

Not sure what you mean about free access, but it means they can view the content on the page. YMMV if that’s a problem or not. Personally, we use this in our announcement categories to require a login, partially so that we can demonstrate that customers have viewed news topics (for liability purposes).

1 Like

If you disable javascript in your browser, you can see the content of a topic.

I then assume LLM-AI scrapers can do the same and access the content and something a site admin/owner may not want.

Is there anyway to stop bots coming in with javascript off and scarp-sucking the content of a discourse site while the real users suffer this disadvantage?

IIRC such verified bots like google are served the non-javascript pages from discussion around page views and Adsense (page counts in a world of infinite scroll)

Maybe the way to handle this is via CF instead?

I’ve been using this for a while and it’s great. I just wonder whether it uses the isAccessibleForFree technique mentioned at Subscription and Paywalled Content Markup | Google Search Central  |  Documentation  |  Google for Developers. Or does it let search engines access the content in some other way?

I don’t know if it’s just on my end, but on the desktop, the profile picture appears, well, empty, while the actual photo is right below it, creating the impression of a bug.

1 Like
topic-avatar,
    .topic-post.sticky-avatar>article>row>topic-avatar {
      position: relative !important;
      top: auto !important;
    }
  }

  .post-stream {
    max-height: 150vh;
    overflow: hidden;

When the top gave way to sticky for some reason, the avatar was in the wrong place. Well, it’s a workaround, and I hope the original maintainer checks if it’s something specific or indeed a general visual bug.

1 Like

Thanks for reporting this! I’ve just merged an update that modernizes the component’s template and included a fix for the avatar position:

2 Likes

Another question: I swear that this component used to hide the HTML content when JavaScript was disabled. Was that the usual behavior, or was it specific to my browser?

By the way, thanks for fixing it :heart_eyes: