Comment to 'Messenger update errors'
  • One more way to invalidate all caches is to change revision number, you can try to do it as well in Studio > Developer > Revision number

    • The Revision number is now 255. I can just change that number to 256, save then clear cache? Then all devices should see this and their cache should clear and refresh?

      A lot of the problems seem to be that members devices also needs to clear their caches. One of my moderators already cleared her cache in Chrome and it was working fine, now she can't do anything at all on the site. It's working fine for me in Chrome but not for her. My user base was cut in half over night so I'm thinking many others can't use the site either.

      • The Revision number is now 255. I can just change that number to 256, save then clear cache? Then all devices should see this and their cache should clear and refresh?

        Yes, that's correct, when you change revision number then names of cache files are changed, so users don't need to clear cache on their devices, new version of files should be loaded after this change.

        • Thank you very much, that really seemed to help. I will keep this in mind. Could be a handy tool to know.