Been a long time user of both CC and love it, thanks again for keeping it free!
This may not be a bug of CC at all but please excuse me for feeling I need to share my recent experiences, only you would know whether it is or not.
I've always noticed that CC would not allow me to keep any cookies from WebMail Notifier (WMN) but it never bothered me because, for some reason, I never had a problem with WMN retaining what it needed. But since turning-on Gmail's 2-step verification, it's become a problem. It's back to all good only if and when I deselect Cleaner+Applications+Firefox+Cookies before running CC.
More details:
Each Gmail account in WMN has three associated cookies. When I choose to keep any of them, it looks good on the right but, if I immediately click on another tab then click back on the Cookies tab again, I see CC dropped the ending part of the cookies name (the vertical line onward):
In search of support from wmn, it seems wmn is now using firefox cookie manager and in firefox I see that the cookies are named as mentioned. I hate to point fingers but it would appear to me that the problem is that CC is not recognizing that vertical line character.
With security being more important, I'll have to give up the convenience of wmn till this is nailed.
My apologies, I should have done this prior to posting initially.
I just ran a clean instance of FF and noted that WMN is creating their own cookies named as such, not FF. I'll take your reply and my findings to WMN with hopes to get this fixed.
Not to defer from what ever the appropriate action is in moving forward by either party, I want to share that I did receive v2.9.3 via an attachment in an E-Mail from the Dev of WMN and it works perfectly, the vertical line has been replaced with #.
Though WMN is now at 2.9.3 and it has been buggy ever since it moved from 2/8/3 to 2.9x. Though 2.9.3 is better, I still feel there are issues so I would keep and eye on things vs jumping the gun.
I want to share that I did receive v2.9.3 via an attachment in an E-Mail from the Dev of WMN and it works perfectly, the vertical line has been replaced with #.
Awesome that's a good outcome (better that devs make things Windows standards than ccleaner changing itself for each and every proggie IMHO). Good response from the developer.
WMN is an add-on that's been granted full review by Mozilla and is available in the gallery with a warning-free install button. That should speak for itself.
WMN is an add-on that's been granted full review by Mozilla and is available in the gallery with a warning-free install button. That should speak for itself.
That speaks to me of inadequate evaluation by Mozilla.
WMN probably recognize that their use of a special "poison" character has damaged the the ability of Windows itself to support its use,
and have wisely chosen to avoid problems for anyone who does NOT use CCleaner but uses one of the billions of other third party applications that run and stumble under Windows.
It is NOT just CMD.EXE that has inhibitions about the validity of '|'
Windows Explorer does not like it either - try creating a file with a name that includes '|' and you get shown this plus 7 other special reserved and illegal characters.
Thanks for the patients with me, it's much appreciated. And the explanation, it does make sense, none of those characters should be used in any naming convention, at least not in Windows OS. It's a bit troubling to see FF allowed/missed it.
