Printer, e-mail and PDF versions This module allows you to generate the following printer-friendly versions of any node: Printer-friendly version (webpage format) (at www.example.com/print/nid)PDF version (at www.example.com/printpdf/nid)EPUB version (at www.example.com/printepub/nid)Send by email (at www.example.com/printmail/nid) where nid is the node id of content to render. Important: The current versions of the module require at least Drupal 6.11 or 7.0. They will not work in older versions. By editing the default print.css or specifying your own CSS file and/or the print.tpl.php files, it is possible to change the look of the output page to suit your taste. Drupal 6: print[_html|_mail|_pdf][.node-node-type].tpl.php located in either the current theme or the module directory. Drupal 7: print[--html|--mail|--pdf][--node--node-type].tpl.php located in the current theme directory. Where node-type is Drupal's node type (e.g. page, story, etc.). You must install one of the following third-party tools to generate PDFs:
Meta tags quick Meta tags support based on Fields API. Included modules Starting from version 7.x-2.1, meta tags functionality is splitted to several modules: metatags_quick Main module. Alternatives Comparison of meta tags generation modules can be found here. Upgrade from nodewords Upgrade path from existing nodewords data (D6) is possible in 7.x-2.x series. Module installation Place the entire metatags_quick directory into your Drupal sites/all/modules/ directory.Enable Meta tags (quick) module by navigating to: Administer > ModulesConfigure module-specific settings: Administer > Configuration > Search and meta data > Meta tags (quick) settings. Financial support I have started this project as my personal workaround of the meta tags problem in Drupal 7.
ImageAPI This API is meant to be used in place of the API provided by image.inc. You probably do not need to install this module unless another module are you using requires it. It provides no new features to your Drupal site. It only provides an API other modules can leverage. Currently GD2 and ImageMagick support are distributed with ImageAPI. This module is specifically for Drupal 6 and older. Differences from Drupal core's image.inc Images are objects.Images are not written on each image operation and must be explicitly closed when processing is complete. Related Modules footermap: a footer site map Generates a site map as a block placed in the footer region by default. It recursively searches through the base menu id (mlid) and outputs a basic list of links ordered by sub-menus. This is dynamically generated versus more traditional theme layer based implementations such as seen in Bartik in Drupal 7. Footermap will be generated based off of Drupal 8's menu router system instead of pulling together from the database layer to make more efficient use of cache. This module was originally developed per request by a client of Kosada Incorporated (a small Columbus Ohio-based consulting firm) and has been used in several other Drupal site projects. Footermap will automatically search for url_aliases if the path.module is enabled. Theming has changed again, which should offer more flexibility in template preprocess or template for overriding what menu, children, and individual menu items to display.
Token Tokens are small bits of text that can be placed into larger documents via simple placeholders, like %site-name or [user]. The Token module provides a central API for modules to use these tokens, and expose their own token values. Note that Token module doesn't provide any visible functions to the user on its own, it just provides token handling services for other modules. For Drupal 6, the Token module provides a "Token Actions" module which can be enabled separately. This provides several "actions" for the Drupal core Actions/Trigger modules to use that take advantage of the Token replacement functionality. Modules that use the Token module and provide tokens via the API include Organic Groups, Pathauto, Comment Notify, and Commerce. Pledges #D7CX: The basic token API is now a part of Drupal 7! #D7AX - I pledge to make this module as accessible as it can be.
Taxonomy Title This module was designed to update the heading tag at the top of the taxonomy term page. The contents of this H1 (or sometimes H2) tag are *extremely* important for SEO (Search Engine Optimization). People interested in SEO may prefer to add more user-friendly, keyword-rich, and descriptive words to this heading element. This is the only module that let's you control that title individually for every term. The taxonomy title module also provides tokens which can be used in conjunction with the Page title and Meta tags modules. The Page title module is designed to let you control the title tag in the HTML Header of your page. Note: The D5 version of Taxonomy Title must be invoked from the theme, and requires a minor change to your template.php file (example included). This module was written by Jen Lampton of Jeneration Web Development.
Pathauto The Pathauto module automatically generates URL/path aliases for various kinds of content (nodes, taxonomy terms, users) without requiring the user to manually specify the path alias. This allows you to have URL aliases like /category/my-node-title instead of /node/123 . The aliases are based upon a "pattern" system that uses tokens which the administrator can change. Requirements Versions The 7.x-1.x and 6.x-2.x branches are currently accepting new feature requests and are kept in sync as much as possible. Known issues Multilingual URL alias support is still a little unstable and should be tested before used in production. Recommended modules Redirect (D7) / Path Redirect (D6) when installed Pathauto will provide a new "Update Action" in case your URLs change. Co-Maintainers Pathauto was originally written by mikeryan and maintained by Greg Knaddison (greggles) . Pledges #D8CX : I pledge that Pathauto will have a full Drupal 8 release on the day that Drupal 8 is released. Downloads
Scheduler Scheduler gives content editors the ability to schedule nodes to be published and unpublished at specified dates and times in the future. Dates can be entered either as plain text or with calendar popups. In Drupal 6 and 7 to use calendar popups you need to install the Date Popup module, which is part of the Date module. In Drupal 8 this is built into Core. Scheduler for Drupal 8 We are actively developing the first 8.x release of Scheduler. Notes Please check if cron is running correctly if scheduler does not publish your scheduled nodes.Scheduler only does publishing and unpublishing of nodes. Credits Scheduler is the work of many people. Translations Translations to other languages than English can be found over there: Screencasts If you want a quick introduction to what Scheduler does, check out these nice screencasts:
Chaos tool suite (ctools) This suite is primarily a set of APIs and tools to improve the developer experience. It also contains a module called the Page Manager whose job is to manage pages. In particular it manages panel pages, but as it grows it will be able to manage far more than just Panels. For the moment, it includes the following tools: Plugins -- tools to make it easy for modules to let other modules implement plugins from .inc files.
Wysiwyg Allows the use of client-side editors to edit content. It simplifies the installation and integration of the editor of your choice. This module replaces all other editor integration modules. No other Drupal module is required. The Wysiwyg module supports any kind of client-side editor including HTML editors (a.k.a. WYSIWYG), pseudo-editors (buttons to insert markup into a textarea), or even Flash-based applications. The Wysiwyg module also provides an abstraction layer for other Drupal modules to integrate with any editor. Discussions happen in the Wysiwyg group, and in IRC #drupal-wysiwyg. Installation Download and install the module as usual.Go to Administer » Site configuration » Wysiwyg, and follow the on-screen installation instructions that are displayed there.Follow the on-screen installation instructions. Further documentation Supported editors/plugins Editors: CKEditor, FCKeditor, jWysiwyg, markItUp, NicEdit, openWYSIWYG, TinyMCE, Whizzywig, WYMeditor, YUI editor. Contribute
Views You need Views if You like the default front page view, but you find you want to sort it differently. You like the default taxonomy/term view, but you find you want to sort it differently; for example, alphabetically. You use /tracker, but you want to restrict it to posts of a certain type. Views can do a lot more than that, but those are some of the obvious uses of Views. Views for Drupal 8 Views is in Drupal 8 Core! Recommended versions of Views! For new installs of Drupal 6, we recommend the 6.x-3.x branch. The 6.x-2.x branch of Views is in critical/security maintenance mode only. Dependencies The Drupal 7 version of Views requires the Chaos Tool Suite also known as CTools. Views' bug squad The Views' bug squad is a group of people who have dedicated a few hours a week to help provide support and fix bugs in the issue queue. Views documentation Views 1 Views 2 (This link goes to the Advanced Help project page. Sponsorship This project is sponsored by IO1. Our book
References This project provides D7 versions of the 'node_reference' and 'user_reference' field types, that were part of the CCK package in D6, at functional parity with the D6 counterparts. See for details. Note for users upgrading from References 7.x-2.0-beta3 There were a couple changes in the way 'References' views are handled ("referenceable nodes/users defined by a view"), which might require double-checking those existing on your site: The 'label' (node title or user name) is no longer automatically added if not included in the view. Note for users upgrading from CCK D6 The References project integrates with the content_migrate module present in CCK 7.x-2.x-dev to allow the migration of field definitions and field values from D6 nodereference and userreference fields. Similar modules: