@maxmillionmusic, sorry to hear you’re having issues with the plugin, we definitely want to try to help out. Just to get a handle on the situation you’re experiencing, could you provide a few more pieces of information to help us understand the issue?
– What plugin version are you using?
– What version of PHP are you using?
– Are there any fatal errors in WooCommerce? (WooCommerce -> Status -> Logs)
– If you have a large number of plugins being used, you may need to bump up your memory limit on your server (1GB for example) to accommodate the initial sync.
– If you haven’t already, please browse through our wiki to find documentation on the most common issues and how to resolve them: https://github.com/mailchimp/mc-woocommerce/wiki
Thanks in advance for these details. I’ll keep an eye out for your reply.
– Latest updates on WordPress, Woocommerce and your Plugin
– PHP 7.3
– No Errors
– Memory is 2GB
– Documentation is already checked, contacted your support for over a week, but not a single solution.
judging from the rest of the forum here, your Plugin is very problematic,
I am getting way different responses from your support, each agent is suggesting something different or asking if i have errors like “header not being allowed”
Do not have any bad feedback from the dev-team, however i was expecting a more solid solution from Mailchimp especially when most of us pay almost half a rent for Mailchimp services each month. I would expect a pro solution and not a poor coded thing that sometimes work and sometimes not.
After a whole week of unsuccessful troubleshooting i gave up and purchased a third party solution plugin from another developer and it worked in under 2 mins of setup.
Thanks
@maxmillionmusic Sorry you’ve been having trouble connecting the plugin – I wish we could have helped you here before you went through all the disabling etc.
There’s a reason that the support agents were asking about “header not allowed” – it’s because sometimes sites are making use of a non-standard header for all ajax requests being sent with jQuery. Our OAuth server is rejecting this right after you tried to connect the account because it’s happening on the browser’s side. Our server never catches this, so it went silent on our end.
We’ve got this fixed in our next release 2.4.2. Once you get past this step, you would not have had trouble.
Be glad to walk you through this if you needed to set it up before we push the new release. It’s super easy to do.
