Index: chrome/app/policy/policy_templates.json |
diff --git a/chrome/app/policy/policy_templates.json b/chrome/app/policy/policy_templates.json |
index c8138681167e392ddf4016388847a83ac49534a6..89a33db4ad2b2eec59f3e18f47654b033eb68861 100644 |
--- a/chrome/app/policy/policy_templates.json |
+++ b/chrome/app/policy/policy_templates.json |
@@ -3011,7 +3011,7 @@ |
'name': 'EnterpriseWebStoreURL', |
'type': 'string', |
'schema': { 'type': 'string' }, |
- 'supported_on': ['chrome.*:17-', 'chrome_os:0.17-'], |
+ 'supported_on': ['chrome.*:17-29', 'chrome_os:0.17-0.29'], |
'features': { |
'dynamic_refresh': True, |
'per_profile': True, |
@@ -3019,18 +3019,14 @@ |
'deprecated': True, |
'example_value': 'http://company-intranet/chromeapps', |
'id': 112, |
- 'caption': '''Enterprise web store URL''', |
- 'desc': '''Specifies the URL for the enterprise web store. When this setting is enabled, an app will appear on the new tab page which, when clicked, will take the user to the specified URL. To actually allow extension installation from the configured website, the ExtensionInstallSources policy must be configured to allow installation from the appropriate extension download URLs. If this policy is set, the EnterpriseWebStoreName setting should also be set. |
- |
- If this setting is disabled, no enterprise web store app will appear on the new tab page. |
- |
- This setting is deprecated as of version 27 and will be removed for future versions. The recommended way to set up organization-hosted extension/app collections is to include the site hosting the CRX packages in ExtensionInstallSources and put direct download links to the packages on a web page. A launcher for that web page can be created using the ExtensionInstallForcelist policy.''', |
+ 'caption': '''Enterprise web store URL (deprecated)''', |
+ 'desc': '''This setting has been retired as of <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> version 29. The recommended way to set up organization-hosted extension/app collections is to include the site hosting the CRX packages in ExtensionInstallSources and put direct download links to the packages on a web page. A launcher for that web page can be created using the ExtensionInstallForcelist policy.''', |
}, |
{ |
'name': 'EnterpriseWebStoreName', |
'type': 'string', |
'schema': { 'type': 'string' }, |
- 'supported_on': ['chrome.*:17-', 'chrome_os:0.17-'], |
+ 'supported_on': ['chrome.*:17-29', 'chrome_os:0.17-0.29'], |
'features': { |
'dynamic_refresh': True, |
'per_profile': True, |
@@ -3038,12 +3034,8 @@ |
'deprecated': True, |
'example_value': 'WidgCo Chrome Apps', |
'id': 113, |
- 'caption': '''Enterprise web store name''', |
- 'desc': '''The name of the enterprise web store, which will appear underneath the app icon on the new tab page. This setting has no effect if EnterpriseWebStoreURL is not set. |
- |
- If this setting is disabled, the enterprise web store app (if it exists) will be labeled with its URL. |
- |
- This setting is deprecated as of version 27 and will be removed for future versions. The recommended way to set up organization-hosted extension/app collections is to include the site hosting the CRX packages in ExtensionInstallSources and put direct download links to the packages on a web page. A launcher for that web page can be created using the ExtensionInstallForcelist policy.''', |
+ 'caption': '''Enterprise web store name (deprecated)''', |
+ 'desc': '''This setting has been retired as of <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> version 29. The recommended way to set up organization-hosted extension/app collections is to include the site hosting the CRX packages in ExtensionInstallSources and put direct download links to the packages on a web page. A launcher for that web page can be created using the ExtensionInstallForcelist policy.''', |
}, |
{ |
'name': 'EnableOriginBoundCerts', |