Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Tockify

    (@tockify)

    Hi,

    Tockify is generated by Javascript as your page renders on the client so in general server side caches shouldn’t cause a problem as long as the cache doesn’t remove our embed code.

    Perhaps W3 Total Cache is trying to pre-render on the server and cache the result or something along those lines. That would cause a problem because Tockify is a live client-side program, not just a piece of static HTML.

    I think W3 Total Cache is able to exclude individual pages from the cache and I recommend that you do that for your events page for now.

    I’m going to install WP Total Cache in a test system and will follow up with anything I learn by doing that.

    I hope that helps.

    Thread Starter arohanui2015

    (@arohanui2015)

    My apologies, on closer inspection this was an issue with my W3 Total Cache settings. In W3 Cache > Minify > JS > JS file management I had added the tockify JS file. This was a recommendation from a page speed report site, and I (obviously) didn’t think it through before adding the Tockify file.

    I removed the file, saved settings and purged cache and all is fine.

    Thanks for your help, sorry for the confusion!
    Steve

    Plugin Author Tockify

    (@tockify)

    No problem – I’m glad you managed to get it resolved!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict with W3 Total Cache’ is closed to new replies.