W3 Total Cache conflict

@diggories

Thank you for your post and for reporting this.

We were able to reproduce this and it seems like it related to the fragment caching. The plugin applies fragment caching for various, popular caching plugins to that page to prevent it from being cached.

We’re adding this to our development list now so that we can investigate and fix it.

Thank you

Any Update on this?

@diggories

Thank you for your follow-up.

We have fixed this issue in our latest development.

We will release an update soon with this fix included.
If you need a development build in the meanwhile, please send us a ticket: https://tribulant.com/support/

Thanks guys,

I will wait for the update.