Old Cache & CDN Data after push to Production
Hi, did anyone else have the same problem like us that the appcache and the files delivered by the CDN will not be refreshed on production after an push to production? If we changed some content in ...
Forum Discussion
Hi luk ,
thanks, but the application.version.revision wasn't the solution for our problem. The application.version.revision is the Khoros release revision, not the studio version. The the number will not change after a push to production without a new Khoros Release.
Any other ideas?
Greetings
Steffen
Hm, you could try to use the appcache (FreeMarker context object) to store the revision number from
restadmin("/plugins/live/version")
that would avoid repetitive (and unnecessary) API requests to a certain degree.
Another option could be to simply create a custom setting (you need support for that), add some kind of versioning-string in there and add that for cache-busting, something like this:
<script type="text/javascript" src="/html/assets/js/thc.global.min.js?v=${settings.name.get('version')}"></script>
