Undefined array key checkout_layout

Hey @goasklecom!

Thanks for the tip about turning off Elementor experiments and tweaking the display_errors setting. I’ve already tried disabling Elementor’s experiments, but the issue persists (Im not using any of them at the moment also).

My best guess is that the plugin is calling Elementor’s Conditions API on the front end without providing a default for checkout_layout. Hiding the warning feels like sweeping it under the rug, and I’d rather tackle the root cause. Could you take another look at how the plugin hooks into Elementor conditions and suggest a way to either supply a fallback for checkout_layout or limit that integration to the editor/order-received context?

Really appreciate any guidance you can share. Let me know if you need logs or want me to try anything else!

it’s just a warning anyway, and I am doing a couple of cleanups, so no rush at all!

First, thanks for all the work you’ve put into this plugin… it’s been a huge help! I dug into the code and saw you’re using both the Store API hook (woocommerce_store_api_checkout_order_processed) and the standard checkout hook (woocommerce_checkout_order_created) in addition to woocommerce_thankyou and woocommerce_view_order.

Perhaps, firing the QR code generation so early in the checkout flow is unintentionally triggering Elementor’s conditions logic on the checkout page, which leads to that “Undefined array key ‘checkout_layout’” warning from Elementor.

I suspect if the QR code ran only after the order is complete (for example, on the thank-you or order-view pages), the warning would stop appearing without “waking up” the elementor’s conditional thing.

Perhaps just //commenting those hooks will prevent them from running too early, not sure if it will affect other instances also, but I can try it later on if this makes sense to you!

Thanks again