After Google Chrome 33, the installation of third-party plug-ins is blocked for security reasons. Although the installation can be successful after the developer mode is turned on, the prompt "Please disable the extension program running in developer mode" will appear every time the browser is started. The extension can only be used normally after clicking Cancel each time, This is a disaster for some excellent third-party plug-ins or some plug-ins modified by themselves.
Finally, it was found that under Windows, using group policy to add an extender white list masked this prompt. The operations are as follows:
1. First download the Chrome Group Policy Management Template chrome.adm Click Download
2. Then open the "Local Group Policy Editor" (execute gpedit.msc while running or open it in Control Panel Management Tools), right click "Add/Remove Template" in "Computer Configuration" - "Management Template" to install the chrome. adm file just now. After the installation is successful, you can install it in "Management Template" - "Classic Management Template (ADM)" - "Google" Here we see "Google Chrome". Two points need to be noted here. One is that there may be two Google Chrome under this one, one with the word "recommended", and see which one has "extension program" under it, usually the one without recommendation; Another point is that in the process of chrome.adm, if the policy editor stops responding for a long time, it can be forced to close it and then open it, without affecting subsequent operations.
3. Next, select "Extender" and double-click "Configure Extender Installation Whitelist" on the right, as shown in the following figure:
4. After opening, first select "Enabled" on the left, and then select the display button below. Enter the ID of the third-party plug-in after installation (displayed after opening the developer mode of Google Chrome) into the white list dialog box just now, and then confirm to save it.
In addition, it should be noted that in this case, "developer mode" needs to be always opened. In addition, if it is also invalid to load plug-ins directly in developer mode by loading the plug-in development directory, you can package them and then install them, but their IDs will change after packaging and then installing them.
reference material:
Prevent Chrome from blocking unofficial extensions tutorial
