• Resolved lbackstrom

    (@lbackstrom)


    I just started my first auction. Since auctions are dynamic, are there any issues I should be aware of when using the OpenLiteSpeed web server with LiteSpeed Cache and a CDN on AWS CloudFront?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Nitesh

    (@nitesh_singh)

    Hello @lbackstrom,

    The Ultimate Auction for Woocommerce plugin works with it. However we do not recommend a cache plugin for users relying on auction functionality.

    The plugin depends on real-time updates for auction elements such as product prices, countdown timers, and bid data. These updates must occur instantly to ensure the accuracy and reliability of the auction system.

    Cache plugins can interfere with this real-time functionality by optimizing or caching dynamic auction components, such as JavaScript for timers. For example, if a caching plugin optimizes or caches the auction timer, it may cause the timer to malfunction, leading to discrepancies. This is just one of many potential issues that could arise.

    To ensure the best performance and seamless operation of the Ultimate Auction for WooCommerce plugin, we strongly recommend avoiding the use of cache plugins. The plugin is specifically designed to function optimally without caching.

    AWS CloudFront can work with an auction-based WordPress site. Auctions involve dynamic and time-sensitive content, so your setup should balance performance (caching) with real-time responsiveness.

    Thank You

    • This reply was modified 1 day, 5 hours ago by Nitesh.
    • This reply was modified 1 day, 5 hours ago by Nitesh.
    Thread Starter lbackstrom

    (@lbackstrom)

    Based on your previous response and given the dynamic nature of an auction, it seems that using a Redis object cache can cause issues, especially with real-time updates like product prices, countdown timers, and bid data. While I understand that adjusting TTL or invalidation rules might help, I believe caching these dynamic elements could interfere with the auction functionality by using stale data.

    I think it goes without saying, you would recommend disabling the Redis object cache entirely to avoid potential issues?

    Thanks in advanced,

    Plugin Author Nitesh

    (@nitesh_singh)

    Hello @lbackstrom,

    Thank you for your question. You are absolutely correct that using a Redis object cache can sometimes lead to issues with dynamic, real-time elements of an auction, such as product prices, countdown timers, and bid updates. These features require instantaneous updates to ensure accurate data is displayed at all times.

    To avoid these issues entirely, we recommend disabling Redis object caching for all woocommerce pages like shop page, auction shortcode pages, product detail page, category page, cart page, checkout page etc. It includes auction-related pages. If your Redis setup supports it, you can also configure cache exclusions specifically for these woocommerce pages, rather than disabling Redis across your entire site.

    If there is no option to exclude specific pages from caching, you will need to disable caching entirely on your site.

    Thank You

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