Error cache litespeed

  • gesbyte

    (@gesbyte)


    10 months, 1 week ago

    Hello, I’ve been thinking for a few days, I’ve tried excluding by categories of entries, by pages, and by code in functions.php, nothing works for me, I only found out that it updates when I purge css/js. It’s a plugin that, although LiteSpeed should purge when it detects changes, this specific booking plugin seems incompatible. The pages where shortcodes appear are created with Divi Builder in case this information helps. The issue is that the seats with pending or accepted reservations should be marked, but since the cache for the shortcode or the page is not being cleared, the changes do not show up and visitors can’t see what is already reserved until they receive an error. How can I exclude it or make it auto-purge upon change? I don’t care as long as when I reserve, if I refresh, it appears marked as occupied.

    I I first asked Litespeed support and this was their response:

    I think you need to check with SeatReg plugin support , and kindly ask if there is any action in their plugin fired when seat is taken , then we can hook it to the cache purge API to purge it when seat is taken to reflect the changes in page.

    Alternatively, a method to exclude, I believe would work, since I have tried everything that came to mind from the Litespeed configuration in blackoffice, such as PHP, parameters in the configuration files.

    It’s quite a serious problem and I am stuck.

    • This topic was modified 10 months, 1 week ago by gesbyte.
    • This topic was modified 10 months, 1 week ago by gesbyte.

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Siim Kirjanen

    (@thesiim)

    10 months, 1 week ago

    Hello
    This plugin should trigger couple of actions you can use to clear the cache.

    seatreg_action_booking_submitted
    Triggered when booking is submitted with registration page. Gets booking ID as parameter.

    seatreg_action_booking_manually_added
    Triggered when booking is added with booking manager. Gets booking ID as parameter.

    seatreg_action_booking_pending
    Triggered when booking gets pending status. Gets booking ID as parameter.

    seatreg_action_booking_approved
    Triggered when booking gets approved status. Gets booking ID as parameter.

    seatreg_action_booking_removed Triggered when booking gets removed. Gets booking ID as parameter.

    I hope this will help.

    Thread Starter gesbyte

    (@gesbyte)

    10 months, 1 week ago

    but what is booking ID in this context ?

    Plugin Author Siim Kirjanen

    (@thesiim)

    10 months, 1 week ago

    Its the booking_id column of the seatreg_bookings table.

    Thread Starter gesbyte

    (@gesbyte)

    10 months ago

    I know what the booking ID is, what I’m asking is how the trigger helps me clear the cache and what does the ID obtained from the trigger have to do with it?

    Plugin Author Siim Kirjanen

    (@thesiim)

    10 months ago

    I’m not familiar with LiteSpeed Cache, but based on the information, I suppose you need to call the LiteSpeed Cache purge API when SeatReg actions are triggered? You likely don’t need to use the booking ID unless it’s specifically required.

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

The topic ‘Error cache litespeed’ is closed to new replies.

Tags