Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Understanding Client Resource ManagerUnderstanding Client Resource Manager
Previous
 
Next
New Post
10/2/2012 2:35 PM
 

Hi,

recently while doing some updates/overhauls on my site UI (css and jquery mostly) I found that there were cases where my edits would not be seen by the end user until they initiated a ctrl + f5 to clear browser cache. The site I am updating is using CRM and has persist files set in the settings.

Could this be a cause for the cache issue I am facing? Is it just a case of incrementing the version when the 'persist files' is set to true in order to insure all end users will see a properly updated version of my site?

Thanks

Mark

 
New Post
10/3/2012 5:47 AM
 
you will always have this issue, if file name remains the same and the client browser is set not to load images and other files upon every request. By versioning the files, this should not happen, if you upgrade version after every file modification.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/3/2012 5:50 AM
 

If you are changing css anywhere on your site - then yes you will need to increment the counter - otherwise the system will not update its cache of the combined css modules.

Basically the system works by merging javascript files and css files into  single file - so that there is only one http request for each type of file each page load.   The name of these merged files are unique ... but as the name itself doesnt ever change - your web browser will continue to use the old cached version unless you hit ctl-f5.

The alternative is to increment the Current Host Version number in the Client Resource Manage - this have the same effect as ctl-f5 - since it forces the browser to reload the files and bypass their cache.

Westa

 
New Post
11/13/2012 1:55 PM
 
Hello everyone!
There's any possibility to accomplish the same goal with DNN 5.6.3?

I'm trying so hard to find a way for forcing client refresh or for versioning my skin.css file but with no success:

I tried to remove (or to set an old date) on "static content - > client cache" on the web.config but didn't work.
I also tried to click on Clear cache link on the host settings -> performance settings, again no success.

Would you please help me to find a solution other than upgrading to 6.x DNN versions?

ps: here is how I set the web.config:

...staticcontent - clientcache - cachecontrolmode="UseExpires" httpexpires="Mon, 12 Nov 2012 00:00:00 GMT" /clientcachestaticcontent...

Best regards.

G.Z.
 
New Post
11/13/2012 2:19 PM
 

If you have already set long duration cache headers at the browser then you can't do this from the server.

http://blog.httpwatch.com/2007/12/10/... explains.


Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Understanding Client Resource ManagerUnderstanding Client Resource Manager


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out