arithdevlpr

In my CSS and JS excludes i have

/wp-content/plugins/b2b/woocommerce-request-a-quote/assets/css/(.*).css

/wp-content/plugins/b2b/woocommerce-request-a-quote/assets/js/(.*).js

I’ve added the snippet you provided, cleared all cache, and oh wow it works now after a small few seconds of delay. Thank you!. just out of curiousity what do you think was the issue?

Yes if the product page is set to Do Not Cache, the add to quote will work just fine. but if i do cache the product pages, the add to quote breaks.

Were you able to also try add to quote for the https://rifftsafety.co.nz/product/hiviz-x-back-vest-transit-orange/ page which is cached?

There are other threads on the subject around too but it seems to be a case by case and in my case even after adding the full url to the css files/folders i want to exclude it still doesnt seem to be working when the page is cached.

Is there a way to tell if an element/css/js file has been properly excluded from being cached?

Try and add to quote. For reference on this product page i’ve force disabled cache so you can see the functionality. :https://rifftsafety.co.nz/product/10l-diesel-jerry-can/

The thing is the add to cart button is woocommerce direct but the add to quote is generated by another plugin – B2B by Addify.

As per the other thread the guy’s workaround was to:

Normally without any optimization Add to cart is done using AJAX without reloading. But with Litespeed optimization, it reloads the page.

So I just needed the names of the files responsible for this Add to cart functionality.

Anyway, I figured it out.

Excluded add-to-cart.css and my cart plugin CSS files from all optimization. It’s working now!

but i’m not entirely sure how or where to try and add this exclusion as it relates to the specific plugin I am using

oh yes sorry i disabled cache for ^/product/ pages so it works but ideally i want to enable cache to further speed things since i have about 2000 product pages.

I’ve just enabled it now so if you refresh and try again you’ll see what i mean

@maykato ‘s reply about checking my endpoints helped me resolve my issue after updating to the most recent version of woo and elementor ( woocommerce version 6.7.0, and elementor/pro (3.6.7/3.7.2)

thank you for your prompt response! i have contacted the other developers. hopefully they will fix it.

sadly i need Elementor as it is my page builder i use.

Thanks