assets cache problem after upgrading version

  • Hi,
    recently I upgrade from version 1.18.3 to 1.20.6.
    In my virtual tour 360 I usually place some hotspots and, after upgrading, I noticed that they will be displayed at 180 degrees from expected position.
    The only way to make them display in the right position using new version is to completely clean browser cache (at least once!) and then it runs as expected.
    This behaviour could create problems with my site users so I need to find a solution to invalidate completely cache without any user's action.

    In my html main file I place that metas to prevent cache:

    Code
    <meta http-equiv="cache-control" content="max-age=0" />	<meta http-equiv="cache-control" content="no-cache" />	<meta http-equiv="expires" content="0" />	<meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />	<meta http-equiv="pragma" content="no-cache" />	<meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" />


    I also add some fake parameters to assets url to invalidate the cache (e.g.

    Code
    <script src="krpano.js?abc"></script>

    )
    but nothing change!

    Anyone faced this problem and could give me some useful advice?
    Thank you in advance

  • Anyone faced this problem and could give me some useful advice?
    Thank you in advance


    Yes for the last 20 years,

    The only browser that has an easy option in menu to clear the cache is Safari. But even they has made it more difficult as you since a couple of years has to activate the special developer menu.

    I simply can not understand that such a simple problem can not be solved with a very visible button or menuoption that also the normal user can find.

    Worst is when you have to go through several menus on iPhone and iPad to delete the cache while optimizing your site.

    I tried all the simple options with Metatags but they do nothing.

    Einmal editiert, zuletzt von HansNyb (29. Mai 2020 um 19:11)

  • Believe me, this kind of things are not simple on any Apple device, anyway this is not what I need..
    I cannot ask all the users to clean their cache to see hotspots on the right place.
    I've tried changing the name of the main js and xml files but still no success.
    On Chrome (win or linux) still CTRL+F5 does nothing, you must clean browser cache.
    I spent a lot of time trying to understand which are the cached assets that cause this behaviour but I havn't found them!
    Hope someone else give some advice.

  • i dont think that there is a 100% safe way to force browsers to load your changes instead of their cache
    there are some things you can do on the server side (expiration etc) but if the browser respects that is another story
    so, in general NEVER update (static) live home pages without also changing the url.

    in development phase, when my clients need to approve, I always use a new link after changes
    and i check everything 3 times in my dev links before i release the final link *rolleyes*

    there is one trick though :
    you can use redirecting to forward your final link to your update
    ie https://mytour.com/index.html forwards to https://mytour.com/200528a/index.html
    this will fix any cache problem, but the downside is, that this is visible in the browser

    HTML
    <!DOCTYPE html><html><head>
    <meta http-equiv="refresh" content="0; url=./200528a" />
    </head></html>
  • Unfortunately I can't do that for virtual tours previously created *sad*
    They could be recreated but still mantain the old url.


    I tried changing all the filename of all created vt but it seems there's something else saved in browser cache (chrome, safari, firefox...) which could be cleared only deleting browser's entire cache. *sad*

  • for old tours its not such a problem... the browsers cache will expire and then it will load your changes
    the problem is more with just released tours, when your clients are still are all over it

    if your old tour used krpano 1.18.3, it probably was not very active the last days ;)
    so probably nobody has a cached version. only you because you first checked and then updated it

    still ... you can read this...
    https://www.digitalocean.com/community/tuto…hing-strategies
    https://stackoverflow.com/questions/4954…ss-all-browsers
    https://stackoverflow.com/questions/4480…r-cache-control

  • Unfortunately not, they were very active because covid situation....

    situation is:

    - If you are a new user no problem : the new vts are ok
    - if you are old user and has old vt created with 1.18.3 they still work but they will not when cache expires.. if you have both older vt and newer one.. that's a disaster!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!