Blueprints: set_current_user to admin before activating plugins and themes #984
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
…hemes Sets the current user to admin before activating plugins and themes. ## Rationale Issue #911 uncovered a problem where activating a plugin does not create a page in the following scenario: ```php function myplugin_activate() { if( current_user_can( 'activate_plugins' ) ) { create_page(); } } register_activation_hook( __FILE__, 'myplugin_activate' ); ``` The root cause is that the activatePlugin and activateTheme steps do not set the current user to admin before activating the plugin/theme. ## Testing instructions This PR comes with unit tests – confirm the CI checks pass.
adamziel
added
[Type] Bug
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.
Sets the current user to admin before activating plugins and themes.
Rationale
Issue #911 uncovered a problem where activating a plugin does not create a page in the following scenario:
The root cause is that the activatePlugin and activateTheme steps do not set the current user to admin before activating the plugin/theme.
Testing instructions
This PR comes with unit tests – confirm the CI checks pass.
Closes #911