• Resolved mystorynorge

    (@mystorynorge)


    On the checkout page, after having filled out all the required information and submitting it we recieve this message:

    The Kustom order id could not be retrieved from the session. Please try again.

    In the Woocommerce logs for this plugin we are seeing lots of these messages:

    Missing WC session kco_wc_order_id during update Kustom order sequence.

    And these messages are shown when we try to go through the checkout:

    [CHECKOUT VALIDATION]: Kustom order ID is not set in the session. Will not proceed with order.

    For now we have had to fall back on the Vipps Checkout extension, so that we can continue to process orders as normal.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • robinkrokedil

    (@robinkrokedil)

    Hi,

    Thanks for the report, and sorry for the trouble.
    To look into this we need your logs and some details about your store setup, which isn’t suitable to share in a public forum. Could you send the case to us directly via https://krokedil.com/support/ ?
    We’ll follow up here in the thread once we know what’s causing it, so others who see the same messages can find the outcome.

    robinkrokedil

    (@robinkrokedil)

    Following up as promised. The cause was the checkout page itself: it used the [vipps_checkout] shortcode instead of [woocommerce_checkout].

    Kustom Checkout works by replacing WooCommerce’s form-checkout.php template, so with neither the WooCommerce checkout shortcode nor the checkout block on the page, the checkout never renders – no Kustom order is created, nothing is stored in the session, and submitting the order produces exactly those log entries.

    Thread Starter mystorynorge

    (@mystorynorge)

    Correction: The cause was the builtin Avada woocommerce checkout block on the checkout page.

    After changing this to the [woocommerce_checkout] shortcode everything started working correctly.

    The [vipps_checkout] shortcode was only used on a separate subpage we created as a temporary solution while this issue was investigated.

    • This reply was modified 3 weeks, 4 days ago by mystorynorge.
Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.