HELOstore
Forum Replies Created
-
Ah sorry for that. I was just trying to make a point.
I understand that sometimes things just get out of hands, and sometimes we all need some help. So if you need help with proper unit testing of your products, just let me know and maybe I could give you a hand, the right way (on your expense). I think you could definitely benefit from this :))
I just realized this new bug is totally unrelated to the current topic, so I created a new post for it: https://wordpress.org/support/topic/url-change-from-http-to-https-creates-new-store-in-mailchimp/
I guess that comment above can be deleted.Okay, so we stumbled into another bug in your “mailchimp-for-woocommerce”.
We just switched to HTTPS everything, and started enforcing HTTPS.
But, once the enforcing was put in place, boom. The plugin’s API synchronization stopped working. Why? Why, why.. Why us!? (and other dramatic sounds)Here’s why:
File: wp-content/plugins/mailchimp-for-woocommerce/mailchimp-woocommerce.php Line: 62 Code: function mailchimp_get_store_id() { return md5(get_option('siteurl')); }You generate the Store ID by hashing the
siteurlvariable, and that variable just got updated fromhttp://example.comtohttps://example.com. Same domain, but different protocol.
So now your plugin tries to sync data using a Store ID that does not exists in MailChimp! And it fails, obviously, throwing exception like this one:
“Resource Not Found :: The requested resource could not be found.” (which makes sense, because there is no such store in MailChimp)
This exception is thrown at:wp-content/plugins/mailchimp-for-woocommerce/includes/api/class-mailchimp-api.php:1001Before figuring this out, I went through your plugin’s settings. In absolutely no place does it say it’s screwed up, or that the store ID has changed, or that I should update the store’s domain in MailChimp. It says absolutely nothing to warn us about this potential issue.
And, after clicking the Save button, it created a new (empty) store in MailChimp.And I don’t even know what does this mean for us, what are the implications. When the segments are updated based on E-commerce criteria (like Orders_count and Total_spent), will it look in both lists from now on? If yes, how it will decide which is the Total_spent? Or will it only look in the newest (empty) store?
I did everything the book, and even so, my client got screwed up and is paying hours and hours for hunting down & debugging your bugs, and for remediation of problems that shouldn’t exist if you would’ve thoroughly tested your product.
Is this fair to my client, MailChimp?@aand, the most obvious sign is seeing unsubscribed people by an admin without mentioning a reason. An admin should always document it’s actions. We knew that no admin among us would’ve had any reason do unsubscribe these members, one after another, and they all had recent purchases.
Also the unsubscribe timing is a pretty obvious sign: they were unsubscribed a few minutes after a purchase; they received an email confirmation with an URL to their profile, they’ve logged in into our WP and updated their profile, and boom, they got automatically unsubscribed.
The good news is that, IN THIS CASE, Mailchimp allows you, the admin, to re-subscribe them, without having to ask them to opt-in again.
Leaving the subscription checkbox unchecked will still update the original MailChimp subscriber’s information to match the latest provided information on Checkout, but it will not unsubscribe this list member.
I disagree.
You’re doing this:$api->update($list_id, $user->user_email, $this->subscribed, $merge_vars); // File: wp-content/plugins/mailchimp-for-woocommerce/includes/processes/class-mailchimp-woocommerce-user-submit.php // Line: 115And if $this->subscribed is false for whatever reason, that call will unsubscribe the member from the list. I unhooked handleUserUpdated() and handleUserRegistration() and everything’s okay now.
Well … I already find out why that happens and fixed my local installation.
But sure, you may wanna fix that in the repository as well, as people will keep getting screwed by this.I posted this in the wrong forum as well. See the “mc-wc-wtf.jpg” screenshot below.
At 2. I’m talking about this: https://drive.google.com/file/d/0B1Spew9GOmzCaVdBcXQwNUlSR00/view?usp=sharing
Good luck!
Dang it. I was ranting on the wrong plugin’s forum. Sorry Adam!
Now that they changed it, the two plugins’ names are pretty confusing though.
I’m re-posting this on the suggested thread, thanks Aand.This is bonkers.
1. The plugin assumes there must be an opt-in form on the website it’s installed on.
2. And if you don’t have an opt-in form in said website, when “profile_update” action is triggered the plugin will unsubscribe customers which subscribed from some other place (e.g. MailChimp API calls!) Also, “profile_update” can be triggered by WP API calls too, so the plugin will attempt to update the optIn status every time, which makes no sense!
3. Point 2. should be mentioned in the description of the plugin because it’s potentially destructive.Awesome stuff. Now let’s see how can I reverse all of this and re-subscribe those customers while not looking like a chump.
(I posted this into the wrong forum a few days ago, because there are 2 plugins with similar names, which is confusing.)
At 2. I’m talking about this: https://drive.google.com/file/d/0B1Spew9GOmzCaVdBcXQwNUlSR00/view?usp=sharing
This is bonkers.
1. The plugin assumes there must be an opt-in form on the website it’s installed on.
2. And if you don’t have an opt-in form in said website, when “profile_update” action is triggered the plugin will unsubscribe customers which subscribed from some other place (e.g. MailChimp API calls!) Also, “profile_update” can be triggered by WP API calls too, so the plugin will attempt to update the optIn status every time, which makes no sense!
3. Point 2. should be mentioned in the description of the plugin because it’s potentially destructive.Awesome stuff. Now let’s see how can I reverse all of this and re-subscribe those customers while not looking like a chump.