You are here

README.txt in Nodewords: D6 Meta Tags 6

Same filename and directory in other branches
  1. 5 README.txt
  2. 6.3 README.txt
  3. 6.2 README.txt
Nodewords: The Drupal 6 Meta Tags module
----------------------------------------

This module allows you to set some meta tags for the different content
available on your site, including nodes, users, views, taxonomy filters and
error pages.

Giving more attention to the important keywords and/or description on your site
may help you to get better positioning within public search engines.

This version of the module only works with Drupal 6.x.


Features
------------------------------------------------------------------------------
The primary features include:

* The current supported basic meta tags are ABSTRACT, CANONICAL, GEO.POSITION,
  DESCRIPTION, ICBM, KEYWORDS, REVISIT-AFTER, RIGHTS, ROBOTS, in addition
  to the TITLE tag.

* The Dublin Core meta tag schema may be added by enabling the "Nodewords
  extra meta tags" module.

* The Open Graph Protocol meta tags, as used by Facebook, may be added by
  enabling the "Open Graph meta tags" module (see below).

* A pluggable system allow the inclusion of new meta tags in addition to the
  ones provided by this module.

* Meta tags can be assigned site-wide defaults and then overridden on a
  per-node, per-tag and per-path basis.

* It is possible to control which of the available tags will be available for
  editing versus only using the previously configured values.

* All text of the DESCRIPTION and KEYWORDS meta tags are added to the search
  system so they are searchable too; other meta tags could be added to the
  search system too (depending on the code implemented from the module).


Integration with other modules
------------------------------------------------------------------------------
Nodewords integrates with other modules for automatic selection of meta tags.

* On node pages all terms of specified vocabularies associated can be added to
  the KEYWORDS meta tag.

* On node pages the DESCRIPTION meta tag can be automatically generated from
  the node's teaser or body text.

* On taxonomy pages, the term description is used as the meta tag DESCRIPTION.
  The term itself is added to the list of KEYWORDS. You can override the
  description to use, if you wish.

* Previous versions of this module provided support for Views and Panels. This
  feature has been removed from Nodewords 6.x-1.x (since August 15, 2009) as
  the module now provides an API allowing other modules to integrate with it.

* This module may also integrate with Tagadelic, CCK, and others.

* The Meta tags Node Type module [1] allows defaults to be assigned to each
  content type, which can then be overridden on individual nodes.

* The Domain Meta module [2] provides integration with the Domain Access
  module [3].


Installing Nodewords (first time installation)
------------------------------------------------------------------------------
 1. Backup your database.

 2. Copy the module as normal.
   More information about installing contributed modules could be found at
   "Install contributed modules" [4].

 3. Enable the "Nodewords" module from the module administration page
   (Administer >> Site configuration >> Modules).

 4. Enable other modules which provide meta tags. The following are included:
    - Nodewords basic meta tags: for "abstract", "canonical", "description",
      "keywords", "logo", "original-source", "revisit-after", "rights",
      "robots", and "standout" meta tags, and the "title" HTML tag.
    - Nodewords extra meta tags: for Dublin Core, "geo.placename",
      "geo.position", "geo.region", "icbm" and "shorturl" meta tags.
    - Nodewords Open Graph meta tags: for the Open Graph Protocol meta tags,
      used for integration with Facebook's API.

 5. Configure the module (see "Configuration" below).


Updating Nodewords (module version upgrade)
------------------------------------------------------------------------------
 1. Verify that the version you are going to upgrade contains all the features
    your are using in your Drupal setup. Some features could have been removed
    or replaced by others.

 2. Backup your database.

 3. Update current module code with latest recommended version. Previous
    versions could have bugs already reported and fixed in the last version.

 4. Complete the update process: set the site into maintenance mode, visit the
    update.php script and finish the update operation. For more information
    please see: http://groups.drupal.org/node/19513

 5. Verify your module configuration and check that the features you are using
    work as expected. Also verify that all required modules are enabled, and
    permissions are set as desired.

Note: Whenever you have the chance, try an update in a local or development
      copy of your site.


Configuration
------------------------------------------------------------------------------
 1. On the access control administration page ("Administer >> User management
    >> Access control") you need to assign:

    - The "administer meta tags" permission to the roles that are allowed to
      administer the meta tags (such as setting the default values and/or
      enabling the possibility to edit them),

    - The "edit XYZ tag" permission to the roles that are allowed to set and
      edit meta tags for the content (there is a permission for each of the
      meta tags currently defined).

    All users will be able to see the assigned meta tags.

 2. On the settings page ("Administer >> Content management >> Meta tags") you
    can specify the default settings for the module. To access this page users
    need the "administer meta tags" permission.

 3. Enable specific meta tags for editing before they are available for use by
    users who do not have the "administer meta tags" permission.

 4. The front page is an important page for each website, therefore you can
    specifically set the meta tags to use on the front page meta tags settings
    page ("Administer >> Content management >> Meta tags >> Default and
    specific meta tags >> Front page"). Users need the "administer meta tags"
    permission to do this. When there are resources providing meta tags
    promoted in the front page, you may force the usage of "Front page" meta
    tags superseding all of them.

    Alternatively, you can opt not to set the meta tags for the front page on
    this page, but to use the meta tags of the node, term or other page the
    used to control the front page. To do this, uncheck the "Use front page
    meta tags" option on the main settings page.

    Note that, in contrast to previous versions of this module, the site
    mission and/or site slogan are no longer used as DESCRIPTION or ABSTRACT
    on the front page!

 5. Each content type should be configured to control whether certain meta tags
    should be automatically generated, e.g. the "description" tag can be
    automatically taken from the node teaser.


Open Graph Protocol Extra Steps
------------------------------------------------------------------------------
Because of a limitation in Drupal 6, if the Open Graph meta tags module is
enabled the site's theme will have to be customized. In order to work
correctly, and pass XHTML validation, the page.tpl.php for any theme(s) in use
must to be customized to add the following attribute to the HTML tag:

  prefix="og: http://ogp.me/ns#"

As an example, to make it work with the Garland theme the HTML tag must be
changed to the following:

  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="<?php print $language->language ?>" lang="<?php print $language->language ?>" dir="<?php print $language->dir ?>" prefix="og: http://ogp.me/ns#">

Unless this change is made the page output will fail XHTML validation and the
Open Graph meta tags may not be properly identified by Facebook.


Using With non-PHPTemplate Themes (Chameleon, Marvin)
------------------------------------------------------------------------------
Because Nodewords depends upon PHPTemplate hooks in order to output the meta
tags it will not work with themes that do not use that template engine, e.g.
the core Chameleon or Marvin themes. In order for these to work a Nodewords
function must be called so it can insert the necessary tags into Drupal's
internal list of head tags. To insert the tags, edit the main theme file, e.g.
chameleon.theme, and insert the following at the top of the hook_page()
implementation, e.g. chameleon_page:

function chameleon_page($content, $show_blocks = TRUE, $show_messages = TRUE) {
  /**
   * Start Nodewords Changes.
   */
  // Allow Nodewords to add its tags to the internal HTML head tags array.
  if (module_exists('nodewords')) {
    $vars = array();
    nodewords_preprocess_page($vars);
  }
  /**
   * End Nodewords Changes.
   */

Once that is added the tags will be inserted into the HTML output as expected.


Known Issues
------------------------------------------------------------------------------
* Meta tags cannot be output with non-PHPTemplate themes like Chameleon or
  Marvin without customization (see above).
* Use of the Open Graph meta tags sub-module requires customizing the
  page.tpl.php file for the site's theme(s) (see above for details).
* Versions 6.x-1.9, 6.x-1.10 and 6.x-1.11 had a severe bug that could cause
  data loss when updating from 6.x-1.8 or older. The problem was in how
  nodewords_update_6162() changed the format of the 'id' field, causing records
  with an 'id' (nid, tid, uid) over 65,536 to be lost. The bug has been fixed
  in this release but any data lost as a result of this bug is irretrievable.
  The maintainers are terribly sorry about this and humbly apologize if your
  site(s) suffered data loss as a result of this and vow to do our utmost to
  ensure errors of this magnitude never happen again.
* Many of the code & API changes from the 6.x-1.12-x development cycle have
  been reverted; modules that integrate with the Nodewords APIs will have to
  be updated accordingly.
* Nodewords currently does not support tokens, that functionality was lost
  when the 6.x-1.12-x codebase was reverted. Adding Token support is planned
  for a future release: http://drupal.org/node/1380362
* If ThemeKey stops changing the theme after Nodewords is enabled, the problem
  is with another module and can be resolved by adjusting the ThemeKey module's
  weight in the 'system' table. See https://drupal.org/node/754970 for more
  details.


Related modules
------------------------------------------------------------------------------
Some modules are available that extend Nodewords with additional functionality:

* Domain Meta Tags, by Katrin Silvius
  http://drupal.org/project/domain_meta
  Integrates with the Domain Access module, so each site of a multi-domain
  install can separately control their meta tags.

* Meta tags Node Type, by Ariel Barreiro
  http://drupal.org/project/nodewords_nodetype
  Allows meta tag defaults to be controlled by content type, not just globally
  and per node.

* SEO Friend, by Kristen Pol
  http://drupal.org/project/seo_friend
  Provides some assistance with ensuring that meta tags are all properly
  assigned, which can be very useful for SEO beginners.

* Nodewords Meta Title, by Zoltán Adamek
  http://drupal.org/project/nodewords_meta_title
  Adds the <meta name="title" /> tag, which maybe be useful for some rare
  scenarios.


Credits / Contact
------------------------------------------------------------------------------
The current maintainer is Damien McKenna [5].

The original author of this module is Andras Barthazi. Mike Carter [6],
Gabor Hojtsy [7] and Robrecht Jacques [8] provided some feature enhancements,
while Alberto Paderno [9] maintained the module for much of its Drupal 6
lifecycle. Dave Reid [10] contributed greatly to the launch of v6.x-1.13, and
Nate Haug [11] played an instrumental role in deciding to scrap the ill-
conceived v6.x-1.12 release.

Development is currently sponsored by Media Current [12], previous sponsors
include Bluespark Labs [13] and others.

The best way to contact the authors is to submit an issue, be it a support
request, a feature request or a bug report, in the project issue queue:
  http://drupal.org/project/issues/nodewords


References
------------------------------------------------------------------------------
[1] http://drupal.org/project/nodewords_nodetype
[2] http://drupal.org/project/domain_meta
[3] http://drupal.org/project/domain
[4] http://drupal.org/documentation/install/modules-themes/modules-5-6
[5] http://drupal.org/user/108450
[6] http://drupal.org/user/13164
[7] http://drupal.org/user/4166
[8] http://drupal.org/user/22598
[9] http://drupal.org/user/55077
[10] http://drupal.org/user/53892
[11] http://drupal.org/user/35821
[12] http://www.mediacurrent.com/
[13] http://www.bluesparklabs.com/

File

README.txt
View source
  1. Nodewords: The Drupal 6 Meta Tags module
  2. ----------------------------------------
  3. This module allows you to set some meta tags for the different content
  4. available on your site, including nodes, users, views, taxonomy filters and
  5. error pages.
  6. Giving more attention to the important keywords and/or description on your site
  7. may help you to get better positioning within public search engines.
  8. This version of the module only works with Drupal 6.x.
  9. Features
  10. ------------------------------------------------------------------------------
  11. The primary features include:
  12. * The current supported basic meta tags are ABSTRACT, CANONICAL, GEO.POSITION,
  13. DESCRIPTION, ICBM, KEYWORDS, REVISIT-AFTER, RIGHTS, ROBOTS, in addition
  14. to the TITLE tag.
  15. * The Dublin Core meta tag schema may be added by enabling the "Nodewords
  16. extra meta tags" module.
  17. * The Open Graph Protocol meta tags, as used by Facebook, may be added by
  18. enabling the "Open Graph meta tags" module (see below).
  19. * A pluggable system allow the inclusion of new meta tags in addition to the
  20. ones provided by this module.
  21. * Meta tags can be assigned site-wide defaults and then overridden on a
  22. per-node, per-tag and per-path basis.
  23. * It is possible to control which of the available tags will be available for
  24. editing versus only using the previously configured values.
  25. * All text of the DESCRIPTION and KEYWORDS meta tags are added to the search
  26. system so they are searchable too; other meta tags could be added to the
  27. search system too (depending on the code implemented from the module).
  28. Integration with other modules
  29. ------------------------------------------------------------------------------
  30. Nodewords integrates with other modules for automatic selection of meta tags.
  31. * On node pages all terms of specified vocabularies associated can be added to
  32. the KEYWORDS meta tag.
  33. * On node pages the DESCRIPTION meta tag can be automatically generated from
  34. the node's teaser or body text.
  35. * On taxonomy pages, the term description is used as the meta tag DESCRIPTION.
  36. The term itself is added to the list of KEYWORDS. You can override the
  37. description to use, if you wish.
  38. * Previous versions of this module provided support for Views and Panels. This
  39. feature has been removed from Nodewords 6.x-1.x (since August 15, 2009) as
  40. the module now provides an API allowing other modules to integrate with it.
  41. * This module may also integrate with Tagadelic, CCK, and others.
  42. * The Meta tags Node Type module [1] allows defaults to be assigned to each
  43. content type, which can then be overridden on individual nodes.
  44. * The Domain Meta module [2] provides integration with the Domain Access
  45. module [3].
  46. Installing Nodewords (first time installation)
  47. ------------------------------------------------------------------------------
  48. 1. Backup your database.
  49. 2. Copy the module as normal.
  50. More information about installing contributed modules could be found at
  51. "Install contributed modules" [4].
  52. 3. Enable the "Nodewords" module from the module administration page
  53. (Administer >> Site configuration >> Modules).
  54. 4. Enable other modules which provide meta tags. The following are included:
  55. - Nodewords basic meta tags: for "abstract", "canonical", "description",
  56. "keywords", "logo", "original-source", "revisit-after", "rights",
  57. "robots", and "standout" meta tags, and the "title" HTML tag.
  58. - Nodewords extra meta tags: for Dublin Core, "geo.placename",
  59. "geo.position", "geo.region", "icbm" and "shorturl" meta tags.
  60. - Nodewords Open Graph meta tags: for the Open Graph Protocol meta tags,
  61. used for integration with Facebook's API.
  62. 5. Configure the module (see "Configuration" below).
  63. Updating Nodewords (module version upgrade)
  64. ------------------------------------------------------------------------------
  65. 1. Verify that the version you are going to upgrade contains all the features
  66. your are using in your Drupal setup. Some features could have been removed
  67. or replaced by others.
  68. 2. Backup your database.
  69. 3. Update current module code with latest recommended version. Previous
  70. versions could have bugs already reported and fixed in the last version.
  71. 4. Complete the update process: set the site into maintenance mode, visit the
  72. update.php script and finish the update operation. For more information
  73. please see: http://groups.drupal.org/node/19513
  74. 5. Verify your module configuration and check that the features you are using
  75. work as expected. Also verify that all required modules are enabled, and
  76. permissions are set as desired.
  77. Note: Whenever you have the chance, try an update in a local or development
  78. copy of your site.
  79. Configuration
  80. ------------------------------------------------------------------------------
  81. 1. On the access control administration page ("Administer >> User management
  82. >> Access control") you need to assign:
  83. - The "administer meta tags" permission to the roles that are allowed to
  84. administer the meta tags (such as setting the default values and/or
  85. enabling the possibility to edit them),
  86. - The "edit XYZ tag" permission to the roles that are allowed to set and
  87. edit meta tags for the content (there is a permission for each of the
  88. meta tags currently defined).
  89. All users will be able to see the assigned meta tags.
  90. 2. On the settings page ("Administer >> Content management >> Meta tags") you
  91. can specify the default settings for the module. To access this page users
  92. need the "administer meta tags" permission.
  93. 3. Enable specific meta tags for editing before they are available for use by
  94. users who do not have the "administer meta tags" permission.
  95. 4. The front page is an important page for each website, therefore you can
  96. specifically set the meta tags to use on the front page meta tags settings
  97. page ("Administer >> Content management >> Meta tags >> Default and
  98. specific meta tags >> Front page"). Users need the "administer meta tags"
  99. permission to do this. When there are resources providing meta tags
  100. promoted in the front page, you may force the usage of "Front page" meta
  101. tags superseding all of them.
  102. Alternatively, you can opt not to set the meta tags for the front page on
  103. this page, but to use the meta tags of the node, term or other page the
  104. used to control the front page. To do this, uncheck the "Use front page
  105. meta tags" option on the main settings page.
  106. Note that, in contrast to previous versions of this module, the site
  107. mission and/or site slogan are no longer used as DESCRIPTION or ABSTRACT
  108. on the front page!
  109. 5. Each content type should be configured to control whether certain meta tags
  110. should be automatically generated, e.g. the "description" tag can be
  111. automatically taken from the node teaser.
  112. Open Graph Protocol Extra Steps
  113. ------------------------------------------------------------------------------
  114. Because of a limitation in Drupal 6, if the Open Graph meta tags module is
  115. enabled the site's theme will have to be customized. In order to work
  116. correctly, and pass XHTML validation, the page.tpl.php for any theme(s) in use
  117. must to be customized to add the following attribute to the HTML tag:
  118. prefix="og: http://ogp.me/ns#"
  119. As an example, to make it work with the Garland theme the HTML tag must be
  120. changed to the following:
  121. Unless this change is made the page output will fail XHTML validation and the
  122. Open Graph meta tags may not be properly identified by Facebook.
  123. Using With non-PHPTemplate Themes (Chameleon, Marvin)
  124. ------------------------------------------------------------------------------
  125. Because Nodewords depends upon PHPTemplate hooks in order to output the meta
  126. tags it will not work with themes that do not use that template engine, e.g.
  127. the core Chameleon or Marvin themes. In order for these to work a Nodewords
  128. function must be called so it can insert the necessary tags into Drupal's
  129. internal list of head tags. To insert the tags, edit the main theme file, e.g.
  130. chameleon.theme, and insert the following at the top of the hook_page()
  131. implementation, e.g. chameleon_page:
  132. function chameleon_page($content, $show_blocks = TRUE, $show_messages = TRUE) {
  133. /**
  134. * Start Nodewords Changes.
  135. */
  136. // Allow Nodewords to add its tags to the internal HTML head tags array.
  137. if (module_exists('nodewords')) {
  138. $vars = array();
  139. nodewords_preprocess_page($vars);
  140. }
  141. /**
  142. * End Nodewords Changes.
  143. */
  144. Once that is added the tags will be inserted into the HTML output as expected.
  145. Known Issues
  146. ------------------------------------------------------------------------------
  147. * Meta tags cannot be output with non-PHPTemplate themes like Chameleon or
  148. Marvin without customization (see above).
  149. * Use of the Open Graph meta tags sub-module requires customizing the
  150. page.tpl.php file for the site's theme(s) (see above for details).
  151. * Versions 6.x-1.9, 6.x-1.10 and 6.x-1.11 had a severe bug that could cause
  152. data loss when updating from 6.x-1.8 or older. The problem was in how
  153. nodewords_update_6162() changed the format of the 'id' field, causing records
  154. with an 'id' (nid, tid, uid) over 65,536 to be lost. The bug has been fixed
  155. in this release but any data lost as a result of this bug is irretrievable.
  156. The maintainers are terribly sorry about this and humbly apologize if your
  157. site(s) suffered data loss as a result of this and vow to do our utmost to
  158. ensure errors of this magnitude never happen again.
  159. * Many of the code & API changes from the 6.x-1.12-x development cycle have
  160. been reverted; modules that integrate with the Nodewords APIs will have to
  161. be updated accordingly.
  162. * Nodewords currently does not support tokens, that functionality was lost
  163. when the 6.x-1.12-x codebase was reverted. Adding Token support is planned
  164. for a future release: http://drupal.org/node/1380362
  165. * If ThemeKey stops changing the theme after Nodewords is enabled, the problem
  166. is with another module and can be resolved by adjusting the ThemeKey module's
  167. weight in the 'system' table. See https://drupal.org/node/754970 for more
  168. details.
  169. Related modules
  170. ------------------------------------------------------------------------------
  171. Some modules are available that extend Nodewords with additional functionality:
  172. * Domain Meta Tags, by Katrin Silvius
  173. http://drupal.org/project/domain_meta
  174. Integrates with the Domain Access module, so each site of a multi-domain
  175. install can separately control their meta tags.
  176. * Meta tags Node Type, by Ariel Barreiro
  177. http://drupal.org/project/nodewords_nodetype
  178. Allows meta tag defaults to be controlled by content type, not just globally
  179. and per node.
  180. * SEO Friend, by Kristen Pol
  181. http://drupal.org/project/seo_friend
  182. Provides some assistance with ensuring that meta tags are all properly
  183. assigned, which can be very useful for SEO beginners.
  184. * Nodewords Meta Title, by Zoltán Adamek
  185. http://drupal.org/project/nodewords_meta_title
  186. Adds the tag, which maybe be useful for some rare
  187. scenarios.
  188. Credits / Contact
  189. ------------------------------------------------------------------------------
  190. The current maintainer is Damien McKenna [5].
  191. The original author of this module is Andras Barthazi. Mike Carter [6],
  192. Gabor Hojtsy [7] and Robrecht Jacques [8] provided some feature enhancements,
  193. while Alberto Paderno [9] maintained the module for much of its Drupal 6
  194. lifecycle. Dave Reid [10] contributed greatly to the launch of v6.x-1.13, and
  195. Nate Haug [11] played an instrumental role in deciding to scrap the ill-
  196. conceived v6.x-1.12 release.
  197. Development is currently sponsored by Media Current [12], previous sponsors
  198. include Bluespark Labs [13] and others.
  199. The best way to contact the authors is to submit an issue, be it a support
  200. request, a feature request or a bug report, in the project issue queue:
  201. http://drupal.org/project/issues/nodewords
  202. References
  203. ------------------------------------------------------------------------------
  204. [1] http://drupal.org/project/nodewords_nodetype
  205. [2] http://drupal.org/project/domain_meta
  206. [3] http://drupal.org/project/domain
  207. [4] http://drupal.org/documentation/install/modules-themes/modules-5-6
  208. [5] http://drupal.org/user/108450
  209. [6] http://drupal.org/user/13164
  210. [7] http://drupal.org/user/4166
  211. [8] http://drupal.org/user/22598
  212. [9] http://drupal.org/user/55077
  213. [10] http://drupal.org/user/53892
  214. [11] http://drupal.org/user/35821
  215. [12] http://www.mediacurrent.com/
  216. [13] http://www.bluesparklabs.com/