(Enquiry) Checkout Error – Problem was the customer’s name

  • Resolved firdauskotp

    (@firdauskotp)


    3 months ago

    Hello team,

    We had a customer from Taiwan. However, she was not able to go to the checkout page of the website. She received this error:

    WPOrg\Requests\Transport(\Curl_request) ( I want to put the picture but it is loading infinitely :/)

    After debugging, I noticed that the error was her name. When she used English characters, she had no problem placing an order.

    My question is, does woocommerce support other language characters for the name or is it English only for now?

    Thank you in advance

    Sincerely,

    Firdaus

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @firdauskotp

    Yes, WooCommerce does support non-English characters. It is designed to be used globally and therefore supports many languages, including those that use non-English characters.

    For better assistance, can you provide screenshots showing the issue on your end? For screenshots, I recommend https://snipboard.io/ for easily sharing screenshots – please follow the instructions on the page, then paste the URL(s) in your reply.

    In the meantime, you can run a conflict test to help you identify the cause of the issue. More info: https://woocommerce.com/document/how-to-test-for-conflicts/

    Looking forward to hearing from you!

    Thread Starter firdauskotp

    (@firdauskotp)

    Hello Shaheem,

    Thank you again for your swift response. Here is the screenshot of the error

    https://snipboard.io/pHIU9A.jpg

    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @firdauskotp

    Thanks for sharing the screenshot. It looks like a curl request related issue. One of your plugins might conflict or fail while requesting a particular library. The best way to determine this is to:

    • Temporarily switch your theme to Storefront or Twenty Twenty-Four
    • Disable all plugins except for WooCommerce
    • Repeat the action that is causing the problem

    If you do not see the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

    I hope that helps! Let me know once you have done a conflict test!

    Thread Starter firdauskotp

    (@firdauskotp)

    Thank you Shameem,

    I think the issues was with one of the language plugins. I have over 80 plugins, 40 used 40 deactivated. I’ll check by them again. I might run a conflict test late on because for these few days the system is live due to a live event. If I manage to detect the problem after the live event, I will let you know immediately.

    Once again, thank you for your swift response.

    Sincerely,

    Firdaus

    Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello firdauskotp,

    Thank you for your reply.

    I think the issues was with one of the language plugins.

    To confirm, were you able to resolve the issue with the conflict test?

    Yes, of course. Take your time and perform further troubleshooting when it is feasible.
    We are here for your support round the clock. ??

    Have a great day!

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