Is it gone? I could only find something similar under the optional Develop menu...dumbing down much or what?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Safari 6 - Where is the EMPTY CACHE option?
- Thread starter 50548
- Start date
- Sort by reaction score
That's it and if this were dumbing something down it would be in a menu and easier to get at. So not sure what you're getting at here.
Before I would click ONCE with the mouse in order to choose "File" and then select Empty Cache.
How is the new setting any better?
p.s.: Nevermind, they seem to really have moved it to "Develop"...doesn't really make a difference.
I'm with you, BRLawyer. What no one has pointed out is that the "Develop" menu won't show up until you go into Safari's Preferences under the "Advanced" tab, and click the box at the bottom that says, "Show Develop menu in menu bar." Then, you can find the option in the drop down Develop menu that says, "Empty Caches."
Even better, it gives us the keyboard shortcut, "Option+Command E".
Click on the Safari menu in the menu bar and click "Reset Safari". It will then prompt you for what you want to "Reset" or clear.
Develop Menu > Empty Caches issue
Perhaps you should either update to version 6 for Safari or check the "Reset Safari" menu (or both). Their is not an "Empty Cache" option there.
I did try the "Develop" menu option to "Empty Caches", but upon checking the ~/Library/Cache/com.apple.Safari folder, it was registering 53MB. So that is not working either (though it does delete the custom icons for specific sites). What an annoyance this issue is!
Perhaps you should either update to version 6 for Safari or check the "Reset Safari" menu (or both). Their is not an "Empty Cache" option there.
I did try the "Develop" menu option to "Empty Caches", but upon checking the ~/Library/Cache/com.apple.Safari folder, it was registering 53MB. So that is not working either (though it does delete the custom icons for specific sites). What an annoyance this issue is!
Oops.
10 to 1 says some coder dozed off and just forgot it. Just like they removed "put back" in the trash menu a while back. (But god bless 'em... it only took 2 new OSX versions to see it returned.)
10 to 1 says some coder dozed off and just forgot it. Just like they removed "put back" in the trash menu a while back. (But god bless 'em... it only took 2 new OSX versions to see it returned.
)Oops.
10 to 1 says some coder dozed off and just forgot it. Just like they removed "put back" in the trash menu a while back. (But god bless 'em... it only took 2 new OSX versions to see it returned.
You seem to be putting a lot of faith on "involuntary oversights" lately - for me the direction is clear, and the BAD decisions are more than deliberate...let's just hope they read these comments and put the thing back into Safari 6 (a disaster in its own right, with missing spinning wheels, missing activity monitor and missing backspace).
Anyone who actually empties the cache in their browser is not going to have any trouble clicking a checkbox to show the Develop menu.
And it's still better than Chrome or Firefox, both of which require navigating multiple screens and checking/unchecking checkboxes every time you want to empty the cache.
And it's still better than Chrome or Firefox, both of which require navigating multiple screens and checking/unchecking checkboxes every time you want to empty the cache.
I've been through too many OSX versions to think otherwise. I've seen it all. One must only ask... why would they intentionally remove it? After all, the very first thing any rookie tech support person tells you is to do when Safari acts up is to "empty the cache". And emptying the cache poses no risk to the user otherwise, I can see Apple removing yet another feature to protect us from ourselves.
Again, somebody simply goofed. OSX development is not this massive room in Cupertino filled with hundreds of coders working 12 hour shifts. Those days are over.
I absolutely love the expression "involuntary oversight".
What about "unnecessary redundancy"?
----------
I could give you at least 10 instances of Apple decisions which ended in exactly the same kind of outcomes...not involuntary at all.
Just one more reason not to upgrade to Mountain Lion...
This used to be something that Safari had right for a long time it used to be the quickest and easiest to Empty Cache... using Safari > Empty Cache.
Removing this feature makes life harder for many people in tech support, web design, and communication with clients about their websites (it's much harder to explain how to Empty Cache now... there should be no barrier to this).
This used to be something that Safari had right for a long time it used to be the quickest and easiest to Empty Cache... using Safari > Empty Cache.
Removing this feature makes life harder for many people in tech support, web design, and communication with clients about their websites (it's much harder to explain how to Empty Cache now... there should be no barrier to this).
Click Preferences -> Advanced ->check the "Show Develop Menu in Menu Bar" check box ... gives you a permanent drop-down menu for cache emptying etc. I like it actually - show page source is a function I use a lot and it's nice having all the geeky stuff grouped together within easy reach.
Scotty
Just noticed that selecting "Disable Caches" still allows sites to store caches in Safari 6. Previous versions had a setting in preferences to not allow storage that actually worked.
If you empty all caches in Safari 6, then select "Disable Caches", just visit one website (such as macrumors.com) then check under preferences how many different web site caches are listed (Preferences>Privacy> Cookies and Website Data> Details).
If you empty all caches in Safari 6, then select "Disable Caches", just visit one website (such as macrumors.com) then check under preferences how many different web site caches are listed (Preferences>Privacy> Cookies and Website Data> Details).
I don't like the way they moved it either.... was difficult to find, had to search for it for a bit.