Trying to find out if there can be a method that forces the custom.js file that contains the jkuery code to modify the way the ticket displays/functions. At the moment it seems the only way is to have the Users/Owners manually do an F5 or Cntrl + F5 to refresh the browser cache to swallow new changes. Even though the date is greater on the modified custom.js script, the changes don't take effect until an F5 occurs.
I was hoping there may be an option to do this with some special syntax in the jkuery file or perhaps an Appliance* side setting that could always for the persons opening up the ticket to always get the latest version to load automatically.
*We run 3 virtual K1000 appliances Sandbox, Development, Production
Thank you
Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer Chosen by the Author


In lieu of our request to have the Apache server config updated to "turn off expiration on KACE content" (preferred method) we have established a means to accomplish this.
*rename file custom.js to custom1.js (non-preferred)
*update the marker files to reflect this name change (non-preferred)
*re-apply the Jkuery patch (non-preferred)
The only improvement from our perspective is for us to have access to Apache config to add "turn off expiration on KACE content" and thereby eliminating the the need to modify the file name/modify marker file contents/re-applying the Jkuery patch.
Answered 09/21/2015 by: gabbenante
Senior White Belt

Please log in to comment
Answer this question or Comment on this question for clarity