Clearing Cache on the Hosted Platform

[craigbrass]

After modifying templates, you may need to clear the cache folder. If you host it yourself that is fine but if you are on the hosted platform, you need to do the following.

1. Go to the members area (http://members.kayako.net).

2. Login using your email address and password.

3. Look under the options heading on the main page and click the "Clear Cache Directory".

[pik20b]

What tab option in the Members Area? I didn't see anything related to clearing the cache directory.

Thanks.

[supportskins]

Or you can simply run the URL -- http://domain.helpserve.com/staff/in...a=rebuildcache in the browser.

[ccrook]

We just got a hosted package through a reseller who initially put in their name for the "company name" in general settings. It still shows up as them in the title bar of the page despite cache rebuilds (using the link provided above) and local browser cache clearing.

Any suggestions?

Edit: I just changed it to hardcoded in the header template, but I'm curious as to what was causing this...

[Jamie Edwards]

Hi ccrook,

Take a look at the "Company Name" specified under the settings for your default template (Admin CP -> Templates -> Manage Groups -> Edit).

[ccrook]

Ahhh didn't know about that area.

Thanks, Jamie.

- Chris

[John Haugeland]

Granted this doesn't apply to ccrook, but in case someone else needs it: there is also a newly discovered issue, where phrases and templates are under rare circumstances cached despite a URL cache call. It's marked for fix in 3.30.02 stable.

If you find that a cache rebuild doesn't clear text you know for a fact you've updated, you may be tripping across this bug. (Granted, lots of people are simply mistaken when they believe this, but that's neither here nor there.) If you are tripping across this bug, just load the phrases page and hit the update button without changing anything, then do the same thing in templates, then re-run the cache clearing URL.

If that doesn't fix it, you aren't tripping across the post-cache bug.