Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter mayso1vn

    (@mayso1vn)

    I dont know, but i have fixed it successfully by your guideline document. Only the broken layout left

    Thread Starter mayso1vn

    (@mayso1vn)

    I hire an Agency to develop website and they set this to me by default which has license already active

    Thread Starter mayso1vn

    (@mayso1vn)

    Hi Gradient,

    Thank you for the previous support.

    As advised, I have removed the woocommerce_cart_hash cookie from the ‘Data dependencies groups’ settings on both of my sites.

    Unfortunately, this has introduced several critical bugs that break the entire shopping experience. The pages are fast, but the cart is now inconsistent and broken.

    Please review these issues carefully:Site 1: muamaymoc.com

    Problem: The Cart page (/cart/) is wrong items, but the Checkout page (/checkout/) is correct.

    Steps to Reproduce:

    1. I visit the site as a new user.
    2. I add a product to the cart.(it’s fast!, i love it)
    3. I go directly to the Checkout page (/checkout/).
    4. Result (Correct): The checkout page correctly shows the product I just added and the correct total.
    5. From there, I then navigate to the main Cart page (/cart/).
    6. Result (BUG): The cart page is wrong product.


    Site 2: mayso1vietnam.com

    Problem: This site has multiple, severe issues: broken layout, empty cart, and incorrect checkout.

    Steps to Reproduce:

    Bug A: Broken Layout on Initial Load

    1. I visit any optimized product page, for example: https://mayso1vietnam.com/san-pham/may-van-vit-dung-pin-bosch-gdr-120-li-12v/
    2. Result (BUG): The page layout is completely broken. This looks related to the “extra closing div” or CSS optimization issue I mentioned in my very first post.

    Bug B: Cart & Checkout Inconsistency

    1. While on the broken page (from Bug A), I click “Add to Cart”.
    2. Result: The layout instantly fixes itself (the page seems to reload dynamically). The mini-cart icon in the header also updates correctly.
    3. I then navigate to the main Cart page (https://mayso1vietnam.com/gio-hang/).
    4. Result (BUG): The cart page is empty. It says No products in the cart, even though the mini-cart icon was correct.
    5. I then navigate to the Checkout page (/thanh-toan/).
    6. Result (CRITICAL BUG): The checkout page shows a completely different, random product that I never added to my cart.

    This confirms my previous question: removing the woocommerce_cart_hash cookie may breaks the cart’s consistency. How can we fix this? We need a solution that provides both fast cached pages and a working, consistent cart across all pages.

    Thread Starter mayso1vn

    (@mayso1vn)

    Thank you, your support has been very helpful.

    I have tested removing the woocommerce_cart_hash cookie on my demo site, and the add-to-cart function seems to be working correctly (as you said, it’s handled by AJAX). I am installing the plugin on my live site again now.

    One last question: Regarding the first issue I mentioned in my original post about a broken layout (the ‘extra closing div’ I was investigating) — I will check this again after reinstalling. If the layout problem is still there, I will let you know.

    Thread Starter mayso1vn

    (@mayso1vn)

    Is your plugin fully compatible with Redis Object Cache, or are there any known conflicts?

    Thread Starter mayso1vn

    (@mayso1vn)

    OK, I understand the point about AJAX. The ‘Add to Cart’ action might work on the current page.

    But what happens when that user navigates to a different page, like the Homepage or another category page?

    If I remove woocommerce_cart_hash from the settings (as you suggested), won’t your plugin just serve the public static cache for the Homepage? This would make the mini-cart in the header show 0 items, even though the cart is not empty.

    Thread Starter mayso1vn

    (@mayso1vn)

    I checked the HTML you mentioned for the “extra closing div,” but everything looks fine in Chrome DevTools — no unmatched <div> found.
    Also, I removed the plugin after buy it because I noticed an odd behavior:
    When a page is in the optimized state, the first load is extremely fast (almost instant),
    but after adding a product to the cart or browsing other products, it becomes slow again — just like before optimization.

    It seems the plugin serves preloaded static cached pages, which explains the “fake” fast speed on the first load.

    Could you confirm if this is indeed how the caching works?Thanks.

Viewing 7 replies - 1 through 7 (of 7 total)