webdesignbyh
Forum Replies Created
-
Hi Marc,
Thanks for your suggestion. The class mkl_pc is already included in the safelist on our side, but unfortunately the issue with the button styling still occurs occasionally.
Do you have any other suggestions on what might be causing this or which CSS might still be excluded?
Thanks again for your help!
Tom
Hi Marc,
Apologies for the previous two messages. I’m still noticing that the “Next” and “Add to my cart” buttons in the configurator sometimes lose their styling and appear black instead of green. It seems their CSS might still be removed somewhere in the optimization. I’m currently looking into which CSS class needs to be excluded to preserve that layout.
I think I fixed it! Thank you for all your help!
Hi Marc,
One thing I still notice is that the buttons inside the configurator appear black instead of green. These are the “Next” and “Add to my cart” buttons. It looks like their styling is still being removed somewhere in the optimization process. Do you happen to know which CSS exception for the configurator might be needed for these buttons?
Hi Marc,
I added the exclusions you suggested and also included the two additional WooCommerce exceptions (
wc-cart-fragmentsandwc-add-to-cart). After clearing the cache, everything now seems to work correctly on my side.I did have to add a few additional CSS and JavaScript exclusions, because the cart was updating a bit too late and some buttons inside the configurator lost their styling and turned black instead of green.
It looks like it’s working now, could you verify if you experience the same behavior?
Thanks again for your help.
Best,
TomHi Marc,
Thanks for the explanation, I completely understand your approach now and I appreciate you guiding me through it step by step.
After adding the latest exclusions, the configurator now opens on the test product, which is great. I think we’re close!
However, the layout still looks different compared to the normal configurator. For example, the buttons look different and there is now a “sluiten” (closing) button visible that normally should not be there.
You can see the current behaviour here:
https://www.onlinekozijnenhuys.nl/product/testing-kunststof-kozijn/And here is another product page where caching is still disabled, where the configurator appears with the correct layout:
https://www.onlinekozijnenhuys.nl/product/vast-glas-kunststof-kozijn/Could you possibly see what might be causing this layout difference?
Thank you! Tom
Hi Marc,
I added the exclusions in WP Rocket under “Load JavaScript deferred → Excluded JavaScript files.”
I excluded the configurator plugins and the dependencies you mentioned:
woocommerce-mkl-pc
product-configurator
jquery
underscore
backboneAfter clearing the WP Rocket cache and flushing the object cache, the configurator on the test product still does not initialise correctly.
Test page:
https://www.onlinekozijnenhuys.nl/product/testing-kunststof-kozijn/Is there a next step we should try?
Thank you! TomHi Marc,
Thank you! I added the exclusions for the configurator scripts in WP Rocket → File Optimization → “Excluded JavaScript files” under “Load JavaScript deferred.”
I first tried excluding the full plugin paths:
wp-content/plugins/woocommerce-mkl-pc/
wp-content/plugins/product-configurator-for-woocommerce/After that I also tried a second method using keywords, as WP Rocket sometimes matches better that way:
woocommerce-mkl-pc
product-configuratorHowever, the result now is that the configurator button on the test product no longer responds / does not start the configurator.
Test product:
https://www.onlinekozijnenhuys.nl/product/testing-kunststof-kozijn/So at the moment the scripts are excluded from defer, but the configurator still does not initialise correctly.
Best regards,
TomHi Marc,
Thanks for your reply.
I’ve created a test product where the issue can be reproduced:
https://www.onlinekozijnenhuys.nl/product/testing-kunststof-kozijn/
On the rest of the website I currently exclude product pages from cache, because otherwise the configurator breaks. When product pages are excluded from cache, everything works normally again.
For this test product, I have temporarily enabled caching, so the issue can be observed on that page.
Best regards,
Tom