You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f960e5b
Browse filesBrowse the repository at this point in the historyBrowse files
My Jetpack: Have the Protect card read the Protect page's module (#53727)
* My Jetpack: Have the Protect card read the Protect page's module
The protect module is Brute force protection, so switching it off marked
all of Protect inactive. Where the Jetpack plugin offers the
protect-dashboard module, Protect now reads that one instead.
* My Jetpack: Keep Protect on its module with the standalone plugin
Activating the Protect page module would take over the standalone
plugin's dashboard. Also cover deactivation with the page module on
offer, and read the module through get_module_name() everywhere.
* My Jetpack: Turn on the Protect page instead of installing the plugin
With the Jetpack plugin offering the Protect page, activating Protect
installed the standalone plugin and then switched on the protect module.
Skip that install there, and resolve the module before deactivating the
standalone plugin so deactivation acts on the module the user saw.
* My Jetpack: Don't reactivate the standalone Protect plugin either
Where the Jetpack plugin offers the Protect page, activating Protect
turned an installed but inactive Jetpack Protect plugin back on. The hook
now covers activation as well as installation.
* My Jetpack: Rename the Protect standalone plugin test provider
* My Jetpack: Check for the Protect page in one place
Main_Features repeated Protect's protect-dashboard availability check,
so the Features tab and the Protect card could drift apart. It now calls
Protect::is_dashboard_module_available() and uses its module constant.
0 commit comments