Opened 15 years ago

Closed 14 years ago

#2904 closed defect (fixed)

djConfig.cacheBust has no effect on non-dojo widget HTML templates or CSS files

Reported by: guest Owned by: James Burke
Priority: high Milestone: 1.1
Component: General Version: 0.4.2
Keywords: Cc:
Blocked By: Blocking:


I've configured djConfig.cacheBust on 0.4.2 and noticed that while it works as advertised for JavaScript? modules both witin dojo.widget and somethingElse.widget, it will not append the cacheBust parameter to somethingElse's HTML template or CSS files. This is for a package somethingElse laid out as a peer to the toplevel dojo, but not built using the build scripts.

Not appending the parameter will cause the browser to always use recent JavaScript? widget definitions but stale templates and stale styling.

I do not know enough about the dojo build system to know if dojo.widget's own CSS and HTML files are rolled into the dojo.widget JS files for download. I do not see dojo base files like *.css?cacheBustParam or *.html?cacheBustParam when watching Firebug.

A naive fix would be adding djConfig.cacheBust to templatePath and templateCssPath when used within Dijit if cacheBust is defined at runtime, but I don't know what else that may break.

Change History (4)

comment:1 Changed 15 years ago by bill

Component: WidgetsGeneral
Milestone: 1.0
Owner: changed from bill to James Burke

comment:2 Changed 14 years ago by James Burke

Milestone: 1.01.1

comment:3 Changed 14 years ago by James Burke

This is fixed in r12320, if you set up djConfig.cacheBust = (new Date()).getTime() then templatePaths will have that cacheBust value appended to the URL. For CSS files, the toolkit no longer loads those directly. To refresh CSS that was included in the page with link tags, try the ReCSS bookmarklet:

comment:4 Changed 14 years ago by James Burke

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.