Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Albert Peschar

    (@kiboit)

    Hi unalgu,

    Thanks for trying out PhastPress.

    It looks like you’re using a caching plugin. Could you empty the plugin cache and try again?

    –Albert

    P.S.: If you like PhastPress, I would really appreciate it if you left a review here.

    Thread Starter unalgu

    (@unalgu)

    Cleared all cache (manually deleted plugin cache as well. No change still getting the error messages. We are using w3 total cache if that helps.

    If it is not compatible with the caching software we are using please let us know.

    Love the plugin less the warning messages. If you can fix will leave a 10 star review

    Plugin Author Albert Peschar

    (@kiboit)

    Hey unalgu,

    Sorry, I think my message was unclear. I understand you deleted this:

    • W3 Total Cache full-page cache
    • PhastPress cache folder

    When PhastPress is used, it generates a token (a kind of password) that is used to sign the URLs for images, CSS, JS, etc., to avoid changing the URLs (allowing users to overload the server by resizing images, etc.).

    You should not empty the PhastPress because it resets the token. If someone loads a page before you do the reset, that page will have the old token in the full-page cache, then you empty the PhastPress cache, and the token is reset. Those pages in the full-page cache with the old token no longer work.

    So could you try again to empty only the W3 Total Cache? Please let me know how it goes– if you still have the issue I’ll make sure it gets fixed.

    –Albert

    • This reply was modified 5 years, 11 months ago by Albert Peschar. Reason: Formatting
    Thread Starter unalgu

    (@unalgu)

    Albert,

    Thank you so much for your quick responses. The issue still remains – even after deletion of the cache files.

    Please let me know if you need any additional information from me for a potential fix.

    Thank you.

    Plugin Author Albert Peschar

    (@kiboit)

    Hi unalgu,

    Can you confirm that you deleted only the W3 Total Cache files? Because it seems that it’s still a full-page caching issue. Are you clearing the cache via the W3 Total Cache settings, or otherwise?

    For example, I see the issue on this URL:

    https://www.society19.com/

    But not when I add a random parameter to avoid the cache:

    https://www.society19.com/?2019

    If you did indeed only clear the W3 Total Cache again, and the issue persists, could you install the Health Check plugin and post the debug information and paste it here? (See instructions.)

    –Albert

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Params verification failed’ is closed to new replies.