The plugin ignores native WP settings and forces automatic updates

This plugin adopts a behavior that I consider bad practice. It intentionally bypasses the native WordPress system by registering its own auto_update_plugin filter to decide for itself whether automatic updates should be enabled.

As a result, the WordPress “Enable/Disable automatic updates” button no longer accurately reflects the plugin’s behavior. Even after disabling updates from the admin interface, the plugin continues to use its own internal method to make the decision.

A plugin shouldn’t take over such a fundamental WordPress feature. Administrators expect interface settings to take precedence, not to be silently ignored by a specific implementation.

This approach unnecessarily complicates site maintenance, surprises administrators, and sometimes requires writing custom code just to restore WordPress’s normal behavior.

I appreciate the integration with WooCommerce and MailerLite, but this design choice is difficult to justify and goes against the principle of least surprise. A plugin should respect the administrator’s decisions, not circumvent them.