I have put the two files FlashPlayerPlugin_17_0_0_169.exe, NPSWF32_17_0_0_169.dll in plugins directory but firefox doesn't detect it. If i go in the Plugins section in about:addons no flash plugin is listed. How to make it detect the plugin?
New: Run-Command (Dec 2, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads Nov/Dec!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Did you put it in FirefoxPortable\Data\plugins or in FirefoxPortable\App\Firefox\plugins? If you try one, please try the other and let us know which works for you.
Sometimes, the impossible can become possible, if you're awesome!
My plugins directory is in the Firefox directory and i don't use portable launcher, i just start firefox.exe with -profile parameter.
Is there any way from about:config to point the path to the plugins directory?
You need to use the launcher. It sets specific environment variables to cause Firefox to use FirefoxPortable\Data\plugins.
Running Firefox with -profile doesn't make it portable. It'll leave things behind on every PC.
Sometimes, the impossible can become possible, if you're awesome!
Using the launcher also sets -profile parameter for firefox.exe, and i am using Firefox locally so i am not concerned for what it leaves behind.
I thought Firefox natively would detect the plugins directory that is inside its directory, isn't that correct?
Support for that was dropped quite a long time ago.
Sometimes, the impossible can become possible, if you're awesome!
Does that mean the path to the plugins directory cannot be pointed from inside Firefox? I guess then this can be done only from the registry.
I have a question about Firefox profile manager and where it stores the data for the created profiles. I have three different Firefox version and profiles on different location on my hard disk. But if i start the profile manager with parameter firefox.exe -p from any Firefox version it lists all profiles and this is happening even if i delete all firefox related files in user data folders and in the registry.
Where the profile manager stores the data for the paths to the profiles if it is not in the registry and user data folders?
Profile manager puts its stuff in your Windows user account profile folders, under "AppData" (same place(s) locally-installed Firefox puts its [profile & non-executable] stuff).
While "portable" means different things to different people, none of the things you're asking about here relate to the Firefox Portable package from PA.c, but only to Firefox as it comes from Mozilla (locally-installed or from a .zip file [just unpacked and copied somewhere]). Firefox Portable doesn't use the profile manager (standalone or integrated with Mozilla applications).
Edit: You should be able to find the info you need at MDN: https://developer.mozilla.org/en-US/Add-ons/Plugins/Gecko_Plugin_API_Ref...
Thanks. I was using the portable Firefox from PortableApps but i don't like the limitation that it has concerning the usage of profile manager and running simultaneously different versions and profiles. And you can use the official Firefox release almost as portable, it leaves some traces in the Local user data folder but i don't think there is some sensitive information.
I use Firefox Portable. I have Firefox installed locally, but I don't use it. I run as many instances of Fx Portable as I want, at whatever release levels of each that I want. The launcher actually enables this--just use an .ini file with AllowMultipleInstances set to 'true' (which is the same as using -no-remote). As a rule, I don't use the PortableApps platform for Firefox Portable, however, because it really doesn't work as it should if you use that 'true' value (not that I'd call it a problem exactly). In ten years I've never actually found any use for multiple profiles, since I've always run multiple instances. I also copy Firefox Portable folders as part of my upgrade process, something else which is enabled by using the launcher (which wouldn't be nearly as simple without it).