• Resolved Mattw1000

    (@mattw1000)


    I had some very odd things going on with this plug in active.

    It made random blog posts, go to Internal 500 errors.

    As soon as i switched this off, they were all fixed and back to normal

    Anyone else experience this please?

    Thanks
    Matt

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hey @mattw1000,

    Thanks so much for reaching out! That does not sound ideal at all and I’ll be happy to take a look and see what’s up. To clarify a bit, the MailChimp for WooCommerce integration is not programmed to make blog posts, and we wouldn’t expect it to cause the behavior described. That being, said something weird definitely seems to be going on here, so I’d love to dig in. Do you mind getting back to us with your WooCommerce System Status Report? That will provide us with your environmental details and allow us to try to replicate the described behavior on our end. Also, could you please provide us with the full 500 error response you’re seeing on your end, as well as what steps were taken leading up to seeing that error? A screenshot of the error would be excellent, if possible. Additionally, have you ever shared the connected MailChimp API key anywhere? If so, that would make it vulnerable and render the connection insecure. If the API key was ever shared, I would advise disabling that key and trying activation with a fresh generated MailChimp API key.

    Thanks! I look forward to seeing your reply and helping out as much as I can.

    Pearl

    Thread Starter Mattw1000

    (@mattw1000)

    Hey Pearl,

    Thanks for getting back so quick! be great to get this fixed as i really want to include products in my mail chimp emails etc.

    Is there somewhere i can email you that info please? would prefer not to put it all up here.

    Because i switched the plug in off, i can no longer take screen shots of the 500 error but if you let me know the best place to see them error in more detail i can try switching it back on quickly. Would you suggest google chrome console or something along that line?

    API – the only other places i have used it are for syncing other plug ins to mail chimp and wordpress. Is that the kind of sharing you mean? Should i be creating an api key for each new plug in i am syncing?

    Thanks
    Matt

    Hey @mattw1000,

    I totally understand the concern here. If you’d prefer a bit more privacy, please feel free to reach out to the MailChimp support team following the steps outlined here and include a link to this support forum post. They will be able to take a closer look at all of your MailChimp account activity and help out. Please include your WooCommerce System Status report.
    As to grabbing more information about that 500 error you were seeing – if you see anything related to MailChimp in your server error logs that would be helpful for sure. Also, I understand not wanting to re-activate the plugin, but any specifics you remember (or see, if you choose to reactivate the plugin temporarily to help with the investigation) would help us get the ball moving in the right direction.
    Regarding that API key – it’s generally a good idea to use one API key for each integration. That can be really helpful when it comes time to troubleshoot. If I remember correctly, in MailChimp it’s possible to set a label or “name” for each API key that’s created. I found this MailChimp knowledge base guide here that may help out if you’re interested: https://kb.mailchimp.com/integrations/api-integrations/about-api-keys

    Thanks!

    Pearl

    Thread Starter Mattw1000

    (@mattw1000)

    Thanks Pearl, ill email them now.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Causing Internal 500 server error’ is closed to new replies.