Forum Replies Created

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

    (@khungate)

    Hi @devancadman, 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.

    Plugin Support khungate

    (@khungate)

    Hi @alijens, Hi there, we just wanted to check back with you to see if this was still a problem with our latest plugin (v4.4 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 @babelhalsupport,

    Thanks for your patience while we researched this further. We’ve attempted to recreate the issue on our end but haven’t been able to do so. I’d recommend upgrading the plugin to the latest version (4.4) from your current version (4.2.1) to see if that resolves the issue.

    If the problem persists after the update, it’s likely due to a plugin or theme conflict. Here are some steps you can follow to troubleshoot: How to Troubleshoot Plugin or Theme Conflicts:

    Update Everything:

      • Ensure WordPress, your theme, and all plugins are updated to their latest versions, as outdated versions can sometimes cause conflicts.

      Switch to a Default Theme:

        • Temporarily switch to a default WordPress theme like Twenty Twenty-Three to check if the issue is related to your current theme.
        • To switch themes:
          • Go to Appearance > Themes.
          • Activate a default theme and check if the problem persists.

        Deactivate All Plugins:

          • Deactivate all other plugins except the one in question.
            • Go to Plugins > Installed Plugins.
            • Select all plugins and choose “Deactivate” from the bulk actions dropdown.
          • Test the site functionality after deactivating to see if the issue is resolved.

          Reactivate Plugins One by One:

            • Reactivate each plugin one by one, checking for the issue after each activation. This will help identify if a specific plugin is causing the conflict.

            Check the Browser Console for Errors:

              • Open your browser’s developer tools (press F12 or Ctrl+Shift+I) and look for any JavaScript errors in the Console tab. Errors here may indicate a conflict.

              Use a Staging Environment:

                • If possible, perform these steps in a staging environment to avoid affecting your live site. You can use a plugin like WP Staging or set up a local development environment.

                Enable Debugging Mode:

                  • Turn on WordPress debugging by adding the following lines to your wp-config.php file:
                    php define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false );
                  • This will log any errors to a debug.log file located in your wp-content directory.

                  Following these steps should help pinpoint whether the issue is related to a theme or plugin conflict. Let us know how it goes or if you need further assistance!

                  Plugin Support khungate

                  (@khungate)

                  Hi @sunnydhain1, here are some examples of fatal errors that have happened today.

                  • WooCommerce: 335 fatal error instances
                  • Elementor: 81 fatal error instances
                  • TFC-ID: 2 fatal error instances

                  You can also see these by going to:

                  1. Navigate to your WooCommerce admin dashboard.
                  2. Click on “WooCommerce.”
                  3. Select “Status.”
                  4. Open the “Logs” tab at the top.
                  5. From the dropdown, choose the “fatal errors” log and click the source link.

                  uncaught error: call to a member function get_id() on string in /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/tfc-id/inc/ajax.php:27 context: {"error":{"type":1,"file":"/home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/tfc-id/inc/ajax.php","line":27},"backtrace":["","#0 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-includes/class-wp-hook.php(324): initialiseverification()","#1 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-includes/class-wp-hook.php(348): wp_hook->apply_filters()","#2 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-includes/plugin.php(517): wp_hook->do_action()","#3 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-admin/admin-ajax.php(192): do_action()","#4 {main}","thrown"]}

                  uncaught error: call to undefined function shell_exec() in /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/themes/shoptimizer-child/functions.php:261 context: {"error":{"type":1,"file":"/home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/themes/shoptimizer-child/functions.php","line":261},"backtrace":["","#0 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-includes/class-wp-hook.php(324): custom_checkout_field_display_admin_order_meta()","#1 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-includes/class-wp-hook.php(348): wp_hook->apply_filters()","#2 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-includes/plugin.php(517): wp_hook->do_action()","#3 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/woocommerce/includes/admin/meta-boxes/class-wc-meta-box-order-data.php(514): do_action()","#4 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-admin/includes/template.php(1456): wc_meta_box_order_data::output()","#5 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-admin/edit-form-advanced.php(723): do_meta_boxes()","#6 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-admin/post.php(206): require('/home/791695.cl...')","#7 {main}","thrown"]}

                  In regards to variations, the Mailchimp editor unfortunately doesn’t support them in their feature set. Here at the plugin development team we don’t have any control over that functionality, but feel free to reach out to Mailchimp directly to push that feature request, it’s something that others have inquired about as well.

                  Your e-commerce data should sync/backfill over provided you were using a previous plugin after v2.3 (which was several years ago). If you’re still have questions around any particular order or customer please send us over and ID and we’ll be happy to investigate further.

                  Plugin Support khungate

                  (@khungate)

                  Hi @dobrabant,

                  Thank you for reaching out and sharing your experience. I’m sorry to hear that you’ve encountered issues with syncing orders and contacts in your WooCommerce stores. We’re constantly working to improve the plugin, so your feedback is invaluable.

                  You mentioned waiting for changes from the developers—could you clarify which specific updates or features you were expecting? If there’s a particular post or GitHub issue where these have been raised, please let me know so I can check the status.

                  We’d be happy to help work through any challenges you’re facing. Our goal is to ensure the plugin works smoothly for all users, regardless of the platform, and I’d love to understand more about what’s been going on in your stores. Feel free to provide any additional details about the problems you’re experiencing, and we’ll do our best to assist you.

                  Looking forward to hearing from you.

                  Plugin Support khungate

                  (@khungate)

                  Hi @sunnydhain1, glad to hear you were able to work through the first example with the fatal logs. However, we’re still seeing quite a few fatal logs as recent as today so it may be worth spending some time there to see if they can be resolved as well; let me know if you need examples but these should be viewable on your side as well. Let me address your other follow up questions:

                  1. Product variations – unfortunately, product variations aren’t supported in the Mailchimp campaign builder at this time. This is something that is known limitation with the product development team, hopefully in the near future the editor is upgraded to handle.
                  2. Syncing speed – syncing is impacted by site traffic to trigger Action Scheduler events which power the sync. If your site has less traffic, you might need to configure a cron job that runs every minute to simulate server traffic. This will activate the WP CRON scheduled events, which is particularly useful for triggering background jobs that the Action Scheduler needs to complete. You can configure a cron job by adding the following to your CPanel or CRONTAB, depending on what your host allows: */1 * * * * wget -q -O - https://site.com/wp-cron.php?doing_wp_cron. By doing this, the Action Scheduler will be able to trigger these background jobs all day, regardless of your site traffic. This approach is recommended because the Action Scheduler needs to be triggered by normal site traffic in regular mode. For better performance, you may also consider using the CLI version. Instructions for this can be found here.

                  Please let us know if you have any follow up questions, happy to help.

                  Plugin Support khungate

                  (@khungate)

                  Thank you @sunnydhain1, we’re seeing a few things here, rest assured we want to ensure we get you shored up.

                  1. You have some fatal logs in your store which could be impacting the syncing process. You may want to go through the plugin conflict resolution process if you’re not able to identify which one it’s related to. Here’s an example: uncaught exception: invalid coupon. in /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/woocommerce/includes/data-stores/class-wc-coupon-data-store-cpt.php:118 context: {"error":{"type":1,"file":"/home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/woocommerce/includes/data-stores/class-wc-coupon-data-store-cpt.php","line":118},"backtrace":["","#0 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/woocommerce/includes/class-wc-data-store.php(159): wc_coupon_data_store_cpt->read()","#1 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/woocommerce/includes/class-wc-coupon.php(156): wc_data_store->read()","#2 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/woocommerce/includes/class-wc-coupon.php(144): wc_coupon->read_object_from_database()","#3 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/yith-woocommerce-points-and-rewards-premium/includes/class-yith-wc-points-rewards-redeeming.php(1076): wc_coupon->__construct()","#4 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/yith-woocommerce-points-and-rewards-premium/includes/class-yith-wc-points-rewards-redeeming.php(923): yith_wc_points_rewards_redeeming->get_current_coupon()","#5 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-content/plugins/yith-woocommerce-points-and-rewards-premium/includes/class-yith-wc-points-rewards-redeeming.php(841): yith_wc_points_rewards_redeeming->apply_discount_calculation()","#6 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-includes/class-wp-hook.php(324): yith_wc_points_rewards_redeeming->apply_discount()","#7 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-includes/class-wp-hook.php(348): wp_hook->apply_filters()","#8 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-includes/plugin.php(517): wp_hook->do_action()","#9 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-settings.php(722): do_action()","#10 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-config.php(105): require_once('/home/791695.cl...')","#11 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-load.php(50): require_once('/home/791695.cl...')","#12 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/wp-blog-header.php(13): require_once('/home/791695.cl...')","#13 /home/791695.cloudwaysapps.com/zrahhqqqse/public_html/index.php(17): require('/home/791695.cl...')","#14 {main}","thrown"]}
                  2. There are errors showing up in our plugin order_submit.error :: addstoreorder :: #orderIDnumberhere :: error code 400 :: a product with the provided variant id does not exist in the account for this list. This usually means that a product has been deleted in your store and the orders can’t be submitted to Mailchimp.
                  3. Logs also show order_submit :: #orderIDnumberhere has a financial status of cancelled and was skipped. Mailchimp will only receive orders from WooCommerce that have the statuses of ProcessingCompleted, and Paid.

                  Could you look at #1 first and let us know if there is a particular order ID in question? We’ll be happy to investigate further.

                  Plugin Support khungate

                  (@khungate)

                  Hi @sunnydhain1, we’ll be glad to help and we should be able to backfill your campaign attribution if you were using an up to date plugin previously. Would you care to turn on your remote diagnostics in the Settings area of the plugin so we can investigate further?

                  Plugin Support khungate

                  (@khungate)

                  Hi @quadlayers, 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, have additional thoughts around the proposed solution 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.

                  Plugin Support khungate

                  (@khungate)

                  Hi @seb112, 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.

                  Plugin Support khungate

                  (@khungate)

                  Hi @amdon, 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.

                  Plugin Support khungate

                  (@khungate)

                  Hi there, we just wanted to check back with you to see if this was still a problem with our latest plugin (v4.3.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 there, we just wanted to check back with you to see if this was still an issue. Please let us know when you get a moment, we’ll be happy to help troubleshoot further if necessary.

                  Plugin Support khungate

                  (@khungate)

                  @jonahcoyote thanks for reaching out. We’re researching this issue further and will update this post with any findings that we have.

                  Plugin Support khungate

                  (@khungate)

                  Hi there, we just wanted to check back with you to see if this was still a problem with our latest plugin (v4.3 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.

                Viewing 15 replies - 91 through 105 (of 1,619 total)