Caching slimbox2_autoload.js.php

[monodistortion]

Hey Greg,
I commented before on your about caching slimbox2_autoload.js.php so I thought I would comment again on that. I’m not sure what you use but I use the Firebugs Net panel and YSlow to see what gets loaded and the header information.

Here are some good links I’ve been reading about caching:
http://developer.yahoo.com/performance/ … ml#expires
http://www.websiteoptimization.com/speed/tweak/cache/
http://www.mnot.net/cache_docs/
http://www.mnot.net/blog/2007/05/15/expires_max-age

I just upgraded your plug-in to version 0.9.4.1 and I noticed that the CSS images weren’t loading since they had moved. The problem turned out to be that slimbox2_autoload.js.php was cached from an older version without the in-line CSS functions. I think this could be solved if you changed the version string any time the settings are changed in the admin panel. For example, if I changed the settings right now the script would be loaded as slimbox2_autoload.js.php?ver=20080126150600 or something like that.

So, in general, you want files to be cached as long as possible but they should be refreshed when they change.

[malcalevak]

Thanks for the info, I will look into this.

I’d actually thought about the whole modifier extension, I just hadn’t gotten around to implementing it, and wanted to get a localized release out – hence the new version disabled caching. I admittedly hadn’t considered putting in a time stamp as the date, like yours appears to do.

The trick is going to be likely storing each update’s timestamp into a new option, and feeding that in the enqueue script block.

[Author]

Posts