API error after upgrade

  • Resolved castlebuilder

    (@castlebuilder)


    2 years, 8 months ago

    Moving to my own topic continued from below.

    With 2.7, I get:

    Mailchimp says: API Request Error – CURL error :: bind failed with errno 22: Invalid argument on 2193 in /home/aiaweb/public_html/wp-content/plugins/mailchimp-for-woocommerce/includes/api/class-mailchimp-api.php

    But it is fine with 2.6.

    You asked for me to “enable the remote diagnostics toggle in the plugin (under settings)” but I do not see this in 2.6, and when I upgrade to 2.7, I only get the error and no settings available. If I close the error, I have the Mailchimp logo but otherwise a blank page. Please advise!

    Error in WP log:

    [07-Jul-2022 16:02:53 UTC] WordPress database error Incorrect table name ” for query SHOW FULL COLUMNS FROM made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, mailchimp_on_all_plugins_loaded, run_mailchimp_woocommerce, MailChimp_WooCommerce->__construct, MailChimp_WooCommerce->registerWebhooks, MailChimp_WooCommerce_Admin->defineWebHooks, mailchimp_handle_or_queue, mailchimp_as_push, as_schedule_single_action, ActionScheduler_ActionFactory->single, ActionScheduler_ActionFactory->store, ActionScheduler_DBStore->save_action, ActionScheduler_DBStore->get_group_id, ActionScheduler_DBStore->create_group`

    • This topic was modified 2 years, 8 months ago by castlebuilder.

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author ryanhungate

    (@ryanhungate)

    @castlebuilder this is really strange – but could be related to needing an upgrade on the Action Scheduler plugin. Can you please check to see which version of the scheduler you’re using currently? We actually may need to pass this over to the WooCommerce team to make sure you’ve got everything squared away before getting to this next step.

    Thread Starter castlebuilder

    (@castlebuilder)

    We are using the latest version of WooCommerce and all related plugins. “Action Scheduler” is packaged into WooCommerce, I’m not using it as a separate plugin (should I be?). Version 3.4.0 is what is in WooCommerce 6.6.1.

    Thanks!

    Plugin Author ryanhungate

    (@ryanhungate)

    @castlebuilder something just came to mind that had happened in the past. Do you by chance have the “Follow Up Emails” plugin?

    If so this is the thread that discusses this problem and I think you might be able to find a solution.

    Sometimes it’s just a random plugin that alters the state of the site and it must be resolved.

    Plugin Author ryanhungate

    (@ryanhungate)

    @castlebuilder just a follow up on this thread to make sure you know that the error you’re experiencing on 2.7 is a different error than the one you’re seeing on 2.6.2.

    The 2.7 version you probably need to specify your IP address in your wp-config.php file. We have documentation on that here.

    Please let us know once you’ve been able to resolve the action scheduler table issue, we understand how that could be frustrating.

    Thread Starter castlebuilder

    (@castlebuilder)

    @ryanhungate Thanks for your help. Adding this code to wp-config.php seems to have solved the problem:

    define( ‘MAILCHIMP_USE_OUTBOUND_IP’, false );

    FYI we are not using the “Follow Up Emails” plugin. I know that these sorts of errors can be a plugin conflict, though. Also note that I was not seeing any errors on versions except for 2.7, so not sure about different error(s) you are referring to above.

    Plugin Author ryanhungate

    (@ryanhungate)

    @castlebuilder ok that’s great… but can you please confirm that the install went through and synced properly afterwords? I would hope the action scheduler issue is resolved as well for you.

    Thread Starter castlebuilder

    (@castlebuilder)

    Yes, upgraded to 2.7, and I can now see the settings, etc. that I could not before. It says that it is connected, do I need to completely resync? I’m not so far seeing any errors in the logs. We have not gotten a new order yet that seems like it would be best way to confirm. Is there another way to check? Thanks.

    Plugin Author ryanhungate

    (@ryanhungate)

    @castlebuilder we actually pushed up a small release to help with these issues. 2.7.1 if you can grab that. If you need to do a resync for any reason that’s fine of course.

    If you have any other issues please feel free to reach back out!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘API error after upgrade’ is closed to new replies.