And I have another needs, that user are able to view and post their own topics, even if that topics are in restricted category.
Summary
Introducing a new feature governed by the setting allow_authors_in_locked_categories. This allows authors to interact with their own topics even in locked categories.
What’s New?
New setting: allow_authors_in_locked_categories (default is false).
Controller logic updated to bypass category restrictions for authors if the setting is true.
Automated tests updated to cover this feature.
Why This Feature?
Locked categories are usually restricted to certain user groups. This feature allows topic authors to access their own topics, offering more flexibility to admins.
Backward Compatibility
This feature is off by default, so existing configurations remain unaffected unless the setting is explicitly enabled.
The whole point of this plugin is to give people a sneak peak so they might then try to fulfill requirements to get full access (e.g. by paid membership)
I’m not really sure this requirement fits within the scope and spirit of the plugin? How is this a logical extension?
Yes, that would be my preferred way forward as well, this is typical functionality that will lead to extra support questions, lack of understanding what the plugin does and (in the longer term) extra maintenance work.
OTOH It seems you already built this months ago and since no one even saw it I guess a branch would work as well. But I’m not sure if it’s worth actually maintaining it.
One way or another I would prefer that this will not get merged into main.
A support category which gives the support crew full visibility while only allowing regular users to see their own support requests. We could use this for our premium support, for example.
But it does seem totally wrong to have it as part of this plugin. Perhaps we could roll it into Private Replies or the CWP. Or even its own plugin?
That would be a total misuse of this plugin. This plugin does allow people to see the topic titles and even for search engines to index the entire topic.
My sincerest apologies for the oversight regarding the Feature PR. Despite our decision to not merge this feature, I failed to close the PR, leading to its unintended merge.
I want to clarify that a community member had inquired about this feature, as it was critical for their use of the plugin, which led to the initial development and PR. The community member was informed that this feature would remain in an unsupported branch, and there was no expectation set for its integration due its niche use-case.
. And I can see 2 use-cases: