Huge Caching issues

Hey, I have been using FCK Editor on a .NET site for about 6 months now.

I decided to upgrade because my clients were experiencing an issue in which 2.6 fixed. I was running 2.5.1. Unfortunately, the editor doesn't load in FF or in IE6 because an older version has already been cached. When I personally clear the cache, everything works.

My client-base is not the most technical, and telling them to 'clear the cache' is proving to be detrimental, as it looks like it is our fault the editor stopped working. Besides, being on the phone all day is a huge time-sink.

Is there an easy way to either fake the browser into thinking it needs to reload the fckEditor Javascript? I have tried the usual meta-tags but nothing seems to work.

Thanks in advance,
Matt

Sat, 05/17/2008 - 13:09

fredck

Joined: 19/01/2007

Posts: 898

Re: Huge Caching issues

The best solution for it is installing new versions in different folders. So you have:

/fckeditor/2.5.1
/fckeditor/2.6

Then, you can set the "FCKeditor:BasePath" application setting in the web.config to easily switch to the new installation:

<configuration>
    <appSettings>
        <add key="FCKeditor:BasePath" value="/fckeditor/2.6/"/>
    </appSettings>
</configuration>

Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn

Sat, 05/17/2008 - 16:31

a.m.

Joined: 20/04/2008

Posts: 256

Re: Huge Caching issues

You can also control caching of static files (CSS, JavaScript, images, etc) through IIS configuration. Go to website properties and select the HTTP Headers tab. Check Enable content expiration checkbox and pick time you would like IIS to tell clients to cache contents for.

Good caching practice for larger web sites is to enable one day expiration and one day before deploying new content reduce it to 5 minutes. For smaller a site, you can set it to 5-60 minutes, depending on the usage pattern.

Mon, 05/19/2008 - 22:07

mrd9483

Joined: 15/05/2008

Posts: 2

Re: Huge Caching issues

Thank you both for the fantastic replies. I didn't think of putting them in different folders, and that's a great practice to keep in mind for IIS.