Cookie 4

unfortunately Cookie doesn't work with iCab, so even if iCab uses the Global cookie store (im not sure how that would work on OS X El Capitan - as cookies now work just like iOS.... seperate cookie stores for each app), Cookie doesn't know when iCab is open...

Perfect!

Hello Russell,
I received and installed, thank you.
Have a good night.

Stefano

ah yes,
my license is pretty flexible, Im all for buy once use everywhere.
🙂

Hi Peter,

you can use right-click (secondary click on your laptop) to reveal a contextual menu which you can use to check all cookies.
If you just skip through the setup selection, Cookie doesn't actually remove any cookies till you tell it to. so you could also skip though the "Removal Options" tab in setup.

I'm having trouble with Cookie 4 (and 5) recognizing my Chrome cookies. Often, Cookie 4 will start up with a proper tally of my favorite cookies, but at some time during a browsing session, Cookie seems to forget all my cookies and the counts all go to 0 (see attached screenshot)[attachment=32]. The cookies are still there, though - when I quit Cookie and Chrome, and restart Cookie, the favorited cookie counts all reappear.

My cookie file is located at /Users/username/Library/Application Support/Google/Chrome/Default/Cookies

Why is Cookie not working properly with this file?

What is the purpose of the whitelist and the blacklist ?

First of all Cookie4 manages cookies per domain, and the Whitelist/Blacklist give you an opportunity to be a lot more specific about which cookies you want to keep/delete.

first the Whitelist:
this is when you have a specific tracking cookie within a domain you want to keep. for example the NID Google cookie preserves login details. Many people want to stay logged into Gmail, so whitelisting the NID cookie (under the google domain) will keep them logged in.

the Blacklist:
say for example you have a single cookie within a favorite domain you want deleted. (and you don't want to flag all similar named cookies as tracking cookies) then this is what the Blacklist is for.

Cookie5 will have per-cookie favoriting, so the Whitelist/Blacklist is less relevant. (in fact the eBlacklist has been removed completely)

hmm,
ok, ill do some experimenting.

I never did see the image....
I guess it did get eaten by the Forum.

I wish I had just purchased directly from your website so I wouldn't have to wait for updates and could try your beta updates. Is there any way to transfer my purchase from the App store and just delete the app store install and install the version from your website?
Mark

Sure, not a problem. Just send me an email at support@sweetpproductions.com
and ill make a license up for you to use with the version from my store.
🙂

this is technically possible and I could add it, but im not sure I want to add Cookie editing abilities... at least not just yet.

thats good news!
just waiting on feedback on another issue before i release this officially.
ill also roll this fix into v5.

thanks for being so persistent with your reporting the bug.

Thank you very much, Russell, the delete and re-install method worked for Cookie, and one other app that (after I posted) did the same thing.

A more recent article on iMore explains what happened and includes an update:

Here's What's Happening

My apologies.
I hear you, it was frustrating for me too.
The large number of updates was due to the El Capitan release (and bugs turning up), and me wanting to get stability for those on El Cap.

there won't be anymore updates now unless a major bug is found.
🙂

All my my focus is now on Cookie 5.

Hmmm,

thats not expected behaviour,
Ill look into that.