Flarum Help Tags

License Latest Stable Version

A Flarum extension.

Now, your users can create discussions in certain tags, but only certain groups can see/reply to posts in those tags. For instance, if you want to have a tag for private support, users could create posts there and manage their own posts, but could not see posts that other users have made. However, designated groups could see and reply to all posts in the tag.

I recommend using the tag description to explain this functionality to users.

Installation

Use Bazaar or install manually with composer:

composer require askvortsov/flarum-help-tags

Updating

composer update askvortsov/flarum-help-tags

Usage

Give the "start discussions" and "start discussions without approval" permissions in a tag to groups of users who should be able to start discussions, but not see ALL discussions in a tag.

Give the "view discussions" permission in a tag to groups of users who should be able to see ALL discussions in a tag.

If you would like the tag to be visible to non-logged-in users, you can give the "view tag" permission for that tag to everyone. Individual discussions will still not be visible, however.

I highly recommend explaining the nature of help tags in the tag description. This was not included by default because of how many different possible use cases there are.

Links

    This type of restrictions gives ability to any user to see all private discussions (between other users) with Inbox tag (byobu default tag for PM usage)

      Purple-Marble ah OK that's definitely an issue thanks for letting me know! Ill add in a special case to private discussions.

      Although tbh I'm not 100% sure what the use case is for letting people see the inbox tag and all discussions within the inbox tag?

          askvortsov
          I'm just trying to use your extension in special way. When I use byobu default tag for private discussion I want next behavior: restrict users from creating public discussion in this tag "Inbox". It does not work. But at least I helped find the issue in your extension)

            askvortsov Although tbh I'm not 100% sure what the use case is for letting people see the inbox tag and all discussions within the inbox tag?

            That's the standard setup for a Byobu Inbox. In addition to the permissions granted in the admin panel, the participant status for any private discussion must be met as well. If you want to allow anyone to participate in private discussions, that's the normal setting for the admin panel.

            It seems, your extension doesn't properly check for the private state of private discussions, so Byobu and Flarum Help Tags are simply incompatible at the moment. I guess your extension together with Byobu will cause big trouble even without a designated Inbox tag.

                Pollux Yeah the byobu integration is currently completely brokem. I'm going to try to get that fixed since byobu is a very popular extension.

                  24 days later

                  Seriously, can someone explain what this plugin does? I read the original post, but I feel that the function described can be done without this plugin? And I installed this plugin, it feels nothins changes.

                  After the plug-in is installed, "View Tags" is set as globally visible by administrator only. But all tags can still be seen by ordinary users without logging in.

                    Littlegolden Essentially, this decouples the permissions for viewing a discussion from those for starting a discussion. As a result, you can now have tags where members can create a discussion, but only the author and authorized groups can see/reply to that discussion. The 'View Tags' permission was introduced so that tags that are restricted in this way can be shown to people who aren't logged in. It isn't intended to restrict who can see tags, but rather to broaden that.

                      Littlegolden Basically, it's great because it allows for private discussions between the discussion creator + a particular group. Only the discussion creator/author and that particular group can see the discussion. It's great if you have a community for health discussions, for example, where you want the discussions to remain visible just for the creator + an expert in that particular field. Hope that makes sense.

                        UPDATE:

                        This is currently incompatible with Clark's Wordpress Extension (https://discuss.flarum.org/d/22229-premium-wordpress-integration/159), and might cause issues with other extensions. I've figured out the root cause, but unfortunately it's a problem with the tags extension. I will be opening up a pull request there to fix it, but this may delay a solution for a while until that PR is merged.

                        Edit: A PR has been opened at flarum/tags79. Once that is merged, I will push out a new version of this extension that fixes the issue.

                          a month later

                          Hi, would you be willing to enhance this extension so that it can be used to grant/restrict access to certain primary tags and certain user groups, in a permission friendly way as described there ? Or should I seek to code my own.

                            bavard this sounds like material for another (new) extension. I see no reason to merge two very different things (theming and permission management) into a single extension.

                                Hi! I'm a bit confused by what exactly you're requesting. If it's a system where only the first post by a user requires approval, then unfortunately this is not something I see in the future of this extension.

                                  askvortsov Actually the other thread went off topic by my fault. What I'm looking for is a simpler way (admin wise) to have certain groups only access certain categories (main primary tags). It can be used in various ways, for example language specific groups with language specific categories, or hierarchy based membership (level 1 access category A, level 2 access categories A B C, etc).

                                    21 days later

                                    Hey, just wondering if this is compatible with the latest release since there is no proof in this discussion that this will work on the latest BETA of Flarum (0.1.0-beta.13).

                                    It should be compatible. However, the bug identified above still stands: it might not play well with other extensions. Starting beta 14 that won't be a problem though.

                                    5 months later