In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Relationship Graph View Issue ] Dependency Graph ]
related to child of duplicate of

Viewing Issue Simple Details
ID Category Type Reproducibility Date Submitted Last Update
0000040 [In-Portal CMS] Admin Interfaces bug report always 2009-06-03 04:41 2011-12-02 04:56
Reporter alex View Status public  
Assigned To Dmitry
Priority normal Resolution no change required  
Status closed      
Summary 0000040: Issues with JavaScript and CSS Caching
Description When script.js or any other script or css file is changed, then it's name stays the same and browser doesn't query it's new contents from server again. This could be a problem, especially, because user's need to clear browser cache before doing anything.

I propose to add new configuration variable named "ScriptVersion". It could be number or timestamp, doesn't really matter. We don't show it to user in admin (can change in db directly) and add to any script/css include in admin templates, like:

<script src="js/script.js?<inp2:m_GetConfig name="ScriptVersion"/>" .../>
<script src="inc/style.js?<inp2:m_GetConfig name="ScriptVersion"/>" .../>

When we change something in js/css then we change this variable value in db (and in upgrade script). This way when js/css is changed, then url also will be changed and browser will be forced to reread content from webserver.
Additional Information

Web Development by Intechnic
In-Portal Open Source CMS
In-Portal Open Source CMS
Copyright © 2000 - 2009 MantisBT Group

Powered by Mantis Bugtracker