brunall reported a bug where a tag (#private_tag) belonging to a tag group was not visible in the “All tags” list—even for users in permitted groups—and prevented those users from creating new posts when filtering by the tag and a category, displaying a misleading “no permission to post in the category” error. Moin clarified that the error message incorrectly attributes the block to the category, even when the tag is the actual cause, referencing a known issue here. brunall later noted that the issue resolved after switching to category-based group restrictions, and confirmed there were 7 topics tagged with #private_tag at the time of reporting. The issue appears to stem from tag visibility and permission handling in tag groups, and while not fully resolved in all configurations, the workaround of grouping by categories mitigates it. The bug is tagged as “fixed” and “tag-groups”.
We have a tag in our forum that belongs to a tag group lets call it #private_tag. We have a restriction there that “Tags are visible to everyone, but only the following groups can use them”.
However, the tag is not visible for users in the “All tags” lists. Not even for those included in the groups that can use the tag. Additionally, when users included in those groups have applied a filter for any category and that #private_tag, they cannot create new post.
In the information they see the message that they don’t have permission to post in the category, even though they do.
So, is this by design or something that should be fixed?
