Move capabilities check behind admin_init
and is_admin
#351
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.
Proposed changes
In the ECommerce constructor capabilities checks are being used. In the data module, if the capabilities transient is absent a request is made to Hiive to update it. This expires after four hours.
From what I read, the capabilities checks here are running on every request, meaning every site is polling Hiive for capabilities every four hours.
This change moves the check behind
admin_init
andis_admin
so the capabilities are only fetched when an admin is accessing/wp-admin
. The actions and filters that were guarded by the capabilities are all related to admin UI changes (most obviously printing HTML).8b9c371
https://jira.newfold.com/browse/PRESS0-1016
Type of Change
Video
Checklist
Further comments