Caching issues with WhatsApp button

[rodfersou]

I know this is already implemented to show just on mobile devices.

But we have a plone site that is showing this button anyway because the site was accessed first on mobile device and our cache server used this generated html on every device, showing the whatsapp button at desktop for some pages.

The suggested fix is to remove this feature from python code, and implement it with javascript.

This page has an example on how to get it working with javascript.

[cleberjsantos]

Hello @rodfersou the problem seems to be with the memoize, it's not being used properly and this is making the cache. I think using more one javascript file will leave minimally loading the plugin and, consequently, the load slowest page.

Also, if the cache server caches resources such as javascript, we have iqual problem.

[rodfersou]

@cleberjsantos we don't use memoize in this plugin

[cleberjsantos]

@rodfersou yes, we use for template render ;-)

[hvelarde]

@cleberjsantos if you're talking about this memoize it doesn't seem to make sense at all as it's a view memoize and for me we're gaining nothing with it.

the problem is the following: we are using a moderate caching rule that caches for 15 minutes the content types views; if the first user that visits an item is using a mobile device, the WhatsApp stuff will be in the rendering and will be cached.

by moving part of the logic outside the backend into some JS executed by the client, we will avoid that problem; that's the way all other plugins work.