Support » Plugin: MailPoet - emails and newsletters in WordPress » Please allow greater control over WooCommerce integrations

  • Resolved deltafactory


    Dear @mailpoet/@wysija-newsletters,

    MailPoet’s WooCommerce integrations *unexpectedly* add a lot of new functionality to a WooCommerce site. In my situation, we *do not want* abandoned cart emails, first-time purchase emails, and some of the other metrics that are instantly calculated.

    On top of this, we’re using an older, highly customized version of WooCommerce. There are incompatible assumptions that MailPoet makes about the WC API/class interfaces. We have experienced fatal errors, MySQL transaction deadlocks, and a number of unintended consequences.

    While it’s no doubt that the functionality you provide is valuable to a large part of your audience, developers/owners of big sites need to trust that a plugin upgrade won’t alter the status quo without configurable action on their part.

    Specifically to address this issue, I have modified some core plugin code (as a last resort) to convince MailPoet that WooCommerce isn’t available. However, some of the init code hooks into WooCommerce actions/filters anyway. I hope some day those items could be addressed and some sort of “master switch” could be made available to permanently solve this concern.

    Also, I don’t know what sort of audit trail is available to track the sending of automatic emails categories described above. Anything would be helpful since we’re otherwise completely ignorant of what a customer sees unless they report it to us. It’s unacceptable for these messages to be sent on our behalf without opportunity to customize the presentation and content.

    I hope we can work together to develop acceptable options. Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor MailPoet


    @deltafactory no automatic WooCommerce email will be sent if you didn’t create them, that’s simple.

    A hook to disable the WooCommerce functionality can definitely be considered, but if you are running a modified version of WooCommerce things will definitely not work as expected and that’s something we can’t predict.

    To clarify, our customizations exclusively use hooks, filters, and template extensions which is should be a valid consideration during your development cycle. The key is that the version of WooCommerce is old enough that certain WC API/function calls do not exist where you assume they do.

    There are a number of hooks that are registered for WooCommerce orders regardless the detection of WooCommerce. The stats gathering and subscriber syncing cannot be disabled in a non-invasive way, and have disrupted the checkout process in multiple ways.

    I’m asking for minimal version/compatibility checks against a plugin that you are trying to integrate with. I’m also hoping for greater isolation of those integrations for those who find that level of data collection disruptive or inappropriate.

    I am likely in the minority but I don’t think it’s appropriate that the plugin has decided that our customers are also subscribers, and has taken upon itself collating sales data about them.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.