• webdesignbyh

    (@webdesignbyh)


    Hi,

    I’m using Product Configurator for WooCommerce on WooCommerce product pages and I’m trying to keep page caching enabled for performance.

    My stack:

    • WordPress + WooCommerce
    • Elementor / Elementor Pro
    • Product Configurator for WooCommerce (+ addons)
    • WP Rocket
    • Redis Object Cache
    • Varnish

    Issue

    If I exclude product pages from cache, the configurator works correctly but performance is much worse.

    If I allow product pages to be cached, performance improves significantly, but the configurator breaks and behaves incorrectly. What I tested

    I also tested JavaScript optimization in WP Rocket:

    • JS minify: on
    • JS combine: off
    • Delay JS execution: off
    • Defer JS: tested on and off

    The configurator still breaks when page cache is enabled, so it doesn’t seem to be caused by deferred JavaScript. Question

    Is full page caching on WooCommerce product pages supported with this plugin?

    If so, what is the recommended setup?
    For example:

    • specific cache exclusions
    • cookies or sessions that must bypass cache
    • AJAX endpoints that should not be cached

    My goal is to keep product pages cached for performance, while allowing the configurator to function correctly.

    Thanks!

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

Viewing 16 replies (of 16 total)
  • Plugin Contributor Marc Lacroix

    (@marcusig)

    Hi Tom,

    You may need to contact WP-Rocket’s support for this:
    The button color is Custom CSS which you added on your side, most likely via the customizer:

    /* maak de knop configurator groen*/
    .mkl_pc .mkl_pc_container button.configurator-add-to-cart, .mkl_pc .mkl_pc_container .mkl-pc--steps button {
    background: #21Ce57;
    border: 1px solid #21ce57;
    color: #FFF;
    font-size: 1rem;
    padding: 10px 25px;
    border-radius: 0;
    font-weight: 400;
    }

    Since mkl_pc is already excluded, I’m not sure what else could prevent this from being removed.
    You could still try adding wp-custom-css which is the handle for the custom CSS.

    Marc

Viewing 16 replies (of 16 total)

You must be logged in to reply to this topic.