Forum Replies Created

Viewing 15 replies - 121 through 135 (of 1,619 total)
  • Plugin Support khungate

    (@khungate)

    Hi everyone, thank you for your patience as we investigated this further. It appears that the issue is caused by the absence of a site title in your WordPress installation. As a temporary fix, you can resolve the error by adding a site title here: https://a.cl.ly/NQu9k9xE. We’ll be addressing this in a future update to ensure a site title won’t be required.

    Plugin Support khungate

    (@khungate)

    Hi @eurosatsco, the error reads : Required fields were not provided: name which sounds like it may be a custom merge tag. Out of the box, we sync merge tags FNAME and LNAME. Can you double check your merge tags in your list? You can find this by going to your Audience settings. Here’s a look at an example: https://a.cl.ly/xQuJPe5z.

    If the First Name is marked NAME in your Audience instead of FNAME that would require a custom merge tag configuration as described. Or, you could simply rename NAME to FNAME in your Mailchimp Audience settings and that would do the trick.

    Let us know what you find, happy to assist further.

    Plugin Support khungate

    (@khungate)

    Hi @eurosatsco, it sounds like you’re using a custom merge tag, which is preventing the sync. Please check out the solution provided in our GitHub repository: Custom Merge Tags Solution. This link contains detailed instructions that should help resolve your syncing issue.

    If the problem persists, please share more details, and we’ll be happy to assist further.

    Plugin Support khungate

    (@khungate)

    Hi @hetaweb, if you’re experiencing a problem with syncing of coupon codes from WooCommerce to Mailchimp here’s a few things to troubleshoot and hopefully resolve this issue:

    1. Clean Reinstallation of the Plugin: Uninstall the Mailchimp for WooCommerce plugin, delete it from your WordPress, and then reinstall it. This can help eliminate any errors that might have occurred during the initial installation.
    2. Checking and Enabling WP CRON: Ensure that WP CRON is enabled on your WordPress site. WP CRON is necessary for Action Scheduler tasks, which are crucial for operations like syncing. If it’s not enabled, you can turn it on by setting up a real cron job or by enabling the WP CRON setting in your WordPress.
    3. Deactivate Other Plugins: Deactivate all plugins except for WooCommerce and Mailchimp for WooCommerce. This step helps isolate the issue to see if it’s being caused by a conflict with another plugin: https://docs.woocommerce.com/document/how-to-test-for-conflicts/.

    If none of those resolve your issue:

    1. Review Logs: Check the plugin’s logs tab for any fatal errors that might provide more insight into what might be causing the issue.
    2. Enable Remote Diagnostics: If the issue persists, you can enable the Remote Diagnostics setting within the Mailchimp for WooCommerce plugin settings and provide your URL here. This allows the plugin engineers to investigate further.
    Plugin Support khungate

    (@khungate)

    Hi @devancadman, it sounds like there may be a plugin conflict in this situation as we’ve been able to confirm that this works properly in our testing environment. To address instances where the plugin is not functioning correctly, you can verify and attempt the following troubleshooting steps:

    • Verify the latest plugin version is being used.
    • Switch themes to the default WooCommerce one, deactivate all plugins except WooCommerce and Mailchimp for WooCommerce, and test the scenario again – ideally in a staging environment.
    • Test for conflicts by following this guide, WooCommerce: Fixing Theme and Plugin Conflicts: https://docs.woocommerce.com/document/how-to-test-for-conflicts/
    • If you use a caching service like Cloudflare, add an exclusion path for the Mailchimp for WooCommerce plugin to prevent caching conflicts. Set the exclusion path at the server level, typically by creating a rule for the “URL Path” such as /wp-content/plugins/mailchimp-for-woocommerce/.
    • Try uninstalling and reinstalling the plugin from scratch and see if the problem persists.
    • Review any log errors in the plugin’s logs tab or enable the Remote Diagnostics in the Settings area of the plugin to allow our engineers to investigate further.
    Plugin Support khungate

    (@khungate)

    Hi @gbotica, we just wanted to check back with you to see if this was still a problem with our latest plugin (v4.2.1 at the time of this post). Please let us know when you get a moment, we’ll be happy to help troubleshoot further if necessary.

    Plugin Support khungate

    (@khungate)

    Glad to hear that fixed the issue! If anything else pops up, don’t hesitate to reach back out to us. We appreciate you using the plugin.

    If you’re happy with this integration, please consider leaving a 5-star review. Your feedback helps other WooCommerce customers find this integration and helps support future development.

    Plugin Support khungate

    (@khungate)

    Hi @amdon, thank you for reaching out. To assist you better, we need some additional details about the issue you’re experiencing. Here are a few points that would help us troubleshoot effectively:

    1. Clarification on the email field: Could you specify whether the issue pertains to the billing_email field for orders or users? This will help us understand where the problem might be occurring.
    2. Details on the plugin’s functionality: When you mention the plugin has stopped working, could you elaborate on what specific functionality is affected? For instance, is it not capturing email addresses, not sending emails, or some other issue?
    3. Error specifics: It appears there might be an error related to the billing_email selector on the checkout page. If you have any error messages or logs, please share them. This information is crucial since client-side errors can sometimes be tricky to diagnose without specific details.

    As a preliminary check, our developer has reviewed the plugin and confirmed that no filters or hooks are currently applied to the email fields. This means the issue might be arising from another source or a conflict with another plugin or theme.

    Looking forward to your response with the additional details so we can assist you further.

    Plugin Support khungate

    (@khungate)

    Hi @freshynathan, we just wanted to check back with you to see if this was still a problem with our latest plugin (v4.2.1 at the time of this post). Please let us know when you get a moment, we’ll be happy to help troubleshoot further if necessary.

    Plugin Support khungate

    (@khungate)

    Hi @sareejoh, hi there, we just wanted to check back with you to see if this was still a problem with our latest plugin (v4.2.1 at the time of this post). Please let us know when you get a moment, we’ll be happy to help troubleshoot further if necessary.

    Plugin Support khungate

    (@khungate)

    Hi @mattinventive, thanks for reaching out, it sounds like there may be a plugin conflict somewhere and to address instances where the plugin is not functioning correctly, you can verify and attempt the following troubleshooting steps:

    • Verify the latest plugin version is being used (4.2.1 at the time of this post): https://wordpress.org/plugins/mailchimp-for-woocommerce/
    • Switch themes to the default WooCommerce one, deactivate all plugins except WooCommerce and Mailchimp for WooCommerce, and test the scenario again – ideally in a staging environment.
    • Test for conflicts by following this guide, WooCommerce: Fixing Theme and Plugin Conflicts: https://docs.woocommerce.com/document/how-to-test-for-conflicts/
    • If you use a caching service like Cloudflare, add an exclusion path for the Mailchimp for WooCommerce plugin to prevent caching conflicts. Set the exclusion path at the server level, typically by creating a rule for the “URL Path” such as /wp-content/plugins/mailchimp-for-woocommerce/.
    • Try uninstalling and reinstalling the plugin from scratch and see if the problem persists
    • Review any log errors in the plugin’s logs tab or enable the Remote Diagnostics setting so the plugin engineers can investigate further.

    Would you care to check these first and see if the problem persists? Also, I’m not familiar with that error message – is that the actual screenshot?

    Plugin Support khungate

    (@khungate)

    Hi @seb112, it sounds like there may be a plugin conflict somewhere, and we’d like to take a look at your logs if the problems persist. Can you follow the steps below first and let us know if you’re still having the issue described? FYI you don’t need to create the webhooks manually, we take care of all that on installation.

    To address instances where the plugin is not functioning correctly, you can verify and attempt the following troubleshooting steps:

    • Verify the latest plugin version is being used.
    • Switch themes to the default WooCommerce one, deactivate all plugins except WooCommerce and Mailchimp for WooCommerce, and test the scenario again – ideally in a staging environment.
    • Test for conflicts by following this guide, WooCommerce: Fixing Theme and Plugin Conflicts: https://docs.woocommerce.com/document/how-to-test-for-conflicts/
    • If you use a caching service like Cloudflare, add an exclusion path for the Mailchimp for WooCommerce plugin to prevent caching conflicts. Set the exclusion path at the server level, typically by creating a rule for the “URL Path” such as /wp-content/plugins/mailchimp-for-woocommerce/.
    • Try uninstalling and reinstalling the plugin from scratch and see if the problem persists.
    • Review any log errors in the plugin’s logs tab or enable the Remote Diagnostics setting so the plugin engineers can investigate further.
    Plugin Support khungate

    (@khungate)

    Hi @gbotica, it does indeed sound like a plugin conflict. Please let us know if you can pinpoint anything, and we’ll be happy to help troubleshoot further if needed. Also, if you haven’t already seen, we just released the latest version of the plugin today (4.2). While this update may not resolve your current issue, we encourage you to update to benefit from the latest improvements and fixes.

    Plugin Support khungate

    (@khungate)

    Hi @kingyyyy we wanted to let you know this has been addressed in the latest release of the plugin (4.2). Appreciate you calling our attention to this issue.

    Plugin Support khungate

    (@khungate)

    Hi there, we’re going to close out this ticket for now since it’s been a few weeks since we’ve been in touch.

    Please let us know if you still need any help and we’ll be glad to reopen and troubleshoot further. Please note, that the best way to reach us is over at the GitHub plugin page: https://github.com/mailchimp/mc-woocommerce/. From there, you can receive direct responses from the development team, log new issues, download the latest version, and track existing support tickets.

Viewing 15 replies - 121 through 135 (of 1,619 total)