Support » Plugin: License Manager for WooCommerce » Weird behavior on activation/deactivation with the last update and litespeed

  • Resolved beeky2



    once again congrats for the great work.
    I’ve noticed an issue from the last update of your plugin. It can be related to Litespeed caching plugin which is a nightmare sometimes.
    I’m receiving messages of costumers complaning they have problems activating or deactivating the license key on my WP plugin. This is happening from the last update of your plugin.
    I’m doing tests with Postman and actually I can perform an activation or deactivation only the first time, then I have to clear all caches to perform the activation/deactivation for the second time and so on.

    Wondering if there’s some cookie or nonce of your plugin I can add to Litespeed “exclude” list to avoid this issue.

    In my plugin, as an example, i had to add this code to whitelist on Litespeed the following nonce:

    // Whitelist the reset password nonce for Litespeed Cache plugin
    if ( class_exists( ‘LiteSpeed_Cache_API’ ) ) {
    LiteSpeed_Cache_API::nonce_action( ‘rs_user_reset_password_action’ );


    • This topic was modified 2 months, 4 weeks ago by beeky2.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Drazen Bebic


    Hello @beeky2

    Sorry for the late reply, I was quite busy the last 2-3 months.

    To be honest, I know nothing of the Litespeed caching plugin or how it works. I’d need to investigate and see what can be done, and to be honest I just don’t have the time for that.

    Since it’s been over a month since you posted this question, were you perhaps able to resolve it on your own in the meantime?

    Hi Drazen,

    I’ve solved the issue myself at that time.
    I just excluded REST API from caching. This maybe a note you can add to your plugin documentation.


    Plugin Author Drazen Bebic



    Thanks for letting me know, if there is anything else you need help with let me know 🙂

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