Feature: Hide all messages from a certain capcode #630
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hmm, just thought that it might be worth to re-do it, and instead introduce a Dropdown field 'visible to' with options 'Everyone', 'Logged-In Users', 'Admins', 'Nobody' - Think this would be more straightforward for users. We could try to integrate the PDW mode into that, I think a lot of users (including me) don't know what that means and why it's called that way without googling it. |
|
Oh, even better: User Groups, with the mentioned levels being default groups that cannot be changed. This would enable to give different rights to different users. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Sometimes you want to store and process messages, but don't show them in the gui. This feature enables you to hide messages belonging to a certain capcode from everyone, including logged-in users and admins. They will however still be stored in the db and sent to all plugins.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: