Trying to live with Ccleaner 7 - modifying

Hi. I figured out how to manually “import” my existing cookie exclusions into the new version (settings.json), but I can’t seem to add any cleaning functions, as in winapp2.ini

They go in ccleaner.ini, but I insert an entry using what appears to be the new format – ignored.

For the cookies, AI is helpful to take one’s old list and convert it into properly-formatted new list as settings.json .

Anybody figure this out yet?

Piriform has a sh*t show on their hands as it is now.. don’t know what they’re thinking, other than they are now invested in their new version no matter how many customers they lose over it.

If I can get my winapp2 type entries recognized it’s conceivable I could live with the new version of ccleaner.

On upgrade from 6.39 to 7 if done as an in-place update will copy (eat because the old files no longer exist) your cookies, includes and excludes to the 7 format.

I can see (and pinged winapp2.ini developer) the new rules have “author” tags so maybe advanced/custom rules are planned (supposition only)

I know the cookies did NOT transfer over when the initial cc7 release was available - if they do now, great.

Until they give us more granular control as we have in cc6, cc7 will be an abomination.

1 Like

they won’t carry over, as in change one change the other. During the initial install (when 7 surprised us in October) at least all my cookies and includes and excludes were (as i said) eaten by 7 and transferred over

no, I understand. but one of my first complaints was that on initial install, cc7 did NOT bring over any of my settings from cc6.

Weird wonder why mine did and yours didn’t

I enabled the option to save settings in the registry instead of an ini file… ?

That sounds plausable i used ini so maybe that’s why

@Laurence_CCleaner can we get confirmation on the settings import only happening with registry vs ini import, and whether by 7.2 this has been resolved.

CC 7.2.1080.0 did successfully copy/move my settings from the CC6.39 registry, delete cc 6, and clean the registry of the cc 6 entry.

Now make cc 7 accept our winapp2.ini files and you will have far fewer pissed-off loyal customers!

One other question: what cc 7 files do we need to back up so we can install again if necessary? I know there’s at least a couple json and a couple ini files – a complete list would help, thanks!!

PLease reread my signature and title. I am a user like you I fixed nothing I can fix nothing
I have no answers your questions, but I am exploring 7 and learning things. You could do the same just by renaming files .old
CCLeaner 7 for all our complaints is pretty “ajar source” (neither open nor closed) and has plenty of plain text files which can be opened in notepad, even if they are a no extension file.

I can edit the underlying file and add the winapp entries, but cc 7 seems to ignore them at this point.

Yeah I think it’s a future infrastructure that isn’t all the way in, my only clue that there will be custom rules in ccleaner 7 is the Author tag in the preexisting rules