want to install chrome extension when mac app is installed.
i followed the instructions on the developer site of chrome Other Deployment Options
Tried both the methods
Local file url
Created file external_extensions.json at path /Users/Sadiq/Library/Application Support/Google/Chrome/External Extensions with contents
{
"external_crx": "/home/share/extension.crx",
"external_version": "1.0"
}
But when i restarted chrome the extension at that path is not installed on chrome.
Store Installation:
Created file fhbjgbiflinjbdggehcddcbncdddomop.json at path
/Users/Sadiq/Library/Application Support/Google/Chrome/External Extensions
with contents
{
"fhbjgbiflinjbdggehcddcbncdddomop": {
"external_update_url": "http://test.com/extension_info.xml"
}
}
Created extension_info.xml file at hosting with following code
<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
<app appid='fhbjgbiflinjbdggehcddcbncdddomop'>
<updatecheck codebase='https://clients2.googleusercontent.com/crx/blobs/QgAAAC6zw0qH2D JtnXe8Z7rUJP0d-cjv- 4fr0OfD1rZlXmwxm1zzQqbU1RRtbPRUspFh5VJIFInV7jQnzNI5Ax7-tVFFNKUqiQdoiA- 43Tdd46i1AMZSmuUS-XRXhbdPB5d5cMLUhLCthCuF7g/extension_1_0_0_26.crx' version='1.0.0.26' />
</app>
</gupdate>
But when i relaunch the chrome it must install the extension given in the manefest file .At first time it works but when i uninstall the extension and relaunch the browser it doesn't install it again. no oter changes are done
I want to install firefox extension on my mac app install .
Thanks
Sadiq
At first time it works but when i uninstall the extension and relaunch the browser it doesn't install it again.
This is intentional. When programmatically installed extension is uninstalled by the user, it becomes blacklisted and will not trigger installation again.
The user can still manually install it from the store, but there's nothing you can do if it was denied.
Related
I found the question How to install Firefox addon from command line in scripts? that seems to work for Firefox extensions (i.e. ones with an install.rdf file) but what about WebExtensions (extension with a manifest.json file instead)?
Please see:
Installing extensions
Customizing Firefox: Including extensions with your distribution of Firefox
The question you link on askubuntu: How to install Firefox addon from command line in scripts? is several years out of date, but does have some good information.
At this point, most Mozilla add-ons, including all Firefox WebExtension add-ons, are installed manually by placing the add-on's .xpi file in the appropriate directory with the correct name for the extension without unpacking (unzipping) the contents. [You can also install them by downloading them in Firefox, drag-and-drop the .xpi onto Firefox/Thunderbird, etc.]
You can determine those add-ons that must be unpacked by unpacking the add-on's .xpi file and looking at the install.rdf file to see if it has <em:unpack>true</em:unpack>. All WebExtensions don't have this file and are installed without unpacking.
The .xpi file must be called [extensionID].xpi. You can find the extension ID from either the install.rdf file (non-WebExtension add-ons). In that file, you are looking for <em:id>ThisEntireStringIsTheAddOnsID</em:id>
For a WebExtension, the ID is in the manifest.json file under the applications property:
"applications": {
"gecko": {
"id": "ThisEntireStringIsTheAddOnsID"
}
},
For both of the above examples the .xpi file must be renamed to ThisEntireStringIsTheAddOnsID.xpi
If the install.rdf file includes <em:unpack>true</em:unpack>, then the files in the .xpi must be unpacked (unzipped) and placed in a subdirectory under the extensions directory. In the above install.rdf example (again WebExtensions are not unpacked), the directory would be named: ThisEntireStringIsTheAddOnsID
Extension directories:
The extension directories where you put the .xpi file or unpacked directory are (information partially copied from MDN):
For all users running a particular version of Firefox:
[Firefox install directory]/browser/extensions/
Firefox will ask the user to confirm installation of the add-on when that version of Firefox is run. The user will not have the ability to remove the extension, only disable it. The extension will not be automatically updated.
For all users running a particular version of Firefox:
[Firefox install directory]/distribution/extensions
The extension will be installed for all users/profiles the first time the profile is run with that version of Firefox. The extension will be copied into the profile's extensions directory and the user will be able to remove it in addition to disabling it. The user will not be asked to confirm installation. The extension copied to each profile will be automatically updated along with all other extensions installed for that profile. You should not unpack any .xpi files in this directory. If the file needs to be unpacked, it will be done automatically by Firefox when the extension is installed in each profile.
For a particular User's specific profile:
[profile directory]/extensions/
On Windows:
All profiles for a specific user:
<I>%appdata%\\Mozilla\\Extensions\\{ec8030f7-c20a-464f-9b0e-13a3a9e97384}\</I>
Profile directories are located at:
<i>\\Mozilla\\Firefox\\Profiles\\*</i>
OSX:
For all users:
/Library/Application Support/Mozilla/Extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
Just for a specific user, place it in that user's library folder hierarchy:
~/Library/Application Support/Mozilla/Extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
Linux:
For all users:
/usr/lib/Mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
or
/usr/lib64/Mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
or
/usr/share/Mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
Just for a specific user:
~/.Mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
NOTE:
The -install-global-extension option mentioned in the question/answer you linked was removed from Firefox as of Gecko 1.9.2 ( a long time ago).
I found the question How to install Firefox addon from command line in scripts? that seems to work for Firefox extensions (i.e. ones with an install.rdf file) but what about WebExtensions (extension with a manifest.json file instead)?
Please see:
Installing extensions
Customizing Firefox: Including extensions with your distribution of Firefox
The question you link on askubuntu: How to install Firefox addon from command line in scripts? is several years out of date, but does have some good information.
At this point, most Mozilla add-ons, including all Firefox WebExtension add-ons, are installed manually by placing the add-on's .xpi file in the appropriate directory with the correct name for the extension without unpacking (unzipping) the contents. [You can also install them by downloading them in Firefox, drag-and-drop the .xpi onto Firefox/Thunderbird, etc.]
You can determine those add-ons that must be unpacked by unpacking the add-on's .xpi file and looking at the install.rdf file to see if it has <em:unpack>true</em:unpack>. All WebExtensions don't have this file and are installed without unpacking.
The .xpi file must be called [extensionID].xpi. You can find the extension ID from either the install.rdf file (non-WebExtension add-ons). In that file, you are looking for <em:id>ThisEntireStringIsTheAddOnsID</em:id>
For a WebExtension, the ID is in the manifest.json file under the applications property:
"applications": {
"gecko": {
"id": "ThisEntireStringIsTheAddOnsID"
}
},
For both of the above examples the .xpi file must be renamed to ThisEntireStringIsTheAddOnsID.xpi
If the install.rdf file includes <em:unpack>true</em:unpack>, then the files in the .xpi must be unpacked (unzipped) and placed in a subdirectory under the extensions directory. In the above install.rdf example (again WebExtensions are not unpacked), the directory would be named: ThisEntireStringIsTheAddOnsID
Extension directories:
The extension directories where you put the .xpi file or unpacked directory are (information partially copied from MDN):
For all users running a particular version of Firefox:
[Firefox install directory]/browser/extensions/
Firefox will ask the user to confirm installation of the add-on when that version of Firefox is run. The user will not have the ability to remove the extension, only disable it. The extension will not be automatically updated.
For all users running a particular version of Firefox:
[Firefox install directory]/distribution/extensions
The extension will be installed for all users/profiles the first time the profile is run with that version of Firefox. The extension will be copied into the profile's extensions directory and the user will be able to remove it in addition to disabling it. The user will not be asked to confirm installation. The extension copied to each profile will be automatically updated along with all other extensions installed for that profile. You should not unpack any .xpi files in this directory. If the file needs to be unpacked, it will be done automatically by Firefox when the extension is installed in each profile.
For a particular User's specific profile:
[profile directory]/extensions/
On Windows:
All profiles for a specific user:
<I>%appdata%\\Mozilla\\Extensions\\{ec8030f7-c20a-464f-9b0e-13a3a9e97384}\</I>
Profile directories are located at:
<i>\\Mozilla\\Firefox\\Profiles\\*</i>
OSX:
For all users:
/Library/Application Support/Mozilla/Extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
Just for a specific user, place it in that user's library folder hierarchy:
~/Library/Application Support/Mozilla/Extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
Linux:
For all users:
/usr/lib/Mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
or
/usr/lib64/Mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
or
/usr/share/Mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
Just for a specific user:
~/.Mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
NOTE:
The -install-global-extension option mentioned in the question/answer you linked was removed from Firefox as of Gecko 1.9.2 ( a long time ago).
I upgraded to Rubymine 8 from 6.3. (I am using Ubuntu 12.04)
After upgrading I could not use the icon launcher and was getting the message
"could not execute child process /home/user...RubyMine-6.3/.."
So I was simply using sudo mine and that was working, but only partially. I could not see the code of the third party gems and I also could not setup my Settings >> Languages & Frameworks >> Ruby SDK and Gems. Apparantly Rubymine, on startup, should recognise the .rvmrc file and set this up automatically. But this was not happening for me.
To fix: I removed the old desktop launcher:
locate rubymine
look for the desktop launcher.. mine was in /home/username/.local/share/applications/jetbrains-rubymine.desktop
rm /home/username/.local/share/applications/jetbrains-rubymine.desktop
open Rubymine with sudo mine and click Tools >> Create Desktop Entry and check the Create entry for all users checkbox and click OK.
you may need to restart the computer.
Now the RubyMine desktop launcher works as it should, and upon first using it, the Rubymine setup ran and loaded the .rvmrc file as it was supposed to. So I can now see the code of the third party gems among other benefits.
Whenever I try to install the Visual Studio SDK I get the following error:
Windows Program Compatibility mode is on. Turn it off and then try Setup again.
I have checked and Compatibility mode is not turned on. From what I've read, renaming the installer to vssdk_full.exe should help. That hasn't had any impact.
I got the installer from Microsoft's website.
What do I need to do to get this to install?
Are you installing on Windows 10? If so, then I have the same problem and it seems as though the current SDK setup is checking the Windows version and 10 isn't currently supported. See https://social.technet.microsoft.com/Forums/en-US/77c61be0-1303-4040-a587-62843d321159/visual-studio-2013-sdk?forum=WinPreview2014General for more info
I have managed to get it to install on windows 10, download the sdk, it will download vssdk_full.exe, run this with /layout path which will extract the actual setup file.
Then set compatibility on the new file to win 8 and it will install just fine.
You might not need to do the/layout thing but that is what I did.
ed
I had the same problem. I downloaded .iso file with install package form the internet. Then I mounted it using PowerISO and tried to start it from virtual CD drive. It ended up in the same message as above.
I looked it up and thought that in Properties of .exe install file, it's enough to uncheck some boxes compability section. But nothing was checked.
Soon afterwards I unzipped the package to a temporary directory with PowerISO and installed Visual from there. Worked without problems.
I had this problem, I renamed the instalation file to "vssdk_full.exe" and it installed without problems.
I have followed the instructions here [MDC - Adding Extensions using the Windows Registry],
but haven't been able to get Firefox to automatically install my extension when I restart it.
I have written an application that is half windows service and half FF extension. I have built an installer and want it to be able to install the Firefox extension along with the service.
So far I have tried the following things:
Removing my dev version of the
extension from FF first
Removing the
pointer file to my dev version of the
extension from my profile dir
Removing my "dev" profile completelly
so that FF only has a "default"
profile
Running FF without the
-no-remote and -P switches I setup for the dev environment
Trying the
key in both HKEY_CURRENT_USER and
HKEY_LOCAL_MACHINE
Carefully checking
the ID and Paths I have used
Trying
Paths that don't include spaces
Trying the Paths in Quotes
Trying a
trailing \ at the end of the path
Trying the .xpi filename at the end of the path instead of just the dir name
Building the XPI using the Extension
Builder plugin instead of manually
(although my manual build would
install just fine if I dragged it to
FF)
I'm using FF3.5.2 on Windows 2003 Server
(could it be a W2K3 install security issue?)
UPDATE: Now tested also on WinXP FF3.0.11. Same problem.
OK. I figured it out myself! I miss-read one line of the instructions!!!
"the location of the unpacked XPI"
I must be losing my mind. For some reason I reread this as the "packed XPI" over and over!!!
(I feel very silly now)
The answer was to use the unpacked files in the install dir not the .xpi file.
I noticed that it's really important to have back-slash in the file path, ex: [TARGETDIR]Extension\Firefox\