Yeah, fragments do not work with the overlay. However, they can be tested by turning off the overlay, and they're helpful for people who don't use the overlay.

Anyway, the patch in #6 looks fine. Can someone give it a manual test to see that:
a) All the links go to where they should be going
b) The names of pages/sections mentioned in the help text match the actual names of the pages in the administrative UI... I guess the only one mentioned is on content editing it says "URL path settings" -- can it be verified that this is still what it says?

I gave this a manual test today and it all looks great except for one conceptual problem.

The "Creating" uses item says that you can create aliases when you create content. This is true for Nodes, but one of the examples it gives is for a user alias, and I am not seeing the ability to create an alias for a user page when I create the user page. With only the core User and Path modules, I think if you wanted to create an alias for user/3 you would need to do it from the alias list, not while you are creating the user.

And the field where you can add a URL alias on a Taxonomy term is not called the same thing. It just says "URL alias" instead of "URL path settings".

So I think this is a bit misleading. I'm not sure what the best way to fix it would be, and I'm not sure why the URL alias is not available for users and looks different for taxonomy terms either. Any comments from the Path maintainers?

This patch attempts to fix the problem raised in #12. The style is not very refined but I think it is clear and not misleading anymore. Suggestions for improvement are always welcome.

I don't think the labeling is different. In the case of the Node it is the "vertical tab label" (form element 'type'= '#details' ?) that is named "URL path settings". The actual input field for both taxo term and node are labeled URL alias.

So since the UI for the Path module changed (see comments above), we need someone to test this help manually again:
- Verify that all the links work
=====> Especially this: Verify that all mentions of pages/text within the UI match what is seen in the UI
- Verify that the formatting is OK.

@gnuget: I could not tell from your review in #30: did you find any problems, or did you think everything was fine? If everything is fine, please set the issue status to "Reviewed and tested by the community". If there is a problem, set it to "needs work" and explain what the problem is. Thanks!

All of the hook_help() implementations are being updated in this way for URLs. We discussed it a while back on the parent issue. We don't need URLs that are already generated with url() or a similar function/method to be further sanitized by check_plain(), so we're using !name rather than @name to put them in t() and similar methods.

@jhodgdon - The patch in #26 no longer applies in current core because all the suggested changes are already in core. Somebody has already committed these changes in core.

Although there is one small issue in the core Path module. As per the Help text standard at https://drupal.org/node/632280, the wording and link should be like "For more information, see the online documentation for the Path module."

Whereas currently in core, it is like "For more information, see the online documentation for the Path module."

Please see the attached patch which simply makes the link on "Path module" wording rather "see the online documentation for the Path module".