Blog Post Paywall
Can anyone tell me a simple way to paywall blog posts for paid community members?
If I could lock it halfway through the blog post so users can read the start of the article, then they need to join the community membership to be able to read the full article would be even better than locking the whole page.
Should be possible with Fluent products, right?
Shahjahan Jewel, this would just be a nice feature to have if it can be done in one of wpmanageninja's products' plugins.
Thanks for any help.
Hello Adam,
Apart from the teaser feature that only displays the beginning of an article, this is usually handled through membership plugins. They let you protect content based on posts, categories, custom post types (CPTs), and other conditions.
A plugin called Fluent Members is apparently already in the works, so I’m confident this kind of functionality will eventually be available.
That said, I’d also love to hear if there’s any ETA to share 😄. I think also a few more users have already noticed about this new plugin project :)
If you use FluentCRM, there is a Conditional Content block added to the block editor, but it's not very well documented!
Jonathan Gwyer I think conditional block in fluentcrm is good for emails....
https://fluentcrm.com/docs/conditional-sections-in-fluentcrm-email-editor/
Debo Ogunrinde that's a different block - there's "Conditional Content" for the post/page block editor that controls access based on tags or whether or not a user is logged in. There's a second block "Conditional Section" for the email editor.
Jonathan Gwyer My bad!
Debo Ogunrinde no no - like I say - there appears to be no documentation, it's almost like it's a secret feature!
Maybe FluentMembers is going to offer this feature? 😉
https://fchub.co/docs/fchub-memberships get it free (open source), update is coming on friday - testing now. see in action -> https://youtu.be/mNGw7JY4JYE
it's friday and it's ready to download and test
Fluent Members should be the solution :)
I wrote my own that works with FluentForms as the payment engine, and this activates another written plugin for the actual access. It also meant I wrote a withdrawal solution for FluentForms too so it can be done.