-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deploying settings #28
Comments
Some more info: |
Regarding automatic installation for deployment, you should be able to use the ExtensionInstallForcelist policy. I was able to automatically install chromium-web-store alongside Chrome using this .reg file:
A couple caveats (that can most likely be avoided, I just don't know how):
Automatically setting options is a different matter. Currently you can either edit the LevelDB file used to store extension data or edit the extension source code (if installing from file), neither of which are ideal. I will work on implementing something similar to uBlock's solution. |
I added policy management for chromium-web-store options similar to µBlock, please give it a try with the latest crx and let me know if it works as expected. For your particular case you can set the policy using this .reg file:
Note that these policy settings will override any settings the user attempts to change; in this case meaning the user will never be able to enable auto-updates or un-ignore the extensions you specify. Other options you do not modify can be changed by the user. |
Wow, I must say I'm amazed at your speed. Thank you so very much!
It works great. |
I have tried this, just yet. Before I tried the ExtensionSettings option. It doesn't work for me, and I think I know the reason. This turns into a nice little caveat: can't use the ExtensionInstallForcelist setting before chromium-web-store has been installed. Can't use it after chromium-web-store has been installed either, because the profile then exists, and chromium ignores this policy setting then. (Of course, why it doesn't work for existing profiles seems like a bit dumb to me.) If however your computer also isn't joined to a domain, I would like to know. Thanks again! |
As far as I know my computer is not a member of a domain. I also tried reinstalling Chrome and this time the extension was not automatically installed (checking |
Yeah, I should move away from windows :) Thanks, I'll close this issue. |
or I can't close it myself? |
I believe you can, but I'm not very familiar with GitHub myself. |
I'm in the process of deploying chromium. I would like to deploy a few settings for all users. With another extension (uBlock) this is documented. I have this working with chromium and this extension.
Is there a way to set some settings for chromium-web-store? I would like to disable automatic updates, and ignore an extension.
At the moment I have a registry setting that installs this extension from a local file. Maybe this only works for a new profile, but this does not matter to me. I have tried using update_url, but couldn't get it to work. So now version 1.0.2 is installed from local, a newer version is available, but updating this does not work.
Some context:
working (with 32-bit redirection, so there is some SYSWOW64 stuff in there!):
not working (this also does not work for uBlock, which uses the standard update_url):
For uBlock I can set settings like this (don't copy this as a reg file, this is from the script I work with):
This last thing works.
Now is there something like that possible/available for chromium-web-store which sets the options of the extension itself?
The text was updated successfully, but these errors were encountered: