A client needs to restrict access to media in posts for specific user groups, with the option to limit by category and views. kinetiksoft explains that category access control is not sufficient, as the content is shared between public discussions and needs to remain public.
itsbhanusharma suggests that this concept sounds like a “pay per view” type of system, where users are allowed a limited number of views before needing to pay to access the media. kinetiksoft agrees with this idea.
A key requirement is that the solution must be secure and not bypassable with CSS or client-side approaches. pfaffman notes that CSS will allow clever users to bypass protection, which is not acceptable.
Pavilion has expressed interest in working on a plugin for this feature and invites kinetiksoft to discuss options.
Our client needs their posts media to be pay-walled for specific groups of users. There are a lot of media in the posts made by forum users, but we need these media to become unavailable after certain time/views or unavailable overall for specific group of users. Unavailability of the media can be represented by placeholder asking user to proceed to checkout to subscribe to the service in order to view everything. Subscription status in the service is being synced with forum and that’s how we define which groups should access the media, and which groups should not.
It would be great if this could be limited to specific Categories in the forum.
This should certainly not be a CSS Hack or something like that.
When do you need it done?
Can be discussed. No rush.
What is your budget, in $ USD that you can offer for this task?
Category access is already controlled by group membership. Why doesn’t that work?
Oh. And you don’t want the topics to be protected, but the media/images on those posts. CSS will allow clever users to bypass the protection ;is that ok?
Because the content is being shared between public discussions and we want them to remain public. Limiting non-subscribers from the category will give no understanding for them of the volume of content available there.
That’s why we need a solution which won’t be bypassed on client side with CSS or using similar approaches.