Settings pages are only for admins and when allowAdminChanges is true
#1581
Conversation
This file contains 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
angrybrad
deleted the
bugfix/settings-only-for-admins-and-with-allowAdminChanges
branch
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
The settings page should only be available to admins and only when
allowAdminChangesistrue.The “Clear pending job queue” button, which was located on the Settings -> General page, was never restricted to just being available to admins, so I moved it to a new “Utilities” tab. This way, you’ll still be able to access it and trigger the action as you were before, even if you’re not an admin or the
allowAdminChangesis off.Note: if the plugin is not set up to show all the tabs, you might need/want to select the new “Utilities” tab and deploy the project config changes.
Related issues
n/a