We have an exclusive feature ESI to solve this compatibility issue perfectly.
Please take a look at https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscwp:esi_replace
Basically, to make token still valid, it is possible to keep cache TTL as long as you want, even 1 year. Just punch a hole for that token and make its TTL 10 hours only.
Thread Starter
dmsims
(@dmsims)
Thanks for the replies
I don’t think the first solution is sustainable: if Caldera do a plugin update the changes could be overwritten
Will take a look at the shortcode
Plugin Support
qtwrk
(@qtwrk)
Hi,
How is your shortcode test ?
from github history , caldera is already compatible with LSCWP since 1.5.6.2
Have you enabled ESI ?
Best regards,
Thread Starter
dmsims
(@dmsims)
Okay so slightly confused at this point!
Changing the global cache timeout did not work, I had to deactivate the plugin
With ESI
is it just a question of enabling it in the plugin options or do you have to use the shortcode as well ?
Caldera Form has our ESI API embedded. For the nonce it will automatically generate a separate cache. If you have ESI turned on, it will use your Default Private Cache TTL setting for that nonce caching. By default Default Private Cache TTL is 1800, it won’t get expired.
For most other plugins, @qtwrk’s answer (ESI shortcode) is a general approach to fix the timeout issue. For Caldera Form, it’s not needed.
Also, we currently improved the compatibility with Caldera Form in Gutenberg. If you are using WP5, you may want to give it (https://github.com/litespeedtech/lscache_wp/archive/master.zip) a try or wait for LSCWP v2.9.4 release.
Please share a report number if you still have this issue.
