Safari Making Me look Bad to Clients

[evildan]

First let me say, I love Safari. I have been using it since beta and didn't look back.

For the most part I've been using it 100% of the time. However, I've recently been forced to unearth -- ACK! -- IE Explorer because of a reoccurring issue in Safari.

Safari will not clear cache and it's starting to make me look bad to my clients.

I am constantly revising web pages, general tweaks here and there. And after those tweaks are done, I have to show my clients that they are done. Some of them are using Safari, but most aren't (as they are on PC's). But it's getting to the point that my first question to clients after they ask me why their changes haven't been done, is do you use Safari?

I test pages on a number of browsers and platforms and I've never seen a browser hold cache like Safari does. I've gone to the extent that I leave the site I originally try to view, click on "empty cache", quit Safari, load another web page, THEN finally attempt to view the cached page. Very often it still holds the cache. Even after several attempts to do so. I've also seen pages hold for days after several revisions have been completed to the page it has in cache.

I'm not bashing Safari, in fact, as I said above, I'm really happy with it overall. I just cannot use it to show clients the websites I've developed for them because it insists on holding the page in cache.

Looking ahead, I'm counting on Safari to resolve this issue so I can once again rely on it as my sole browser of choice.

Empty cache should mean empty cache and it's clear that, for the moment it isn't clearing everything from memory.

Apart from "Reseting" Safari, is there anything else I can do?

[evildan]

Okay I downloaded Safari Enhancer and was able to disable cache.

Which tells me two things...

1) This is an issue with other people
2) Apple really cannot expect people to download helper applications like this to solve these types of issues. These enhancements should be included in Safari 2.0.

[evildan]

You know what, that didn't even work!

Safari Enhancer disables the Safari Cache and for some reason it still displays the incorrect version of some pages in memory.

There must be some system image cache that Safari uses to display commonly accessed images because I am currently looking at an a version of an image several iterations old.

Any thoughts on this?

[bobw]

Get Cocktail and empty the cache.

[evildan]

Thanks bob, I've done that too.

And, for me, it works. But I can't see telling my clients to do that. Considering I'm the one who sold them on the browser to begin with, my clout with them is under suspicion.

The most I can hope for is for them to use another browser to prevent these pages from displaying cached versions. At least in other browsers, clearing the cache means clearing the cache.

My clients are up in arms because they think the changes have not been completed, I am currently the only one who knows they have been done, because I personally did them and uploaded them to the dev box.

And yes, I've cleared the Dev box's cache, it's set to not cache for this very reason.

Kind of a bummer, but nothing says I can't wait for a fix.

[pds]

Is it little tweaks or big changes? For example, the apple site changes pretty regularly and I (think I) get the change right away.

I reset my prefs on the board and they showed up right away. I hope I don't have to go back to IE, it is unpleasant to look at after months on safari.

[bobw]

See if just refreshing the pages gets the new page up.

[bobw]

Evil

Try this;

First, go to the Safari menu and empty the cache

Now open your home folder.
Open your library folder.
Open your Caches folder.
Get Info on the Safari Folder.
Expand the video for the Ownership and Permissions section.
For all of the users, select no access.
Close the info window
Close your finder windows.
Done.


If you simply remove the folder, I think Safari creates a new one. By leaving it there, but not allowing it to be written to, Safari can't use it for anything. Just be sure to empty the cache first, else it'll keep whatever in there.