A new approach to content restriction in the plugin with the ability to create content restriction "rules". The aim is to make it easier and faster to restrict access to content on a website.
At the moment if you use ForumWP the permissions from the Forum Page do not cascade or get inherited by topics and replies and therefore all the content of the Forum is exposed to the world . It makes the Forum restriction pointless. ForumWP do not reply to posts . I think the problem is with UM.
Emma F
•
Nov 29, 2024
With restricted content rules, I’d love for one of the rules to be restrict content for x days. I’d like to create a model with my website where new content is restricted for 3 days for one group of logged in users and available immediately for other users.
Anthony
•
Oct 23, 2024
This is a very good suggestion, as it will save a lot of code writing!
Vitalii
•
Jul 19, 2024
It’s a very smart move. From a communication perspective, personalization of content matters. Display conditions I expect would be based on:
user role
user logged-in status
any user meta key (for, example, “registration_date”, “participated_in_beta_test”, “subscribed_to_our_maling_list”, “last_login_at”, etc).
Also, I expect an option to combine these conditions with “AND”, “OR” operators.
Log in to comment and vote
Comments6
Gregoire Martin
Mar 17, 2025
Jason Richards
Mar 6, 2025
At the moment if you use ForumWP the permissions from the Forum Page do not cascade or get inherited by topics and replies and therefore all the content of the Forum is exposed to the world . It makes the Forum restriction pointless. ForumWP do not reply to posts . I think the problem is with UM.
Emma F
Nov 29, 2024
With restricted content rules, I’d love for one of the rules to be restrict content for x days. I’d like to create a model with my website where new content is restricted for 3 days for one group of logged in users and available immediately for other users.
Anthony
Oct 23, 2024
This is a very good suggestion, as it will save a lot of code writing!
Vitalii
Jul 19, 2024
It’s a very smart move. From a communication perspective, personalization of content matters.
Display conditions I expect would be based on:
user role
user logged-in status
any user meta key (for, example, “registration_date”, “participated_in_beta_test”, “subscribed_to_our_maling_list”, “last_login_at”, etc).
Also, I expect an option to combine these conditions with “AND”, “OR” operators.