Loading custom js file in chrome caches file indefinely

[nils.enhoerning]

Howdy 🙂

I have an issue, that is most likely a misunderstood feature on my part. I am loading a file via the “Load these files before executing the Custom JS” and referencing a method in it for some rules.

This works brilliantly in IE(not exactly normal, i know :P), but chrome seems to be insisting on caching the js file from several versions ago, a shift-f5 is not helping at all 🙂 While I can likely get around this by purging my chrome caches, this is not something i can expect the users to be able to deal with if i need to alter the scripts after they have begun using them.

So long story short: Is my only option to rename the js file everytime or is there some trick or setting i can use to avoid the js file being cached 🙂

I am using the newest version of dffs from a week ago:

Version information
DFFS frontend: 4.4.2.5
DFFS frontend CSS: 4.21 / 4.21
Autocomplete: 1.4.12
Cascading dropdowns: 3.6.5
jQuery: 1.12.4
Lookup: 1.1.5
Resource management: not loaded
SPJS-Utility: 1.270
vLookup: frontend v2.2.79

Best regards,

Nils

[Alexander Bautz]

Try appending a version number to the file name like this:

/folder/filename.js?v=1.0

Then change this version number if you want to force loading a new version.

Alexander

[nils.enhoerning]

You are, as always, the sp js messiah! Thanks, that worked brilliantly, and I am pretty ashamed i did not think of the versioning system myself… 😀

[AdamP]

Is this related to the minimal download strategy in SP2013 and up?

[Author]

Posts