conorseed

@somersby – you legend. Going back to 5.0.4 works. Thanks heaps for that fix!

For reference @ionutn – both 5.0.7 and 5.0.8 didn’t work. I’m running WP 6.7 on Cloudways. Not marking as resolved yet as the latest versions don’t seem to work as expected.

@ionutn – thanks for confirming it’s working on your end! Can you tell me – if there is a cache clear on post update, should that show in the logs? If so, what do the logs looks like for that?
I’ll have another play on my end and see if I can get to the bottom of it once you’ve confirmed the above.

Hey @oluirael, Just popping by to say I had the exact same issue. Thanks for the patch file above – it fixed the issue. However, if you could PLEASE release the patch as an update to the plugin that would be greatly appreciated. It’s not ideal to have to come to the support forum and manually install a patch, a month after the issue was brought to your attention. Thanks ??

Hey @qtwrk – apologies for not being more specific.
I was going to attach an image but must have forgotten!

Here’s a screenshot of the console with all the errors with ESI enabled:
https://drive.google.com/file/d/1ax6cVpNVFEAZDQKSmH4V59N97HcBY8Iz/view?usp=sharing

As mentioned above, when ESI is disabled these errors don’t exist.

Hey @churious , I’m wanting to achieve the same thing. Did you manage to get this sorted? ??

Hey Thomas (@webzunft),

Thanks for the quick response. I had totally missed the import & export functionality!

It makes sense but its not ideal ?? Guess it’d be easier to use if it were .csv instead of .xml. But that’s ok, I can setup a spreadsheet for the client to fill out and convert to xml.

Thanks again for your help ??

Hey @iberezansky,

I’d also love to be able to go straight to full screen instead of into the lightbox. Can you point in the right direction with the JS? I’m happy to code, just need direction. Thanks.

There we go! And we have a winner ?? Officially resolved now!

Thanks again for all the help.

Brilliant response – thank you @lclarke. That helps me immensely.

I think I know what I’m doing now. Thanks to both of you for being patient with me and answering my (probably very noob) questions!

One last one for you: I’m probably missing something but is there a way I can set a TTL for the ESI block? Or do I have to manage that in the general settings somewhere?

@hailite Thanks for the response.

I thought no cache would be the best option in terms of making sure the block always shows the most recent information. It is linked into a booking system via API: it shows upcoming courses, as well as how many spots are left on each course.

Currently (even with the esi block set to “no-cache”), the whole page is cached. Which means it’s outdated after an hour – often showing the wrong number of spots left, or a course which is no longer available to book.

If I set it to “private”, will the block always show the most recent info for ANY user (logged in or not)?

• This reply was modified 6 years, 7 months ago by conorseed.

Ok, so I found in the documentation to set the below but it’s still caching the block in the public cache. Any ideas?

LiteSpeed_Cache_API::esi_url($block_id, $wrapper, $params = array(), $control = 'private,no-vary')

Set $control = 'no-cache' to set the ESI block as non-cacheable.

That makes sense now thank you! ?? I got it working by using the `after_setup_theme’ action as you suggested.

I do have another question though: does an ESI block load fresh every time, even for logged out users?

Sorry @hailite, I don’t quite understand. Can you expand on that please?

Hey, I get the below error. How do I include the api in my plugin? ??

Uncaught Error: Class 'LiteSpeed_Cache_API' not found in path/to/my/plugin

Ok thanks! I’ll give it a go and come back if I have any issues ??