-
Notifications
You must be signed in to change notification settings - Fork 801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protect: Improve Network Activated Jetpack check #13267
Protect: Improve Network Activated Jetpack check #13267
Conversation
Previously, Jetpack Protect would complain that the plugin was not network activated even if the plugin *was* network activated but installed in a non-standard directory. Use `plugin_basename()` to always look in the right place.
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: September 3, 2019. |
Related to (and will need rebase against) #13266. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice improvement!
* 7.7 changelog: initial set of changes * Changelog: add #13154 * Changelog: add #13134 * Changelog: add #12699 and many others * Changelog: add #13127 * Changelog: add #13167 * Changelog: add #13225 * Changelog: add #13179 * Changelog: add #13173 * Changelog: add #13232 * Changelog: add #13137 * Changelog: add #13172 * Changelog: add #13182 * Changelog: add #13200 * Changelog: add #13244 * Changelog: add #13267 * Changelog: add #13204 * changelog: add #13205 * Changelog: add #13183 * Changelog: add #13278 * Changelog: add #13162 * Changelog: add #13268 * Changelog: add #13286 * Changelog: add #13273 * Changelog: add #12474 * Changelog: add #13085 * Changelog: add #13266 * Changelog: add #13306 * Changelog: add #13311 * Changelog: add #13302 * Changelog: add #13196 * Changelog: add #12733 * Changelog: add #13261 * Changelog: add #13322 * Changelog: add #13333 * Changelog: add #13335
Previously, Jetpack Protect would complain that the plugin was not network activated even if the plugin was network activated but installed in a non-standard directory.
Changes proposed in this Pull Request:
plugin_basename()
to always look in the right place.Is this a new feature or does it add/remove features to an existing part of Jetpack?
No: bug fix.
Testing instructions:
Prior to this PR: See the warning about Network Activation.
After this PR: See no warning.
Proposed changelog entry for your changes: