WP-CLI commands fail when plugin is enabled
-
In trying to build a development workflow system, I was trying to deactivate the Stop Spammers plugin on specific staging environments using the WP-CLI command “plugin deactivate”. However, even when I have the IP address of the WP-CLI client machine (127.0.0.1) included in the “Allow” list, I still get prompted for a password when trying to deactivate the plugin. Other plugins I try to also deactivate have no problem, and no password is prompted for those. Just Stop Spammers asks for a password upon plugin deactivation commands. Any idea why and how I can configure it to allow itself to be deactivated via WP-CLI commands on staging environments?
The topic ‘WP-CLI commands fail when plugin is enabled’ is closed to new replies.