RixNox
-
Posts
5 -
Joined
-
Last visited
Posts posted by RixNox
-
-
As an alternative to your specific suggestion, I suggest a more general approach :-
For each specific unstable Browser/Application, a checkbox to disable cleaning if it has had a version update since CCleaner was updated.
Regards
Alan
This is the point! Unless your hobby is tracking browser updates, you'll never know exactly if and when CCleaner is compatible with a specific browser....
As I guess the guys at Piriform are checking any compatibility issue with existing browser, it would be quite easy for them to disable or at least warn a user on potential issues
-
If you wish to avoid all risks when you use an obsolete CCleaner on a new version of Chrome that habitually moves such things as user preferences,
from locations which CCleaner respects into locations which were once Chromes garbage dump,
then perhaps it is your responsibility to uncheck Chrome from CCleaner's settings.
If this CCleaner strategy, you will never be safe. Authors may update products in a way CCleaner may be fooled and spoil data. The only safe way is to stick to a version check: over an unverified version, disable!
-
CC 4.04.4197 just destroyed my Chrome (Version 32.0.1700.107 m) prefs. Fortunately I had previously synchronized settings with my Google account.
Maybe you should choose to verify what version is supporting, disabling Chrome settings when Chrome version is greater than xxx, forcing users to upgrade CC to the latest version
As I wrote, for future versions I would stick for a version check, disabling risky operations on unsupported versions.
-
CC 4.04.4197 just destroyed my Chrome (Version 32.0.1700.107 m) prefs. Fortunately I had previously synchronized settings with my Google account.
Maybe you should choose to verify what version is supporting, disabling Chrome settings when Chrome version is greater than xxx, forcing users to upgrade CC to the latest version
Google Chrome preferences spoiled by CCLeaner
in CCleaner Bug Reporting
Posted
thanks