New: HomeBank (Sep 03, 2023), Platform 26.2.1 (Sep 17, 2023)
450+ real apps (49GB), 1.1 billion downloads, Please donate.
Jack Haller, Advisor and Father of Our Founder, Has Passed Away
Hi,
I am the developer of FoxyProxy. Some users have requested that it work with PortableFirefox. I haven't used Portable Firefox yet, but I'd like to know what generally needs to be changed to make an extension work with PFF.
FoxyProxy has a settings file which, by default, is created and stored in the user's profile (this can be changed, however).
Thanks for any tips,
grimholtz
p.s. is there anyway to subscribe to this thread so I get email notifications? I'm not familiar enough with Drupal
Howdy grimholtz. The only issue that might arise is if you are referencing a full path. As portable devices move PCs, the drive letter changes. So, if you're referencing the location of that file with a full path, that would be the issue. If you can somehow reference that file relative to the profile directory, that would be the better option. I don't know enough about Firefox extension development to know how difficult that would be.
As for monitoring, you can't get notifications for responses just yet (though I'm working on it) but you can monitor the Portable Firefox Support Forum by watching its RSS Feed.
Thanks for taking the time to make your extension PFF-friendly 
Hi John,
Saw your name in the torpark splashscreen, IIRC. Nice to meet you. FYI, Steven Topletz has expressed interest in bundling FoxyProxy with torpark.
Anyway, foxyproxy stores the location of the settings file with an absolute path, even though it derives that path relative to the profile directory. Is that still a problem? For instance, if the profile dir is:
X:\Documents and Settings\grimholtz\Application Data\Mozilla\Firefox\Profiles\61x84apv.myprofile
where 
is the USB drive, shouldn't this work? I guess I should first ask how extensions are installed on PFF? I need to just install it, I suppose.
Yeah, I redid sections of the standard Portable Firefox launcher to help integrate Tor into the launch process to make TorPark a more integrated experience. I actually owe Steve an email, actually...
If you generate that full path on each launch, then you're ok. If not, then you have an issue. The profile with Portable Firefox is self-contained. By default, it's in PortableFirefox\Data\profile. If you install in the root of your portable drive, that path might be X:\PortableFirefox\Data\profile on your home PC. But at work, that path might be F:\PortableFirefox\Data\profile. And, if you were to rearrange directories, that path might become F:\PortableApps\PortableFirefox\Data\profile. So, if you generate that path at runtime on each launch, you're fine. If, however, you store a full path between sessions, it will fail as the path changes. Make sense?
Yes, thanks.
Hi,
As foxyproxy developer, I'm not only trying to get foxyproxy to work with PFF, but I'm also trying to make my the PFF profile my development environment.
My USB drive is E: so here's what I've done:
Copy my development environment to:
1. e:\dev\foxyproxy\src. This directory has install.rdf, chrome.manifest, chrome/, components/, content/, defaults/, locale/, skin/, etc.
2. Create file named foxyproxy@eric.h.jung (this is the extension's ID) in E:\PortableFirefox\Data\profile\extensions. The contents of this file are: e:\dev\foxyproxy\src
When I restart PFF, there's no indication that my extension has been registered. Any advice?
Thanks,
grimholtz
edit: nevermind, it seems to work now.
Visit the Community page
Join our forums
Follow us on BlueSky