• Good morning,
    Today I have updated to Woocommerce 9.7.1 and when a user tries to make a purchase with their default address on the checkout page, the message “no shipping method available” appears. For it to work and for the system to detect the address and therefore display a shipping method, the user has to slightly modify the “street address” field. Once the user has slightly modified that field, the system detects the address and applies the corresponding shipping cost. Is this a defect in the update? Could you please solve this problem? When a customer accesses the website and their default address appears, the message “no shipping methods available” should not appear since they have previously purchased with that address and there were no problems. Thank you very much.

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

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    Thanks for your message!

    Could you please confirm if this issue is happening for logged-in users with saved addresses, or does it also happen for guest users during checkout?

    I’ve tested this on my own site using WooCommerce 9.7.1, but I wasn’t able to replicate the issue — the correct shipping methods appear without needing to change any fields.

    Also, I’d like to understand your site properly, could you please share the System Status Report?which you can find via WooCommerce > Status, please use?https://pastebin.com/?or?https://gist.github.com/ and share a link to that paste in reply here. Once we have more information, we’ll be able to assist you further.?????????

    Thread Starter fcbaena

    (@fcbaena)

    Hi,
    I finally rolled back the Woocommerce update and I still have the problem. It is an issue with logged in users with saved addresses, not with guest users.
    Here is the link (https://pastebin.com/5GkV0niF) to the paste file with the Woocommerce status information, which has the following password to access it (744g9TAV7B).
    Thanks!

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    If rolling back doesn’t work, that indicates the issue is likely not related to the WooCommerce update.

    However, I’m unable to access the Pastebin report — it’s asking me to log in with the correct email address. Could you please remove the privacy restriction so we can access the system status report?

    In the meantime, I’d recommend running a conflict test by deactivating all plugins except WooCommerce, then checking if the issue persists. For more details you can use this article.
    https://woo.com/document/how-to-test-for-conflicts/

    Once we have the system status report and test results, we’ll be happy to assist you further.

    Thread Starter fcbaena

    (@fcbaena)

    Hi there,
    Thank you very much for your help. I will take your advice into account when detecting the incompatible plugin.
    On the other hand, you should now be able to view the file in Paste. It is now public (https://pastebin.com/5GkV0niF)
    I look forward to hearing from you, thanks again.

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    I have checked the system status report. First, I would suggest upgrading WooCommerce to the latest version again. Then, try deactivating the following plugins:

    • WC Hide Shipping Methods
    • Flexible Shipping
    • WooCommerce Multilingual & Multicurrency
    • Autoptimize
    • WP Rocket
    • Country Based Payments for WooCommerce

    If you still face the same issue, try deactivating the remaining plugins as well. Let me know how that goes.

    Thread Starter fcbaena

    (@fcbaena)

    Hi!

    Thank you for your response and suggestions. As you recommended, I have upgraded WooCommerce to the latest version and proceeded to deactivate the plugins. After deactivating the plugins, I thoroughly tested the checkout page, but unfortunately, I was still unable to reproduce the error message.

    To further investigate, I created a clone of my website for testing purposes. To my surprise, on the cloned site, the error does not appear at all, even with all plugins and the theme active. This difference in behavior between the live site and the cloned site is puzzling.

    Given these results, I have a few questions:

    • What could be the potential reasons for the error to disappear on the cloned site without any changes to plugins or the theme?
    • Are there any other troubleshooting steps you would recommend, considering that the issue is proving difficult to reproduce?

    Thank you!

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there,

    Thank you for providing an update and for your thorough testing. Based on your feedback, it’s clear that the issue is difficult to reproduce on the cloned site, which is puzzling. Here are some potential reasons for the discrepancy and further troubleshooting steps:

    Caching Issues (Server or Browser)

    • Server-side caching might be affecting the live site. Some hosting providers implement caching systems that can interfere with live updates, especially for dynamic pages like checkout. Also try to deactivate all cache plugin like wo rocket and see if that resolve the issue.

    Test with a New User Account

    • Sometimes, user-specific data or settings can interfere with checkout. Create a new user account and try placing an order from the live site to see if the error persists.


      Let me know how thot goes.
Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.