Quoting Michael M Slusarz <[email protected]>:
It appears a bunch of people are having the same issues on upgrading, and in almost every case it is because they don't have their server (either Horde or their HTTP server) correctly configured regarding caching of javascript files.
I tried clearing the cache and disabling the JS caching in Horde, but get the same errors (on screen at least).
If not already obvious in the configuration literature (maybe it isn't... I don't have it in front of me right now), unless you *really* know what you are doing, you should almost certainly be using static files to deliver JS. This is the ONLY guaranteed way to cache-bust across ALL browsers.
Obvious? Let's see, from the administration page: Javascript caching packages all static javascript files used in a page into more efficient chunks to send to the browser. It also allows compression and optimizations of this file to reduce the data size. Caching reduces server load, speeds up the user's browsing experience, and is HIGHLY RECOMMENDED. HIGHLY RECOMMENDED doesn't seem to make it clear that it shouldn't be used -- quite the opposite I would say... Or do I have something wrong here?
michael ___________________________________ Michael Slusarz [[email protected]]
-- Eric Rostetter The Department of Physics The University of Texas at Austin I still find each day too short for all the thoughts I want to think, all the walks I want to take, all the books I want to read, and all the friends I want to see. - John Burroughs -- IMP mailing list Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [email protected]
