Forum Replies Created

Viewing 15 replies - 1 through 15 (of 921 total)
  • Thread Starter Anthony Hortin

    (@ahortin)

    Hi Krystian,

    Thanks for the explanation. I think it’s still incredibly confusing for the end user though. These APMs should’ve been disabled by default, not enabled. This would’ve prevented all these unnecessary “Payment Gateway enabled” messages, that no doubt, a lot of people are going to be receiving as their plugin gets updated.

    Thread Starter Anthony Hortin

    (@ahortin)

    This seems like a huge issue with your plugin configuration then. Why are you explicitly opting people into payment gateways, and forcing them to “Opt-out”. I don’t even recall seeing any options in the previous UI about alternate payment gateways or being required to explicitly “Opt-Out” (instead of Opting-in).

    If these were previously enabled, unknowingly, then why do all the emails that I received tell me that the above Gateways were just enabled? Surely, if these options were already enabled as you’re saying, then why would I get any emails to say that something has changed?

    Thread Starter Anthony Hortin

    (@ahortin)

    Hi @kjvextras,

    Thanks for such a detailed response. I’ve added that filter into the Theme, so hopefully that preserves the Mailchimp status.

    One of the things you mentioned towards the top of your reply was that “Regardless of whether a customer selects the ‘subscribe to the newsletter’ option at checkout, if they abandon their cart, they will be synced with Mailchimp as Transactional”.

    While I’m all for adhering to email marketing regulations, this seems like the wrong approach. One of the steps that that we took recently, in order to try to to track down this issues and at the same time, also avoid the problem of people being accidentally unsubscribed, was to remove the “Subscribe” checkbox from the Checkout page. This means that we know for sure that people haven’t simply been unsubscribing as part of the checkout process (they can obviously still unsubscribe from the Newsletter though).

    Automatically marking someone as “Transactional”, which effectively unsubscribes them from marketing campaigns, simply because they abandon their cart seems wrong. There’s various reasons that someone would abandon their cart and I can’t see how this action would mean that you would also want to unsubscribe from marketing campaigns. I know myself, that I’ve added items to an online shopping cart before and then changed my mind. This didn’t mean that I also wanted to unsubscribe from their newsletters though.

    You also asked about the “Ongoing Sync” setting on the Audience tab. If you have a look at that screenshot I posted above for the Audience tab (https://share.zight.com/YEu2vEAe) you can see that there doesn’t appear to be any “Ongoing Sync” setting.

    We’ll keep an eye on things and hopefully that new Filter that you suggested, will stop people being unsubscribed.

    Thanks 🙂

    Thread Starter Anthony Hortin

    (@ahortin)

    Hi @jeremrm,

    I’ve finally tracked down the issue. After disabling plugins, the issue looks to have been caused by some custom code for defining Custom Post Types. More specifically, the name used for one of the Taxonomies.

    I’ll mark this as resolved.

    Thanks. 🙂

    Thread Starter Anthony Hortin

    (@ahortin)

    Hi @kjvextras,

    There’s no setting like that anywhere within the Plugin settings for Mailchimp for WooCommerce or within the WooCommerce settings.

    Here’s some screenshots of the settings pages for your plugin.

    Overview tab: https://share.zight.com/z8ujwgnj
    Store tab: https://share.zight.com/lluLwlyv
    Audience tab: https://share.zight.com/YEu2vEAe
    Advanced tab: https://share.zight.com/L1uAYwgm

    I’ve also updated to the latest versions of WooCommerce and Mailchimp for WooCommerce.

    Thread Starter Anthony Hortin

    (@ahortin)

    Hi @jaideeprm,

    With DEBUG turned on, this is the error that is displayed:

    Fatal error: Uncaught ArgumentCountError: Too few arguments to function RankMath\Admin\Post_Columns::taxonomy_columns_contents(), 2 passed in /***/public_html/wp-includes/class-wp-hook.php on line 341 and exactly 3 expected in /***/public_html/wp-content/plugins/seo-by-rank-math/includes/admin/class-post-columns.php:203
    Stack trace:
    #0 /***/public_html/wp-includes/class-wp-hook.php(341): RankMath\Admin\Post_Columns->taxonomy_columns_contents()
    #1 /***/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
    #2 /***/public_html/wp-includes/plugin.php(522): WP_Hook->do_action()
    #3 /***/public_html/wp-admin/includes/class-wp-media-list-table.php(714): do_action()
    #4 /***/public_html/wp-admin/includes/class-wp-list-table.php(1801): WP_Media_List_Table->column_default()
    #5 /***/public_html/wp-admin/includes/class-wp-media-list-table.php(747): WP_List_Table->single_row_columns()
    #6 /***/public_html/wp-admin/includes/class-wp-list-table.php(1711): WP_Media_List_Table->display_rows()
    #7 /***/public_html/wp-admin/includes/class-wp-list-table.php(1635): WP_List_Table->display_rows_or_placeholder()
    #8 /***/public_html/wp-admin/upload.php(457): WP_List_Table->display()
    #9 {main} thrown in /***/public_html/wp-content/plugins/seo-by-rank-math/includes/admin/class-post-columns.php on line 203
    Thread Starter Anthony Hortin

    (@ahortin)

    Hi @kjvextras,

    Apologies for my slow reply.

    You mentioned that the “subscriber status” being changed to “transactional” could be caused by a third-party integration. I would assume then, that this would also include something like WooCommerce?

    Looking at some more recent mailchimp_woocommerce logs, I can see the following for a particular user:

    2026-03-05T00:34:11+00:00 Notice order.member.updated :: Updated *****@hotmail.com subscriber status to transactional
    2026-03-05T00:34:11+00:00 Notice order_submit.success :: updateStoreOrder :: #+++++ :: email: *****@hotmail.com
    2026-03-05T00:38:38+00:00 Notice handleOrderUpdate :: order_status
    2026-03-05T00:38:38+00:00 Notice action_scheduler.queue_job :: MailChimp_WooCommerce_Single_Order starts in 90 seconds :: obj_id xxxxx with id 7954753
    2026-03-05T00:38:38+00:00 Notice debug :: Order ID xxxxx was processing and is now completed :: Array
    (
    [new_order] =>
    [tracking] =>
    )

    You can see that this log entry for a particular user, states “Updated <email_address> subscriber status to transactional”. If I read your reply correctly, then changing the subscriber status to “transactional”, would cause Mailchimp to reflect them as non-subscribed. Does this mean that it could actually be WooCommerce that is causing all these users to become Unsubscribed?

    Lastly, when I look at the mailchimp_woocommerce logs within WooCommerce, are these logs that are generated due to actions by the Mailchimp plugin, or from some action performed by WooCommerce?

    Thread Starter Anthony Hortin

    (@ahortin)

    Hi @kjvextras,

    Unfortunately not. This still seems to be an issue, and we can see that a number of users are still being unsubscribed from the Mailchimp account.

    One thing that I am curious about… in the Mailchimp Logs, I can see that for a few recent email accounts that were unsubscribed, the log states “Updated <email_address> subscriber status to transactional”.

    (<email_address> is obviously the email address of the user, which I didn’t want to post here)

    What does that actually mean? I would’ve thought that status would simply be “subscribed” or “unsubscribed”. What does a status of “transactional” mean?

    Thanks.

    Thread Starter Anthony Hortin

    (@ahortin)

    Hi @builtbyjordan

    Thanks for looking into this. I’ll go back and look into this a bit more and see what I can find out.

    Thanks.

    Thread Starter Anthony Hortin

    (@ahortin)

    Hi @builtbyjordan,

    I’ve just sent you that Customer email address, via your form.

    Thanks,
    Anthony.

    Thread Starter Anthony Hortin

    (@ahortin)

    Hi @builtbyjordan,

    I’ve just submitted that form with some details.
    Thanks.

    Thread Starter Anthony Hortin

    (@ahortin)

    Thanks for the reply. If you need any further info, just let me know.

    Thread Starter Anthony Hortin

    (@ahortin)

    Thanks Jamie. I’ve just used the Manual option and that worked much easier, and was a lot less messing around.

    Just as a note for anyone else having issues connecting to the PayPal Sandbox…

    • Login to your PayPal Developer account (https://developer.paypal.com)
    • On the homepage of your account, ensure Sandbox is selected in the top-left corner of the screen.
    • Click on Apps & Credentials in the left-hand menu
    • Click the Create App button to create a new REST API app
    • Copy the Client ID and Secret key 1 API keys that are generated
    • Back in your WordPress site, on the Payments tab within the WooCommerce > Settings screen, click the button to edit the PayPal settings
    • Scroll down to the Advanced Option towards the bottom of the page and select Manually Connect and then enter in the above API Keys you copied from your PayPal Developer page.
    • Save your settings and you should then be connected once the page refreshes
    Thread Starter Anthony Hortin

    (@ahortin)

    Hi Jamie,

    Thanks for the reply. I’m aware of the ‘Advanced Options’. I mentioned in my original post…

    When I go to the PayPal settings I scroll down to the Advanced settings and click Connect Account. This then redirects me to the PayPal sandbox site. After logging in, it tells me that me I’m “Ready to get paid with PaPal” and then simply gives me a button to return to my site.

    As I mentioned, clicking the Connect button simply takes me to a PayPal screen (https://share.zight.com/yAumjkLw), which then just has a button that returns me back to my website. The PayPal Sandbox doesn’t get connected, I then keep getting prompted to ‘Complete Setup’ which then just takes me back to the PayPal settings page again, where I have to click the Connect Account button again. Then it all repeats and I get nowhere.

    Thread Starter Anthony Hortin

    (@ahortin)

    Ahh thanks for that. Looks like that issue was raised almost 4 years ago. I guess I shouldn’t hold my breath for a fix. I appreciate the quick reply. Thanks 🙂

Viewing 15 replies - 1 through 15 (of 921 total)