Use different action for admin context logic #5663
Merged
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.
The
-context=admin
logic was hooking some of its logic to theadmin_init
action. However, as the loading was adapted, the requirement for triggering theadmin_init
action ended up within the action's closures, causing the entire construct to not be executed at all.This PR changes the
--context=admin
logic to useinit
instead ofadmin_init
, and adds custom (hacky) logic to load the admin environment accordingly.This hacky approach for loading the admin environment is used to ensure we stick with the behavior of whatever WordPress version is being used. Inlining the code would make this hard to accomplish.