Add Opera Portable Custom path in INI or CCleaner

Hi, i know i have requested before to custom add official opera portable path (that when use official opera installer and choose stand-alone installation USB) in INI file or CCleaner so that CCleaner can read it as it's installed in the system.

I tried the suggestion page in CCleaner but i have found when i add a custom location it will delete all files: ex. cookies

so please add this option.

thanks

currently Opera is not supported by Custom Locations however I'd also love to see it implimented (so odd that it's currently only supporting chrome-based and mozilla-based browsers)

Thanks for your reply

I hope to add it in the next version...

Any news about this feature ?

It's have been more than 3 month...

I'd like to vet support for the 64-bit portable installation of Opera as well; it appears there is support for the 32-bit version of a portable installation of Opera, but this doesn't work with the 64-bit version...

:huh:

Opera is supported, here's an example I've in my ccleaner.ini: CustomLocation4=OPERA|I:\PortableApps\OperaPortable\Data\profile

wait opera works for custom location ?!? Sweet thanks nodles

I don't see any 'custom location' entries in my ccleaner.ini or winapp2.ini... What's the exact syntax that should be used? And how is it that on a 32-bit install of Windows 7, CCleaner detects and cleans a portable installation of Opera, but can not detect the 64-bit installation Opera portable (or 64-bit portable installation of Opera Next ) on a 64-bit installation of Windows 7? Please advise?

I don't see any 'custom location' entries in my ccleaner.ini or winapp2.ini... What's the exact syntax that should be used? And how is it that on a 32-bit install of Windows 7, CCleaner detects and cleans a portable installation of Opera, but can not detect the 64-bit installation Opera portable (or 64-bit portable installation of Opera Next ) on a 64-bit installation of Windows 7? Please advise?

follow the link in reply #2

most browser entries in ccleaner use a specialised detect. So this may be why 32bit sees but 64 doesn't.

Thanks Nergal -- though it would be nice if Crap Cleaner could reconcile this and do it automatically as the native detection gives nice audit confirmation of what was cleaned vs. the 'custom locations' method.

What's more, the x64 builds of Opera have for some months been at feature parity and have surpassed the 32-bit versions for stability and performance -- and are seeing a substantial up-tick in use.

:)

what no the custom locations tells opera where to look for the opera section, it's transparent compared to native (no differences)

Yes, I understand that -- but when you use custom locations there's no audit display of the path being cleaned in Crap Cleaners output display...

I think you are confusing custom location with includes

if I use

CustomLocation4=OPERA|I:\PortableApps\OperaPortable\Data\profile

and analyze opera cookies, it shows the cookies that are in my opera that will be cleaned

No Nergal, I'm not cousfued, I use the same kind of path statement. You seem to have missed the point that I am referencing portable installations of the 64-bit editions of Opera and Opera Next -- you appear from your path data appear to be using the 32-bit version...

Edit: I finally got it to work, though I've been using the same path statement all along, added quotes and removed them from the path, used truncated short file names etc:

CustomLocation1=OPERA|C:\Program Files\Opera x64\profile\cache

When I added 'cache' to the string it was finally detected... And that's why there's veracity in having this as a native feature of Crap Cleaner, a lot of people aren't going to be as patient as I am...

note that was not my path, it was nodles. I'm glad you got it figured out, though I wonder why you are using a portable in c:\program files? And why you are letting any program write it's temp file in that directory especially a web browser?

On that point I believe that I recently +1'd a suggestion for just that, inclusion of a native interface for that, for now I am content with it being an advanced, yet easy function in an ini

is your profile in side the cache folder?

as of yet I do not have access to a 64bit pc

Well taking your questions in order; there are substantial advantages to be had with regard to security to using portable applications that are natively portable; ergo do NOT write to the Windows Registry (don't require a wrapper to redirect Registry i/o) and whatever local directories they store anything in is immaterial as long as the permissions are properly managed. That said I have all my Opera data hard-linked to a RAM disk, so the application is in effect 'sandboxed'...

B)