README.txt 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. Please read this file and also the INSTALL.txt.
  2. They contain answers to many common questions.
  3. If you are developing for this module, the API.txt may be interesting.
  4. If you are upgrading, check the CHANGELOG.txt for major changes.
  5. ** Description:
  6. The Pathauto module provides support functions for other modules to
  7. automatically generate aliases based on appropriate criteria, with a
  8. central settings path for site administrators.
  9. Implementations are provided for core entity types: content, taxonomy terms,
  10. and users (including blogs and forum pages).
  11. Pathauto also provides a way to delete large numbers of aliases. This feature
  12. is available at Administer > Configuration > Search and metadata > URL aliases
  13. > Delete aliases.
  14. ** Benefits:
  15. Besides making the page address more reflective of its content than
  16. "node/138", it's important to know that modern search engines give
  17. heavy weight to search terms which appear in a page's URL. By
  18. automatically using keywords based directly on the page content in the URL,
  19. relevant search engine hits for your page can be significantly
  20. enhanced.
  21. ** Installation AND Upgrades:
  22. See the INSTALL.txt file.
  23. ** Notices:
  24. Pathauto just adds URL aliases to content, users, and taxonomy terms.
  25. Because it's an alias, the standard Drupal URL (for example node/123 or
  26. taxonomy/term/1) will still function as normal. If you have external links
  27. to your site pointing to standard Drupal URLs, or hardcoded links in a module,
  28. template, content or menu which point to standard Drupal URLs it will bypass
  29. the alias set by Pathauto.
  30. There are reasons you might not want two URLs for the same content on your
  31. site. If this applies to you, please note that you will need to update any
  32. hard coded links in your content or blocks.
  33. If you use the "system path" (i.e. node/10) for menu items and settings like
  34. that, Drupal will replace it with the url_alias.
  35. For external links, you might want to consider the Path Redirect or
  36. Global Redirect modules, which allow you to set forwarding either per item or
  37. across the site to your aliased URLs.
  38. URLs (not) Getting Replaced With Aliases:
  39. Please bear in mind that only URLs passed through Drupal's l() or url()
  40. functions will be replaced with their aliases during page output. If a module
  41. or your template contains hardcoded links, such as 'href="node/$node->nid"'
  42. those won't get replaced with their corresponding aliases. Use the
  43. Drupal API instead:
  44. * 'href="'. url("node/$node->nid") .'"' or
  45. * l("Your link title", "node/$node->nid")
  46. See http://api.drupal.org/api/HEAD/function/url and
  47. http://api.drupal.org/api/HEAD/function/l for more information.
  48. ** Disabling Pathauto for a specific content type (or taxonomy)
  49. When the pattern for a content type is left blank, the default pattern will be
  50. used. But if the default pattern is also blank, Pathauto will be disabled
  51. for that content type.
  52. ** Credits:
  53. The original module combined the functionality of Mike Ryan's autopath with
  54. Tommy Sundstrom's path_automatic.
  55. Significant enhancements were contributed by jdmquin @ www.bcdems.net.
  56. Matt England added the tracker support (tracker support has been removed in
  57. recent changes).
  58. Other suggestions and patches contributed by the Drupal community.
  59. Current maintainers:
  60. Dave Reid - http://www.davereid.net
  61. Greg Knaddison - http://www.knaddison.com
  62. Mike Ryan - http://mikeryan.name
  63. Frederik 'Freso' S. Olesen - http://freso.dk