Simon

Hey @juzzyjayy !

Thanks so much for all the detail here, it’s super helpful! As Order Bumps is part of our premium plugin features, and not the lite plugin on ww.wp.xz.cn, you’ll need to submit the query through your checkoutwc.com account instead.

The good news is that I’ve tested this locally based on the details you provided, I am seeing something similar on my test site too. I’ll pass this over to our engineering team to take a closer look at, but if you’d like to be kept in the loop then please do contact us through your premium account directly.

Cheers!

Hey @djwilko12,

My name’s Simon from the CheckoutWC support team. Thanks for reaching out about this issue!

Typically CheckoutWC should work with most plugins out of the box, as it mimics the same behavior as the standard (non-blocks) WooCommerce checkout. However, every now and then, there can be conflicts with some plugins, especially if you’re using multi step checkout and the plugin is expecting a single page layout.

That said, we’re happy to take a closer look and see if it’s possible to find a workaround for you! Usually to do this we would require looking at the site directly, and sometimes asking for settings/screenshots. In order to do this in a more private fashion, could you email us at [email protected] or drop us a line on https://www.checkoutwc.com/support/ and mention this thread?

We can then take a closer look with you to see what we can find. If you’d prefer to carry on here instead, then no worries, just let me know!

Cheers,

Hey @sip24 ,

Simon here from the CheckoutWC engineering team, I’m happy to help. I took a look at the code and can see that it might throw that error if that property is not set.

I’ve added a tweak that should avoid this error logging in the future, though for now it shouldn’t effect the behavior of the plugin. The fix will be included in our next release, thanks so much for letting us know!

Is there anything else I can help you with today?

Cheers,

Hey @lands23!

Thanks for getting back to us. The best place to start with your custom snippet would be to add a shortcode that receives a product_id or retrieves the post/product_id of the page it’s used on.

This is because our custom tab data is stored as product metadata, so you will need to grab the produce first. The meta key in question is then: “frs_woo_product_tabs” and this will contain an array with ‘title‘, ‘id‘, and ‘content‘ values.

Hopefully this puts you on the right track to being to integrate into Elementor! If you need further assistance with the custom development, I’d be happy to recommend some developers experienced with WooCommerce, just let me know.

Is there anything else I can help out with today?

Cheers,

Simon.

Hey @keithhill1968,

Great stuff! Thanks for keeping me in the loop. If there’s anything else I can help with, or if they have any suggestions for us, please don’t hesitate to reach out!

Cheers,

Simon.

Hi @keithhill1968,

Thanks for reaching out and thanks so much for sharing that log snippet, that’s very useful!

It looks like our Braintree Gateway is checking if Apple Pay should be initiated on ‘init’, which eventually works it’s way through the code to the External_Checkout code. Here it’s confirming what payment gateways are available by calling ‘woocommerce_available_payment_gateways‘ which the WC_Gateway_Afterpay then seems to jump onto.

Here, the Afterpay gateway looks to be calling the get_cart() function which is generating the error.

To confirm I’m reading this correctly, can you let me know if you’re also running the Afterpay gateway on your site? If so, has this only occurred since upgrading either Braintree or have you also upgraded Afterpay recently too?

Cheers!

Simon.

Hey @oxhey,

It has been a while since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Thanks,
Simon.