Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(89)

Issues Search
    My Issues | Starred     Open | Closed | All

Side by Side Diff: chrome/common/extensions/docs/external_extensions.html

Issue 8084006: Document the new external extensions path on Mac OS. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Rev comments Created 9 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | chrome/common/extensions/docs/static/external_extensions.html » ('j') | chrome/common/extensions/docs/static/external_extensions.html » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note: 1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note:
2 1) The <head> information in this page is significant, should be uniform 2 1) The <head> information in this page is significant, should be uniform
3 across api docs and should be edited only with knowledge of the 3 across api docs and should be edited only with knowledge of the
4 templating mechanism. 4 templating mechanism.
5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a 5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a
6 browser, it will be re-generated from the template, json schema and 6 browser, it will be re-generated from the template, json schema and
7 authored overview content. 7 authored overview content.
8 4) The <body>.innerHTML is also generated by an offline step so that this 8 4) The <body>.innerHTML is also generated by an offline step so that this
9 page may easily be indexed by search engines. 9 page may easily be indexed by search engines.
10 --><html xmlns="http://www.w3.org/1999/xhtml"><head> 10 --><html xmlns="http://www.w3.org/1999/xhtml"><head>
(...skipping 248 matching lines...) Expand 10 before | Expand all | Expand 10 after
259 <li> 259 <li>
260 <a href="#prereqs">Before you begin</a> 260 <a href="#prereqs">Before you begin</a>
261 <ol> 261 <ol>
262 <li style="display: none; "> 262 <li style="display: none; ">
263 <a>h3Name</a> 263 <a>h3Name</a>
264 </li> 264 </li>
265 </ol> 265 </ol>
266 </li><li> 266 </li><li>
267 <a href="#preferences">Using a preferences file</a> 267 <a href="#preferences">Using a preferences file</a>
268 <ol> 268 <ol>
269 <li style="display: none; "> 269 <li>
270 <a>h3Name</a> 270 <a href="#troubleshooting">Troubleshooting Mac OS permissions problems</a>
271 </li> 271 </li>
272 </ol> 272 </ol>
273 </li><li> 273 </li><li>
274 <a href="#registry">Using the Windows registry</a> 274 <a href="#registry">Using the Windows registry</a>
275 <ol> 275 <ol>
276 <li style="display: none; "> 276 <li style="display: none; ">
277 <a>h3Name</a> 277 <a>h3Name</a>
278 </li> 278 </li>
279 </ol> 279 </ol>
280 </li><li> 280 </li><li>
(...skipping 145 matching lines...) Expand 10 before | Expand all | Expand 10 after
426 426
427 </p> 427 </p>
428 428
429 <ol> 429 <ol>
430 <li>If you are installing from a file, make the <code>.crx</code> extension 430 <li>If you are installing from a file, make the <code>.crx</code> extension
431 file available to the machine you want to install the extension on. 431 file available to the machine you want to install the extension on.
432 (Copy it to a local directory or to a network share for example, 432 (Copy it to a local directory or to a network share for example,
433 <code>\\server\share\extension.crx</code> 433 <code>\\server\share\extension.crx</code>
434 or <code>/home/share/extension.crx</code>.) 434 or <code>/home/share/extension.crx</code>.)
435 </li> 435 </li>
436 <li>Locate the <code>external_extensions.json</code> file 436 <li>Locate the <code>external_extensions.json</code> file.
437 under the Google Chrome installation directory.
438 If the file doesn't exist, create it. 437 If the file doesn't exist, create it.
439 The location depends on the operating system. 438 The location depends on the operating system.
440 <dl> 439 <dl>
441 <dt> Windows: </dt> 440 <dt> Windows: </dt>
442 <dd> <code><em>chrome_root</em>\Application\<em>chrome_version</em>\Extensio ns\</code> 441 <dd> <code><em>chrome_root</em>\Application\<em>chrome_version</em>\Extensio ns\</code>
443 <br> 442 <br>
444 Example: <code>c:\Users\Me\AppData\Local\Google\Chrome\Application\6.0.422.0 \Extensions\</code> 443 Example: <code>c:\Users\Me\AppData\Local\Google\Chrome\Application\6.0.422.0 \Extensions\</code>
445 </dd> 444 </dd>
446 <dt> Mac OS X: </dt> 445 <dt> Mac OS X: </dt>
447 <dd> <code>/Applications/Google Chrome.app/Contents/Extensions/</code> </dd> 446 <dd> <code>/Library/Application Support/Google/Chrome/External Extensions/</ code> </dd>
447 <p class="note"><b>Note:</b> The external extensions file is read only if ev ery directory in the path is owned by the user <code>root</code>, has the group <code>admin</code>, and is not world readable. The path must also be free of sy mbolic links. These restrictions prevent an unprivileged user from causing exte nsions to be installed for all users. See <a href="#troubleshooting">troublesho oting</a> for details.</p>
448 <p class="note">
449 <b>Note:</b> The above path was added in Chrome 16. Prior versions used a d ifferent path, which is now deprecated:
450 <code>/Applications/Google Chrome.app/Contents/Extensions/</code> .</p>
448 <dt> Linux: </dt> 451 <dt> Linux: </dt>
449 <dd> <code>/opt/google/chrome/extensions/</code> <br> 452 <dd> <code>/opt/google/chrome/extensions/</code> <br>
450 <b>Note:</b> Use <code>chmod</code> if necessary 453 <b>Note:</b> Use <code>chmod</code> if necessary
451 to make sure that <code>extensions/external_extensions.json</code> 454 to make sure that <code>extensions/external_extensions.json</code>
452 is world-readable. 455 is world-readable.
453 </dd> 456 </dd>
454 </dl> 457 </dl>
455 </li> 458 </li>
456 <li> Add an entry to <code>external_extensions.json</code> 459 <li> Add an entry to <code>external_extensions.json</code>
457 for your extension's ID. If you are installing from a file, specify the 460 for your extension's ID. If you are installing from a file, specify the
(...skipping 26 matching lines...) Expand all
484 "external_update_url": "http://myhost.com/mytestextension/updates.xml" 487 "external_update_url": "http://myhost.com/mytestextension/updates.xml"
485 } 488 }
486 }</pre> 489 }</pre>
487 </li> 490 </li>
488 491
489 <li>Save the JSON file. </li> 492 <li>Save the JSON file. </li>
490 <li>Launch Google Chrome and go to <b>chrome://extensions</b>; 493 <li>Launch Google Chrome and go to <b>chrome://extensions</b>;
491 you should see the extension listed. </li> 494 you should see the extension listed. </li>
492 </ol> 495 </ol>
493 496
497 <h3 id="troubleshooting">Troubleshooting Mac OS permissions problems</h3>
498
499 On Mac OS, if you do not see the external extension installed when Chrome is lau nched, there may be a permissions problem with the external extensions preferenc es file. To see if this is the problem, follow these steps:
500
501 <ol>
502 <li> Launch the Console program. You can find it under /Applications/Utilitie s/Console. </li>
503 <li> If the leftmost icon in the Console says "Show Log List", click that icon . A second column appears at the left. </li>
504 <li> Click "Console Messages" in the left pane. </li>
505 <li> Search for the string <b>Can not read external extensions</b>. If there is a problem reading the external extensions file, you will find an error messag e. Look for another error message directly above it, which should explain the i ssue. For example, if you see the following error:
506 "Path /Library/Application Support/Google/Chrome is owned by the wrong grou p", you need to use <code>chgrp</code> or the Finder's Get Info dialog to change the directory's group owner to the Administrator group.</li>
507 <li> After fixing the issue, relaunch Chrome. Test that the external extensio n is now installed. It is possible that one permissions error keeps Chrome from detecting a second error. If the external extension was not installed, repeat these steps until you do not see an error in the Console application.
508 </li></ol>
509
494 <h2 id="registry">Using the Windows registry</h2> 510 <h2 id="registry">Using the Windows registry</h2>
495 511
496 <ol> 512 <ol>
497 <li>Make the <code>.crx</code> extension file available 513 <li>Make the <code>.crx</code> extension file available
498 to the machine you want to install the extension on. 514 to the machine you want to install the extension on.
499 (Copy it to a local directory or to a network share — 515 (Copy it to a local directory or to a network share —
500 for example, <code>\\server\share\extension.crx</code>.) 516 for example, <code>\\server\share\extension.crx</code>.)
501 </li> 517 </li>
502 <li>Find or create the following key in the 518 <li>Find or create the following key in the
503 registry: 519 registry:
(...skipping 316 matching lines...) Expand 10 before | Expand all | Expand 10 after
820 _uff=0; 836 _uff=0;
821 urchinTracker(); 837 urchinTracker();
822 } 838 }
823 catch(e) {/* urchinTracker not available. */} 839 catch(e) {/* urchinTracker not available. */}
824 </script> 840 </script>
825 <!-- end analytics --> 841 <!-- end analytics -->
826 </div> 842 </div>
827 </div> <!-- /gc-footer --> 843 </div> <!-- /gc-footer -->
828 </div> <!-- /gc-container --> 844 </div> <!-- /gc-container -->
829 </body></html> 845 </body></html>
OLDNEW
« no previous file with comments | « no previous file | chrome/common/extensions/docs/static/external_extensions.html » ('j') | chrome/common/extensions/docs/static/external_extensions.html » ('J')

Powered by Google App Engine
This is Rietveld 408576698