Watcher works fine if cache is off. It also works if cache is on. Except one thing: The toggle link stays the same therefore I think the (ajax) form to watch / unwatch content will stay the same.

If I clear the cache (i.e. with drush cache clear) and I request to watch a post (as anonymous user) I get the form with the submit button call "watch". If I submit the form and later I want to unwatch it, I also get the form with submit button is called "watch" (the submission works well: it runs the unwatch procedure). If I clear the cache before requesting to unwatch the post, I get the real "unwatch" form (this also gets cached so later I will get the unwatch form wile requesting to watch the post).

I think you can solve this Problem easily by changing the toggle link so it's different for watch and unwatch.

Watcher is also listed under: "The following enabled modules are incompatible with aggressive mode caching and will not function properly". Is this correct, watcher does not work in aggressive mode? Why not?

Comments

osopolar’s picture

osopolar
Primary language German
Location 🇩🇪 GER 🌐
commented
Title: Toggle has problems with (normal) caching » Watcher-Toggle has problems with (normal) caching

(changed title otherwise people will think its about a toggle module ;) )

Militopedia’s picture

Militopedia commented

Hello,

First, this is a great module, exactly what I have been looking for! Thank you for the development :-)

I have the same issue over here. At the moment, the only solution seems to be to turn off caching (loosing performance of the whole website). I would be very glad if in the next release this issue is resolved and 'normal' caching can be used without side effect. Is this planned to be implemented in the next release?

I also noted that when the browser cache is emptied and a page that is tracked already via watcher (as anonymous user) is visited again, the link says again 'You are NOT watching this post...'. Is this the normal behaviour? I don't know how you check whether an anonymous user is watching already or not, but if it's based on IP, then the link should show 'You are watching this post already'. But maybe it is done by a cookie that is lost when the browser cache is emptied? Any insights?

Thanks a lot!
Roger