• Resolved ardennesplaques

    (@ardennesplaques)


    Hello,

    We are currently experiencing a login issue on our website since implementing your plugin. While we’ve been impressed with the improved speed—so much so that we replaced LiteSpeed Cache with your solution—we’ve noticed that most users, including administrators, must attempt to log in 3–4 times before it succeeds.

    Here’s what we’ve tried so far to resolve the issue:

    • Added all possible variations of the account page URL to the “Prevent the following URIs from being cached” setting.
    • Enabled “Don’t cache the following WooCommerce page types” and selected the My Account page (is_account) option, as recommended.

    Please note that our account page URL is not the default but the French version: “mon-compte”.

    Could you kindly assist us in identifying the cause and resolving this issue?

    Thank you for your support, and please let us know if you require additional information.

    Best regards,

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

Viewing 1 replies (of 1 total)
  • Plugin Support Kush

    (@kushnamdev)

    Dear @ardennesplaques,

    Thank you for reaching out and sharing the details of the issue you’re experiencing. I understand how frustrating it can be to encounter login challenges. Let’s address the problem step by step.

    From the steps you’ve already taken, it’s clear you’re familiar with the plugin’s caching settings. However, the issue likely lies in how caching interacts with session management or WooCommerce’s account-related pages.

    Please try the following:

    1- Ensure Full Exclusion of the Account Page URL: Try to Use wildcard patterns (/mon-compte*) or Add the exact URL (/mon-compte) and any variations that could appear, such as /mon-compte/

    2 – Cookie exclusion: Under the option Bypass Page cache when these cookies are present in the request packet, you can add WooCommerce-specific cookies such as –

    woocommerce_

    wp_woocommerce_session_

    3- Clear Cache Thoroughly: After making any changes, clear both the plugin cache and your server-level cache (if applicable). This ensures the new settings take effect.

    Please let us know if this solves your issue.

    Best regards

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.