Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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...Administration ...Administration ...How to force clients to reload skin.css? Client Caching ProblemHow to force clients to reload skin.css? Client Caching Problem
Previous
 
Next
New Post
10/15/2010 7:41 PM
 
rubicite


Joined: 6/22/2010
Posts: 9
Sometimes when I make changes to my skin, visitors to the site who have visitors to the site are seeing the old skin.css file.

The common way to resolve this is put a version number in the url to a css file. Example: skin.css?ver=1.12

However, I do not see any way to do this with DNN (I'm not using the source version and have no desire to edit the core of DNN).

I'm using IIS 7 and DNN 5.4 with moderate caching.

I have confirmed the problem persists no matter the cache setting.

I have also confirmed that the problem can be resolved on the client side with a hard-refresh (Ctrl-F5 in Firefox), but I can't exactly ask my customers to do this when they visit the site.

I need to somehow tell the browser clients that they need to reload the css files for the site.

Is there some way to do this?

Thanks!
 
New Post
10/15/2010 8:33 PM
 
Matthias Schlomann


Joined: 8/10/2003
Posts: 3594
It is a problem all sides have.  The Browsers saved the site in the client temp folder like a proxy.  There is no way to start a hard refresh of the page with clientpostback.  If a ueser didn't unload/delete the files closing the browser leaves the files localy on the client system.

Regards
Matthias
DNN MVP
www.aarsys.de
Metro7 Skin
ShoutCastStats Module for DNN
 
New Post
10/15/2010 8:33 PM
 
Matthias Schlomann


Joined: 8/10/2003
Posts: 3594
It is a problem all sides have.  The Browsers saved the site in the client temp folder like a proxy.  There is no way to start a hard refresh of the page with clientpostback.  If a ueser didn't unload/delete the files closing the browser leaves the files localy on the client system.

Regards
Matthias
DNN MVP
www.aarsys.de
Metro7 Skin
ShoutCastStats Module for DNN
 
New Post
10/15/2010 11:56 PM
 
rubicite


Joined: 6/22/2010
Posts: 9
The solution is to browse to the skin files in CSS, switch to features view, go to HTTP Headers, Add an expiration of 1 second to your skin.css and other .css files that might change. Keep the 1 second expiration during development. Then, when the development of the site is complete, set those expiration headers to be much higher.. 1 week perhaps. Be careful with this though, if you might have to make changes, customers' browsers won't load the new file for a long time if you expiration value is too high.
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to force clients to reload skin.css? Client Caching ProblemHow to force clients to reload skin.css? Client Caching Problem


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