Document the new external extensions path on Mac OS.

Document the new external extensions path on Mac OS.

Chnaged doc is here:

http://www.corp.google.com/~skerner/macPathFix/external_extensions.html

BUG=67203
TEST=See updated version at http://moma/~skerner/macPathFix/

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=103469

[kathyw, 2011-09-29 20:31:20]

Some copyedits, for clarity.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
File chrome/common/extensions/docs/static/external_extensions.html (right):

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:106: <p
class="note"><b>Note:</b> The external extensions file will only be read if
every directory in the path is owned by the user <code>root</code>, the group
<code>admin</code>, and is not world readable.  The path must also be free of
symbolic links.  These restrictions prevent an unprivileged user from causing
extensions to be installed for all users.  See <a
href="#troubleshooting">troubleshooting</a> for details.</p>
file will only be read if
->
file is valid only if

(move "only" closer to what it modifies, avoid future tense and passive voice)
(if you can think of a better word than "valid", go ahead and use it)

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:106: <p
class="note"><b>Note:</b> The external extensions file will only be read if
every directory in the path is owned by the user <code>root</code>, the group
<code>admin</code>, and is not world readable.  The path must also be free of
symbolic links.  These restrictions prevent an unprivileged user from causing
extensions to be installed for all users.  See <a
href="#troubleshooting">troubleshooting</a> for details.</p>
the group -> has the group

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:158: On Mac OS, if
you do not see the external extension installed when Chrome is launched, there
may be a permissions problem with the external extensions prefs file.  To see if
this is the problem, follow these steps:
prefs -> preferences

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:161: <li> Launch
the console program, under /Applications/Utilities/Console. </li>
console program, under
->
Console program. You can find it under

(make it a little clearer that the "under" phrase just says where to find it,
not  how to launch it)

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:162: <li> Click
<code>Console Messages</code> in the left pane. </li>
Insert a step above here that says something like:

<li> If the leftmost icon in the Console says "Show Log List", click that icon.
A second column appears at the left. </li>

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:163: <li> Search
for the string <code>Can not read external extensions</code>.  If there is a
problem reading the external extensions file, you will find an error message. 
Look for another error message directly above it, which should explain the
issue.  For example, if you see the following error:
change <code> to <b>?

<code> is pretty ugly.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:164: <code>Path
/Library/Application Support/Google/Chrome is owned by the wrong group.</code>,
you need to use <code>chgrp</code> or the Finder's Get Info dialog to make the
file owned by the Administrator group.</li>
Use quotation marks (double quotes) instead of <code> for "Path ... group", and
don't include the period, for readability.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:164: <code>Path
/Library/Application Support/Google/Chrome is owned by the wrong group.</code>,
you need to use <code>chgrp</code> or the Finder's Get Info dialog to make the
file owned by the Administrator group.</li>
make the file owned by the
->
change the file's owner to the

(this makes it harder to misread "by" as describing the file instead of the
action of changing ownership)

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:165: <li> After
fixing the issue, relaunch Chrome to try reading the external preferences file
again. </li>
Chrome to try
->
Chrome.</li>
<li> Test whether the external extension is now installed.

(It's easy to misread "to try reading", plus the important thing is testing the
installation, right?)

[Sam Kerner (Chrome), 2011-09-30 15:22:04]

Ready for another look.  The url in the issue has the changes in this patch.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
File chrome/common/extensions/docs/static/external_extensions.html (right):

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:106: <p
class="note"><b>Note:</b> The external extensions file will only be read if
every directory in the path is owned by the user <code>root</code>, the group
<code>admin</code>, and is not world readable.  The path must also be free of
symbolic links.  These restrictions prevent an unprivileged user from causing
extensions to be installed for all users.  See <a
href="#troubleshooting">troubleshooting</a> for details.</p>
On 2011/09/29 20:31:20, kathyw wrote:
> file will only be read if
> ->
> file is valid only if
> 
> (move "only" closer to what it modifies, avoid future tense and passive voice)
> (if you can think of a better word than "valid", go ahead and use it)

I went with "read" instead of "valid".

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:106: <p
class="note"><b>Note:</b> The external extensions file will only be read if
every directory in the path is owned by the user <code>root</code>, the group
<code>admin</code>, and is not world readable.  The path must also be free of
symbolic links.  These restrictions prevent an unprivileged user from causing
extensions to be installed for all users.  See <a
href="#troubleshooting">troubleshooting</a> for details.</p>
On 2011/09/29 20:31:20, kathyw wrote:
> the group -> has the group

Done.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:158: On Mac OS, if
you do not see the external extension installed when Chrome is launched, there
may be a permissions problem with the external extensions prefs file.  To see if
this is the problem, follow these steps:
On 2011/09/29 20:31:20, kathyw wrote:
> prefs -> preferences

Done.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:161: <li> Launch
the console program, under /Applications/Utilities/Console. </li>
On 2011/09/29 20:31:20, kathyw wrote:
> console program, under
> ->
> Console program. You can find it under
> 
> (make it a little clearer that the "under" phrase just says where to find it,
> not  how to launch it)

Done.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:162: <li> Click
<code>Console Messages</code> in the left pane. </li>
On 2011/09/29 20:31:20, kathyw wrote:
> Insert a step above here that says something like:
> 
> <li> If the leftmost icon in the Console says "Show Log List", click that
icon.
> A second column appears at the left. </li>
> 

Done.  Good catch.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:163: <li> Search
for the string <code>Can not read external extensions</code>.  If there is a
problem reading the external extensions file, you will find an error message. 
Look for another error message directly above it, which should explain the
issue.  For example, if you see the following error:
On 2011/09/29 20:31:20, kathyw wrote:
> change <code> to <b>?
> 
> <code> is pretty ugly.

Done.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:164: <code>Path
/Library/Application Support/Google/Chrome is owned by the wrong group.</code>,
you need to use <code>chgrp</code> or the Finder's Get Info dialog to make the
file owned by the Administrator group.</li>
On 2011/09/29 20:31:20, kathyw wrote:
> Use quotation marks (double quotes) instead of <code> for "Path ... group",
and
> don't include the period, for readability.

Done.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:164: <code>Path
/Library/Application Support/Google/Chrome is owned by the wrong group.</code>,
you need to use <code>chgrp</code> or the Finder's Get Info dialog to make the
file owned by the Administrator group.</li>
On 2011/09/29 20:31:20, kathyw wrote:
> make the file owned by the
> ->
> change the file's owner to the
> 
> (this makes it harder to misread "by" as describing the file instead of the
> action of changing ownership)

Done.

http://codereview.chromium.org/8084006/diff/2001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:165: <li> After
fixing the issue, relaunch Chrome to try reading the external preferences file
again. </li>
On 2011/09/29 20:31:20, kathyw wrote:
> Chrome to try
> ->
> Chrome.</li>
> <li> Test whether the external extension is now installed.
> 
> (It's easy to misread "to try reading", plus the important thing is testing
the
> installation, right?)

Done.

[kathyw, 2011-09-30 15:29:04]

I missed something before (<p> tag). Once that's fixed, LGTM.

-k-

http://codereview.chromium.org/8084006/diff/5001/chrome/common/extensions/doc...
File chrome/common/extensions/docs/static/external_extensions.html (right):

http://codereview.chromium.org/8084006/diff/5001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/external_extensions.html:158: On Mac OS, if
you do not see the external extension installed when Chrome is launched, there
may be a permissions problem with the external extensions preferences file.  To
see if this is the problem, follow these steps:

Oops, I missed one before: Add <p> tags around this paragraph.