I and other plugin others mistakenly thought that "disable" merely shuts down the plugin temporarily (e.g. housekeeping such as cancelling the scheduler task) but it also sets the global opt-out configuration to "opt out", which is not the intended effect!
I and other plugin others mistakenly thought that "disable" merely shuts down the plugin temporarily (e.g. housekeeping such as cancelling the scheduler task) but it also sets the global opt-out configuration to "opt out", which is not the intended effect!