Better Restriction for Tag Protected Discussions #14
Conversation
…n to select roles on which settings.
Cleanup index.js for forum with extended functions files to separate extended or override sections.
…r not loading extended Tag. Instead create ProtectedTag instances for usage in tagLabel and tagsLabel
…switch, able to display different view for different User Permission Groups Added ReferrerFinder helper class to find which section is the API is loaded from Added User Policy to simplify the isUnlocked logic. Added tooltipForPermission helper class to produce tooltip for both Post and Discussion List for Protected Tags
…scussion and Posts Added restricted view of Discussion Title and Post Contents for protected tags.
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| - | Generic Password | 33580c6 | js/dist/forum.js | View secret | |
| - | Generic Password | 33580c6 | js/dist/forum.js | View secret | |
| - | Generic Password | 33580c6 | js/dist/forum.js | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Thank you for your contribution! It looks great. I'll go ahead and merge your changes and credit you as the contributor for this extension. P.S: For your next PR, you won't need to push files in the |
|
Please wait, I found a bug |
|
I'll mark the PR as a draft. Once you're finished, you can mark it as ready for review. |
|
I've fixed the issue when using Theme extension that doesn't like null string, this is now ready. I haven't updated the dist with the latest changes. |
…stsUserPage styling
|
PR is ready, tidied most it now. |
|
Thank you! |
Closed #12 #13
New Permissions Settings
Toggle user group for each settings, instead of using a on or off switch.
Provide Access for Sharing Link depending on User Roles
Everyone
Admin Only
User Page Post Page is now protected, you can choose to show the protected
Data API is now restricted for protected Tags
The data is still displaying IDs for objects, but the details are now cleared from view. Please note that API will pretty much strip all data away, unless you are viewing the Discussion Page with the Correct User role for URL Sharing.
