• Hi, I have a problem-there was a conflict with the LiteSpeed Cache caching plugin after the last update of the cluevo plugin. Do you know anything about this?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author CLUEVO

    (@cluevo)

    Hi Portass,

    what exactly is the problem? It seems these caching plugins often cause problems. Some issues we can address, like js conflicts but other things like plugins caching frontend pages that use stale permissions are harder to fix.

    Thread Starter portass

    (@portass)

    invalid nonce parameter in the cookie. it appears after a day of work. I clear the cache and everything is fine again.

    Thread Starter portass

    (@portass)

    Plugin Author CLUEVO

    (@cluevo)

    Ok, so the way this works is that requests to the backend use a nonce value to verify that you are actually allowed to make these requests. What I think is happening, is that you are caching this nonce value and your caching plugin keeps returning pages with the stale nonce. Is there any way you can configure the caching plugin to maybe ignore certain pages? I’ll take a look if we can mitigate this somewhat but as short term solution you can maybe add an exception to the caching plugin.

    Thread Starter portass

    (@portass)

    Additionally, LiteSpeed has recently begun maintaining an editable list of known third party plugin nonces? here. Press the? Fetch Latest Predefined Nonce? button, and the nonces from the list will be automatically appended to the nonces you have already listed in the? ESI Nonce? box. This allows you to easily convert every nonce on the list into ESI blocks. If you have a nonce that you would like to be included in this list, and you are familiar with GitHub, you can add the nonce to our list yourself and? submit a Pull Request.

    If you don’t know the name of the nonce(s) your plugin uses, try asking the plugin author. You should also suggest they add their nonces to our predefined list.

    Thread Starter portass

    (@portass)

    Thread Starter portass

    (@portass)

    hi, delete the comments above. I solved the problem-I limited the time of pressing the cache to 12 hours.

    Plugin Author CLUEVO

    (@cluevo)

    Hey portass,

    great to hear you figured out a solution. We can’t delete posts here though so they’ll have to stay for now.

    We’ll probably add our nonces to the list you mentioned though, so that problem doesn’t come up in the future and people have an easier time solving this.

    Thread Starter portass

    (@portass)

    nice doing business with you!

    Thread Starter portass

    (@portass)

    It doesn’t work, the error continues. Rolled back the plugin to the previous version.

    • This reply was modified 3 years, 9 months ago by portass.
Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘conflict with the caching plugin’ is closed to new replies.