• Resolved tboy123

    (@tboy123)


    I noticed recently that when customers make a purchase, it is triggering several different functions that I have for a newly registered user, such as emails, webhooks, etc.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello tboy123,

    Thank you for contacting WooCommerce support.

    I understand that customer purchases are triggering functions meant for newly registered users, such as emails and webhooks.

    Could you share screenshots of the triggered emails and webhooks?
    This will help me understand the issue better.

    Also, when did this issue first start?
    Did you make any changes to the website that might have triggered this issue?

    Once I have more details, I’ll be able to assist you better. ??

    Best regards.

    Thread Starter tboy123

    (@tboy123)

    It started sometime between Oct 6 and 14. I have not made any significant changes to the website, such as adding or subtracting plugins.

    I’m not sure screenshots would be helpful, but I can tell you everything that is being triggered:

    • Miniorange API, triggers that a new user registered
    • WP Webhooks, triggers that a new user registered
    • User Registration, sends me an email that someone registered an account

    I have a a Webhook in Woocommerce that triggers when an order is updated, but that has never previously triggered the new user registered functions.

    Plugin Support EastOfWest a11n

    (@eastofwest)

    Hi @tboy123, thanks for the additional details. It sounds like you’re using custom code on your site, is that correct?

    If it is, can you temporarily disable or remove the code, and then complete an order to see if the issue still persists? If the issue goes away, then you’ll need to audit the custom code or ask the developer that created it to inspect it to see why it behaves differently.

    Even if no overt changes were made, plugins and themes constantly roll out new versions, and with it can come new ways to do things, that may not have existed when the custom code was created. Developers usually avoid this scenario by staying up to speed via our Developer Resources (Stay updated).

    Let us know if the above helps, or if you need further assistance.

    Thread Starter tboy123

    (@tboy123)

    I am using some, but this is the only one related to woocommerce:

    function sv_link_orders_at_registration( $user_id ) {
    wc_update_new_customer_past_orders( $user_id );
    }
    add_action( ‘woocommerce_created_customer’, ‘sv_link_orders_at_registration’ );

    Would that do it?

    Thread Starter tboy123

    (@tboy123)

    To be clear, that was added nearly 2 years ago without issue.

    Thread Starter tboy123

    (@tboy123)

    Tried it with that code disabled, still had the same problem

    Plugin Support EastOfWest a11n

    (@eastofwest)

    Thanks for trying, @tboy123! I’m not finding similar issues that exist with just WooCommerce and a standard theme active, so it seems something else on your site is misbehaving. The next step, and the best way to figure out what that something is, is to do a conflict test. Our How to Test for Plugin and Theme Conflicts guide explains how to do it.

    Start with a good backup of your site and, if at all possible, set up a staging site. Verify that you can recreate the issue on the staging site as well, then run the conflict test there, instead of your live site.

    Let us know what you find.

    Thread Starter tboy123

    (@tboy123)

    It was an issue with another plugin. Thank you for the help!

    Plugin Support Beauty of Code (woo-hc)

    (@beautyofcode)

    Hey @tboy123 ,

    Glad to hear you’ve managed to find the culprit! I’ll go ahead and mark this as resolved then, feel free to create a new topic if you need any further help. ??

    Cheers.

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.