Saint Systems

We have published another small update v2.4.7 to tell the Mailchimp API to skip merge field validation.

Please update and let us know if you encounter the error again.

@toxoplasmaarts,

We released another small update v2.4.6 that adds additional error details to the logs in the event of this error. This should provide more detail regarding which merge field is having an issue.

The most common error is an error with the ADDRESS merge field. Even if it is not marked required, if there is an error with the ADDRESS merge field, you will get back a “Please enter a complete address” error.

This means that the merge field “ADDRESS” is missing or incomplete. When there is an incomplete or invalid address on a subscriber, Mailchimp will not let you or any third-party app (i.e. our plugin) update any merge field until the invalid field has been fixed. Unfortunately, Mailchimp does allow some connected e-commerce platforms to sync subscribers even though they have invalid addresses.

Hi there @toxoplasmaarts,

We just published a small update (v2.4.5) to hopefully address this.

Please let us know if you still experience any issues and feel free to open a ticket at our help center: https://support.saintsystems.com/hc/

Hi there,

This isn’t yet included in our pro version, but will be added to a future update.

Let us know if you’d be interested in being notified when it’s available.

@rtpharry,

Glad to hear it. Let us know if you encounter any other issues.

Closing as we have moved this discussion to our ticketing system.

@rtpharry,

In any case, we just published another small update (1.3.0), which now forces logout of disabled users. Please update to that version and let us know if you encounter that issue again.

@rtpharry,

Hi there. We’re unable to reproduce this error in our test environment.

If the problem persists for you, can you reach out to us via https://support.saintsystems.com/hc/en-us/requests/new and send us a screenshot of the error and any applicable logs?

Thank you.

@florianvb,

Sorry for the delay in responding to this. There isn’t currently a way to automatically unsubscribe customers who cancel an order, but that is a good feature request. I’m going to add it to our list of features to consider.

If we implement this, most likely we would make it an option where you could choose the behavior and opt-in to doing this.

Thanks and stay tuned.

@mxnj,

Please let us know if you’re still receiving this error.

@yaniv691,

Hello and thanks for your question!

Our Pro version is designed specifically for the use case you described – allowing you to control (at the product level) what list, interest groups, and tags are associated with the customer in Mailchimp.

You can check out our pro version here: https://www.saintsystems.com/products/woocommerce-mailchimp-pro/

The pro version extends our free plugin will allow you to specify at the product level different lists for purchasers of the product. Or, you can assign the same list and choose to segment the subscribers with interest groups and/or tags.

Please let us know if you have any questions!

@dustysheldon,

Sorry for the delay on this, but this has been fixed in v2.3.13 which was published today.

@dustysheldon,

Thank you for reporting this issue. We have captured it as a new issue on Github here: https://github.com/anderly/woocommerce-mailchimp/issues/29.

You can monitor that issue for status and we’ll post back to here as well once a fix is in place.

• This reply was modified 4 years, 7 months ago by Saint Systems.

@sync4489 thanks for your question.

Glad to hear you were able to solve the first issue with Admin Columns.

We’ll look at the possibility of forcing the user to logout when disabled.

@r181 We would need you to enable detailed logging on the WooCommerce > Settings > Mailchimp > Troubleshooting tab so we can review the detailed error message. This looks like it may have been an transient network error communicating with the Mailchimp API.

Let us know if you’re still experiencing any issues or need us to review the logs.