Drupal 6 modules

Notes on various Drupal 6 modules.

Also see Drupal 6 custom content type for info about modules related to content types.

My notes on Drupal 7 modules could also be useful because modules may not have changed significantly between releases. I don’t add information to this page much any more as I mostly work on D7.

Index

Essential modules
Access Control
Data import
- Table Wizard
- Schema
Additional modules
Modules good for development
- Devel
- Others
Potential modules
- Kaltura

Essential Modules

When I say “essential modules” I mean those modules that will be installed on most web sites.

User protect

Install and enable as usual.
Administer -> User management -> User Protect.
By default, users with ‘administer user’ permission bypass all protections i.e. can still edit/delete anything/anyone. To prevent this, untick everything under ‘Administrator bypass default’ in the ‘Protection defaults’ tab -> ‘Administrator bypass defaults’ section.
Also check out permissions in Administer -> User management -> Permissions -> ‘userprotect module’ section.

Important note: In order to protect a user from deletion (by visiting user/X/delete directly) and/or OpenID edits (by visiting user/X/openid directly), you must enable the ‘delete’ and/or ‘openid’ protection specifically. Enabling ‘all account edits’ does not enable these protections!

Token

Required by Pathauto module (and many others).

Pathauto

Auto remove node IDs from URLs. Note that the core Path module allows users to rename paths, but doesn’t do it automatically.

Pathauto

Enable clean URLs at Administer -> Site configuration -> Clean URLs.
Enable Path module.
Install Token module.
Install Pathauto module.
Configure URL aliases to set the default path pattern for Nodes to content/[menupath-raw], via Administer -> Site building -> URL aliases, ‘Automated alias settings’ tab, ‘Node paths’ section.
To have UTF-8 characters translated into ASCII (as per URL spec requirements), turn on transliteration. You’ll need a file that tells the module how to transliterate, e.g. sites/all/modules/pathauto/i18n-ascii.txt.
Before saving the configuration, generate all aliases by ticking ‘Bulk generate aliases for nodes that are not aliased’ and the similar bulk generation checkboxes in the ‘User contact form paths’, ‘Taxonomy term paths’ and ‘User paths’ sections.

Note: If you don’t have any taxonomy vocabularies yet, you will get an error on bulk update of taxonomy term paths:

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘) LIMIT 0, 50’ at line 1 query: SELECT tid, vid, name, description, src, dst FROM term_data LEFT JOIN url_alias ON CONCAT(‘taxonomy/term/’, CAST(tid AS CHAR)) = src WHERE src IS NULL AND vid <> 0 ) LIMIT 0, 50 in /home/bn/f3/dev/webapps/drupal/f3drupal/sites/all/modules/pathauto/pathauto_taxonomy.inc on line 84.

Just ignore it.

Auto-generate all aliases

If you want to auto-create all aliases using Pathauto, but you installed it after Path has already been used to create aliases that are used (i.e. linked to) on your site, then you can prevent the existing aliases being deleted by Pathauto:

Administer -> Site building -> URL aliases, ‘Automated alias settings’ tab -> ‘General settings’ section.
Set ‘Create a new alias. Leave the existing alias functioning.’ in the ‘Update action’ part.
Create or recreate the aliases. See below.

Configure alias formats

You can configure the paths generated via Administer -> Site building -> URL aliases, ‘Automated alias settings’ tab. I’ve been unable to find a page that lists all available tokens (e.g. [title-raw]), but some of those available can be found in sites/all/modules/token/token_node.inc. Note that the “raw” version of tokens should be used otherwise there may be problems. Raw tokens can contain user-submitted data, unfiltered by Drupal, but pathauto filters them.

To have the path reflect the content hierarchy (as achieved via the menu), set the ‘Default path pattern’ in ‘Node path settings’ to content/[menupath-raw].

After changing the settings, recreate the aliases as described below.

Create aliases for pages that don’t yet have them

Administer -> Site building -> URL aliases -> Automated alias settings -> Node paths.
Tick ‘Bulk generate aliases for nodes that are not aliased’.
If required, do the same for taxonomy term paths and user paths.
Save.

Recreate pathauto URL aliases

Delete all aliases via Administer -> Site building -> URL aliases, ‘Delete aliases’ tab, then create them as described above.

Alternatively you could re-save any existing content to have path aliases auto generated, but this is obviously time consuming with many nodes.

XML sitemap

To create an XML sitemap that abides by the sitemaps.org spec.

Install as normal.
Enable ‘XML Sitemap’, ‘XML sitemap engines’, ‘XML sitemap node’, ‘XML sitemap taxonomy’, ‘XML sitemap user’. ‘XML Sitemap menu’ is not required.
Administer -> Site configuration -> XML sitemap, Setting tab.
Expand ‘Taxonomy’ section, click on the taxonomies you’d like to include in the map and set Inclusion to ‘Included’ in their ‘XML Sitemap’ section.
Do the same for the appropriate content types in the ‘Content’ section.
To generate the sitemap, run cron.php or ‘Rebuild links’ via Administer -> Site configuration -> XML sitemap.
The sitemap should be available at /sitemap.xml.
Administer -> Site configuration -> XML sitemap, Search Engines tab.
Tick all engines and save.

Note: Do not generate sitemap items for the user profile pages unless anonymous users have permission to view them.

i18n

Enable ‘XML Sitemap Internationalization’ submodule if you’ve a multi-language site.
For some reason, the default sitemap won’t work. To fix this, edit then immediately save the default sitemap (this will set its language to the default, e.g. English). The URLs /sitemap.xml and /en/sitemap.xml should now both work.
Add other sitemaps for each language.

Menu Breadcrumb

Uses menu hierarchy to generate breadcrumb (admin breadcrumb will still work).

Install and enable as usual.
Configuration can be done via Administer -> Site configuration -> Menu breadcrumb.
One option that may be worth ticking is ‘Hide the breadcrumb if the breadcrumb only contains the link to the front page’.

Note: The breadcrumbs won’t show unless the theme supports it. Check the theme settings at Administer -> Site building -> Themes.

Gotchas

If you want the menu breadcrumbs to work with a view, you have to give the view a menu item via the view config, even if you then go on to disable it via menu config and add another item deeper in the menu.
It doesn’t work properly when a page has a menu item in multiple menus - I think the first menu will be used for the breadcrumb.

Menu block

Enables you to create blocks that output different types of menus, configurable by source, start point, depth, expanding behaviour etc.

Install as normal.
Administer -> Site building -> Blocks, ‘Add menu block’ tab.

Conditional Stylesheets

Allows conditional stylesheets to be specified in theme.info file, e.g…

conditional-stylesheets[if lt IE 7][all][] = ie6_and_below.css

Search

Core module. Provides a basic search box that after initial search offers advanced options for e.g. searching within a particular taxonomy. Indexing is done via cron.

Enable ‘Search’ module as normal.
Administer -> Site configuration -> Search settings.
Configure access to basic/advanced search via Administer -> User management -> Roles.

Customisation

Can we customise advance search?

Search configuration

To configure the advanced search form.

Enable as normal.
Enable access in ‘search_config module’ section of Administer -> User management -> Roles.
There should now be an ‘Advanced search configuration’ section at Administer -> Site configuration -> Search settings.
Node types excluded from search index should also be excluded from search form.

Better Formats

Allows you to set different default input formats/filters, by role, for nodes, comments or blocks.

Install as normal.
To be on the safe side, it’s probably best to have site default filter as whichever has most filtering / least markup control, then allow use of other filters via the defaults, as follow.
Set defaults via Administer -> Site configuration -> Input formats, Defaults tab.
Roles are matched in the order they appear in the defaults list, so be sure to drag custom roles above the Authenticated user role, otherwise the filter default for logged-in users will always be that set for Authenticated user.

WYSIWYG

Note: This module did not work properly with YUI - all buttons were displayed on the left regardless of settings and there was no image uploading. Not tried any other editors. See YUI Editor module notes below.

Wysiwyg

To set up a number of possible WYSIWYG editors.

Install the module as normal.
Administer -> Site configuration -> Wysiwyg. Download chosen editor and extract into directory listed in instructions on that page.
Select your editor for Filtered and Full HTML.
Click Edit link to edit editor settings.

For YUI…

Add buttons to the editor via Buttons and Plugins. Best not to add any that create fonts or mess with colouring.
Filtered HTML only allows <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>, so ensure chosen buttons will only output those.
Editor appearance -> Button allignment: centre.
Cleanup and output -> Force cleanup on standard paste.

For FCKeditor…

Add buttons to the editor via Buttons and Plugins.
Enable ‘Force cleanup on standard paste’ in ‘Cleanup and output’ section, to prevent user pasting in dodgy content.

IMCE

For image uploading with some WYSIWYG editors that don’t provide it (e.g. FCKeditor).

Install module as normal.
Administer -> Site configuration -> IMCE.
Set profile for authenticated users to ‘Sample profile’ (or create a custom one).
You can set add/edit/delete/resize/thumbnail permission on different directories, using placeholders to e.g. limit a user to their own directory (sites/default/files/u%uid).

Install IMCE Wysiwyg API bridge module for easy integration with FCKeditor or TinyMCE.

IMCE Wysiwyg bridge

This adds an IMCE button option to the button config for FCKeditor (tested) and TinyMCE (apparently).

IMCE mkdir

IMCE Mkdir

Allow users to create subfolders.

Custom Permissions

Adds granularity to ‘Administer site configuration’ permission, to allow e.g. permission to administer site information without permission to access any other site configuration.

Install and enable ‘Site Configuration Permissions’ (at the time of writing, the module is going through a name change).
Administer -> Site configuration -> Site Configuration Permissions. You’ll see a whole load of permissions have been added.
To grant administer site information without anything else…
1. Administer -> User management -> Permissions, ‘config_perms module’ section.
2. Grant ‘dispay site configuration menu’ and ‘administer site information’.

Access Control

Probably the neatest solution is Taxonomy Access Control, because normal content and forums can be associated with taxonomies and it allows defaults (unlike TAC Lite).

Another option is a combination of Content Access for content types (unsetting all access control for forum posts) and Forum Access for forums, though they are administered in slightly different ways.

Core private downloads

This serves all files through Drupal so it can apply whatever access mechanisms apply to the nodes to which the files are linked.

Administer -> Site configuration -> File system.
Set Private download mechanism. All files will now be served via /system/files/ instead of via /sites/default/files/, allowing Drupal to control access.

To prevent files being accessed via direct link to /sites/default/files/…

Either:

Move files directory out of the drupal root so that Apache can’t serve them (see Setting private download method tutorial).
Set ‘File system path’ accordingly (via Administer -> Site configuration -> File system).

Or:

Set the following in /sites/default/files/.htaccess:
```
Order deny,allow
Deny from all
```

Core permissions

Permissions reference

View own

Splits the view/edit/delete permissions into ‘view/edit/delete own content’ and ‘view/edit/delete any content’, particularly useful when combined with CCK and Views modules to create custom databases of user-submitted data.

Note: You will probably have to rebuild permissions via Administer -> Content management -> Post settings.

Content Access

This adds an ‘Access Control’ tab to a content type’s edit page (Administer -> Content management -> Content types, ‘edit’ link for a content type) so that you can configure access control by role for each content type. The permissions available are the same as normal, so only view/edit/delete. You can also set permissions on a per-node basis.

This module is not good at assigning different access permissions to different groups of nodes - you can only do it for all nodes of a particular type (e.g. all pages) or for each node of a particular type (e.g. each individual page). For a site where some pages are public and others private, you’d prevent anonymous users viewing the Page content type, then give them permission to view particular pages.

For forums, the modules can only control access to forum topics, because only topics are nodes but other entities are not (categories and forums are achieved via taxonomy vocabulary terms). To achieve access control over forums at the category/forum level, you can use the Forum Access module.

Block Access

Adds fine grained permissions for administering blocks.

Install and enable as usual.
Grant ‘Administer blocks’ permission at Administer -> User management -> Permissions. This is required in order to view the block admin page.
Global permissions that apply to all blocks can be found at Administer -> User management -> Permissions, ‘block_access module settings’ section.
Permissions over all blocks created by a particular module can be found at Administer -> Site building -> Blocks, ‘Block Access Settings’ tab.
To allow a role to edit a particular block, edit the block and select the role under the ‘Role specific view settings’ and ‘Role specific config spec’ sections. Note: The view permission is required to view the block in the block admin page. It does not control whether the block is visible on the site.
The ‘Role specific config spec settings’ grants access to change the block-specific settings, e.g. the content of a block.

Bugs

There seems to be an oddity whereby setting block-specific permissions for the first time will also set the Block Access Settings, so the permissions will apply to all blocks of the same types. To get around this, just remove the changes from the Block Access Settings and update the block-specific permissions again. From there on in the block-specific permissions should no longer be applied to the Block Access Settings.

Forum Access

Requires ACL module: ACL

Install ACL module then forum access module as normal.
Access control setting will be available when you edit a container/forum via Administer -> Content management -> Forums, edit container/forum link.
If using the Content Access module, deselect all of its access control settings for the forum topic node type via Administer -> Content management -> Form topic, ‘Access Control’ tab.

Taxonomy Access Control (TAC)

Taxonomy Access Control

Using Taxonomy Access Control module:

Allows you to control access via taxonomies, hence very flexible.

Install the module as usual.
Administer -> User management -> Taxonomy access permissions.
Edit a role.
Each action view/update/delete/create/list has access controls - Allow, Ignore, Deny.
Add a new category for a role (e.g. and set access controls.
Perhaps best to set the global default category for anonymous and authenticated users to deny and for other roles to ignore. That way all roles will inherit deny by default.

Note that when a user has access to create content be sure to have TAC allow them to create the appropriate vocabulary terms. In the case of forum topics, if the user can create a topic they must also be able to create the terms that define the topic’s forum (and its container). Permission to list forum vocab terms will determine whether they can see the particular forums or not.

Note also that the global default settings apply to any content that’s created without association with a taxonomy vocab, e.g. by modules like Content Profile. So for example if you’ve got a taxonomy set up for access control of nodes you may have problems accessing any nodes created by modules which don’t apply any vocab terms if you set the default for the vocab to deny access. The only way around this is to set to default to allow then override for all other relevant vocabs.

Taxonomy Access Control Lite

Allows you to control access via taxonomies, but not as powerful as TAC and critically doesn’t allow you to set defaults for missing/new vocabulary terms.

Install and enable as usual.
Create and access control “scheme” by going to Administer -> User management -> Access control by taxonomy. Choose a vocabulary for a scheme and save.
Click the scheme’s tab to edit it. Choose the permissions to assign and the vocabulary terms by role and save the scheme.

E.g. You could create a vocabulary called “Forum Privacy” with terms “public”, “members”, “editor” and “admin”, then create schemes to assign view, edit and delete permissions to those terms.

The major downside to this module is that there is no “all” option when selecting terms, so you have to edit the schemes every time a new term is created (e.g. when you create a new forum).

Data import

Table Wizard

Requires Schema and Views.

Install as normal (and the Schema and Views modules).
Administer -> Content management -> Table Wizard.
TODO

Schema

Required by Table Wizard.

Additional modules

Secure Pages

Force SSL when creating or editing content, viewing user details, or administering the site.

Editable blocks

Allows editable blocks to be created, the contents of which can be edited by users without full ‘administer blocks’ permission.

Install and enable as normal.
Grant at least ‘edit editable blocks’.
Create a new editable block.
The user (with edit permission) can now edit the block via the ‘edit’ link that appears by the block when they’re logged in.

Backup and Migrate

Backup and Migrate Files

Has the capability of dumping the database periodically, allowing automated backups to be taken from shared hosting via FTP.

Filefield Sources

Useful to link IMCE with image/file fields.

Install and enable as normal.
Content management -> Content types -> manage fields (for the desired content type) -> Configure (the desired field).
‘File sources’ section, select IMCE as source.

Filefield Paths

Filefield paths

Allows you to use node tokens for the upload path of file upload fields.

Install and enable as normal.
Content management -> Content types -> manage fields (for the desired content type) -> Configure (the desired field).
In the File Path Settings section, you’ll have a list of file name replacement patterns, which should now include node tokens.

Imagefield Tokens

ImageField Tokens

Requires Filefield Paths.

Allows you to use node tokens for the image alt and title (where image is created by file field). E.g. For an image you could allow user defined alt text and set its default to use the [title] token.

Install and enable Filefiels Paths, then Imagefield Tokens, as normal.
Node tokens will be available for image alt and title.

MultiLink

NOTE: This can’t be used with Link Checker as it links to the home page if the node ID isn’t found, hence link checker can’t detect broken links.

MultiLink

Install and enable the module as normal. Can also enable MultiLink Redirect for i18n support.
Configure a filter at Administer -> Site configuration -> Input filters and enable MultiLink filter.

You should now be able to use the following shortcuts in your node body:

[123:$] to link to node 123 using its title.
[123:foo bar] to link to node 123 using the words "foo bar".

CKEditor

CKEditor Link

Adds support to CKEditor for linking to nodes.

Install and enable as normal.

Edit the CKEditor config at [drupal]/sites/all/libraries/ckeditor/config.js:

CKEDITOR.editorConfig = function( config )
{
  ...

  // For CKEditor Link module.
  if (Drupal.settings.ckeditor_link) {
    config.extraPlugins += (config.extraPlugins) ? ',drupal_path' : 'drupal_path';
    CKEDITOR.plugins.addExternal('drupal_path', Drupal.settings.ckeditor_link.module_path + '/plugins/link/');
  }
   
};

Give roles permission to use it via Administer -> User configuration -> Permissions by granting ‘access ckeditor link’ in the ‘ckeditor_link module’ section.
Configure relevant input filters at Administer -> Site configuration -> Input formats and enable the CKEditor Link Filter.
Edit WYSIWYG settings for the relevant input filter at Administer -> Site configuration -> WYSIWYG and enable its CKEditor Link button (Link also has to be enabled).

You should now get a Drupal option for Link Type when you create a link using the editor. It generates links like <a href=”/node/1”>foo</a> then replaces the /node/1 with the actual clean URL on display.

Only down side is that by default it uses the URL as link text, instead of node title.

Link Checker

Install and enable as normal.
Grant the appropriate permissions via Administer -> User configuration -> Permissions, ‘linkchecker module’ section.
Select the things you’d like to scan at Administer -> Site configuration -> Link checker.
After cron has run a report will be available at Reports -> Broken links.

Upload

Allows editors to attach files to their content.

Give all roles (including anonymous users) permission to ‘view uploaded files’ at Administer -> User management -> Permissions.
Give editors permission to ‘upload files’.

Profile Category Weights

Lets you change the order of profile categories.

Install as normal.
Administer -> Site configuration -> Profile Category Weight.

Protect Critical Users

Note: User Protect module is better, essential for Drupal 6, and can do the same things as this module anyway.

Protect Critical Users

Prevents user id 0 (anonymous user), id 1 (admin) and current user being deleted.

Important: The users can still be edited, which means passwords can still be changed, so non admin can gain admin access if they can administer users! Use the User Protect module to protect edits as well as deletes.

Install and enable as usual.

NOTE: Do not use this for now - it wasn’t working properly last time I tried.

Menu Subtree Permissions

Grants users ability to add content to a particular menu without full blown menu admin access. It only works on manually created menus, not default Drupal menus (see menu notes below).

Administer -> Site building -> Menus.
Select a menu, edit it, then in the ‘Menu Sub-tree Permissions’ section choose the role it’s available to and save.

Note that you no longer have to grant the user permission to ‘administer menu’ as you would without this module (see menu notes below).

Caveats

Regardless of how many menus you set available to a role, the only one that will show when creating content is the one selected as default menu for content in Administer -> Site building -> Menus -> Settings tab.
It only works when you create new content - editing content does not allow you to change its menu settings.

Menu Admin per Menu

Adds “administer ‘menuname’ menu items” to the permissions page, so that users can add nodes to some menus but not others.

Administer -> User management -> Permissions.
Grant access to ‘access administration pages’.
Grant access to the appropriate menus in the ‘menu_admin_per_menu module’ section.

WYSIWYG Filter

Allows you to create filters to get rid of any nasty markup output by the WYSIWYG editor.

Install.
Create new filter or edit an existing one at Administer -> Site configuration -> Input formats. Tick ‘WYSIWYG Filter’ option and save.

Configure the filter (via its ‘Configure’ tab). The following ‘HTML elements and attributes’ seem good for use with the Full HTML input format using most CKEditor buttons:

a[href|name|title],
img[!src|!alt|style],
-p[style],
-div[class],
br,-h2,-h3,-h4,-h5,-h6,-em,-strong,-strike,-sup,-sub,-address,-pre,-cite,-code,-blockquote,-ul,-ol,-li,-dl,-dt,-dd,-span,
-table[align|border|cellpadding|cellspacing|style|summary],-tr,-td,-th[scope],-thead,-tbody,-captiona[!href],

The format is a comma-separated whitelist of tags with their allowed attributes. - specifies that empty elements should be removed. ! specifies an attribute must be included. An attribute’s presence indicates it’s allowed.
Allow whatever styles you need in the ‘Style properties’ section. The following seem good for use with the Full HTML input format using most CKEditor buttons (and the f3 customisations):
```
margin,margin-left,height,width,float
```
Set allowed classes (and ids and URLs) in the ‘Advanced rules’ section. This is necessary is allowing a class on div tags for YAML’s ‘float_right’ and ‘float_left’ styling.
Add the site’s domain to the whitelist in ‘Spam link deterrent settings’ section.
Rearrange it to be above HTML corrector (not sure why - it’s in the installation instructions).
Add editor to filter via Administer -> Site configuration -> Wysiwyg.

Embedded Media Field

Allows you to add fields to your content types for referencing third party media sources, e.g. flickr, youtube.

Node Picker

Add a button to WYSIWYG which allows you to easily insert a link to existing nodes. Can filter by node name and content type.

Poor Man’s Cron

For use if cron is not available on the server. Calls the maintenance page via AJAX. Requires regular visitors to the site.

Install as normal.
To configure how often cron will run, change the setting at the bottom of Administer -> Site configuration -> Site information.

Locale, Content Translation, i18n and Language Icons

The Locale and Content Translation modules are built in. They allow you to translate the Drupal UI and content. They don’t however have any support for multi-lingual menus, block and other features. For that, install the i18n module package, which will add a number of modules for translating different Drupal artifacts. The Language Icons module changes the language switch block to use icons.

Enable Content Translation and Locale modules.
Download translation from http://drupal.org/project/translations and extract into root directory. This will create ‘translations’ directories all over the place.
Enable language from Administer -> Site Configuration -> Languages -> Add Language.
Change language negotiation to ‘Path prefix with language fallback’ in Administer -> Site configuration -> Languages -> Configure tab.
Active the Language switcher block by placing it in e.g. the header. Administer -> Site building -> Blocks.
Enable content translation for each content type by editing it from Administer -> Content management -> Content types and choosing ‘Enabled, with translation’ in the Workflow section.

For the advanced capabilities offered by i18n module:

Install the i18n module and enable at least ‘Content type translation’, ‘Internationalization’, ‘Menu translation’, ‘Taxonomy translation’ and their dependencies. A ‘Multilingual system’ tab will be added to Administer -> Site configuration -> Languages, but the defaults are good.
Install the ‘Language Icons’ module to include flags in the language switch.
Administer -> Site configuration -> Languages, Configure tab, Icons sub-tab to configure icons - their path, size and how they are used in the language switcher block (e.g. flags and text, flags only, etc).

URL aliases

By default, the default language doesn’t use a prefix for its URL alias. If you’d like the default language to use a prefix, for consistency:

Administer -> Site configuration -> Languages.
Edit the default language.
Set its path prefix.

Gotchas

If you are on a page that doesn’t have a translation, then use the language switcher block to switch languages, the same page will still be shown (though the menus will probably changes).

To get around that either use the Translation 404 module or write a custom module (which I’ve done - ‘f3 Translation Not Found’ module).

Translation 404

Provides a custom 404 page for when a translation isn’t found (as opposed to the default, whereby the same page will still be shown though the menus may change).

Install as normal.

Bug: The default behaviour is to load the module’s translation404-page.tpl.php, which shows a message for all languages. Though it doesn’t seem to have a variable available to it that gives the current language, I believe you can use the global $language variable to determine language and show a language-specific message. However, the module seems to have a bug that prevents the template being overridden in your theme. See Can’t override template.

So, instead, can create a custom module that uses hook_nodeapi to redirect and display a message if a translation isn’t available. I’ve done this as the ‘f3 Translation Not Found’ module.

Forums

Must add a menu item pointing to ‘forum’ in order to get a link to the forums.

Comments serve as replies.

Permissions for authenticated users should allow creation of forum topics at least. Will also need permission to create comments.

YUI Editor

Install YUI and YUI Editor module.
Download latest YUI supported by the module and extract to sites/default/files/lib/yui-x.x.x, where x.x.x is the latest version supported, e.g. yui-2.6.0 at the time of writing. Available YUI Downloads
Set location of YUI library at Administer -> Site configuration -> YUI Common Settings. Ignore the note to enter the path as files/lib - it should be the full path from drupal root e.g. sites/default/files/lib/yui-2.6.0.
Edit default editor profile at Administer -> Site configuration -> YUI editor settings.
Choose a role and enable ‘Resize’, ‘Use P tags’, ‘Image upload’ and ‘Coder button’.
Use ‘Custom’ button profile and remove controls for font, font size, font colour, background colour and underline (because links are underlined).
Grant permission for role to use editor. Administer -> User management -> Permissions, ‘Access YUI and ‘access yui editor’.

For image uploading (if not already set up):

Enable Upload module. Upload
Give user permission to ‘upload files’ and ‘view uploaded files’ at Administer -> User management -> Permissions.

Create a page using Full HTML. Note that using Filtered HTML will prevent images and other filtered content from showing. To disable Filtered HTML:

Administer -> Site configuration -> Input formats.
Select Full HTML as default and ‘set default format’.
Configure Filtered HTML and remove all roles.
Configure Full HTML, add all desired roles.
Optionally enable ‘HTML corrector’ and ‘URL filter’ are enabled.

Advertisment

Install as usual.
Enable “sub”-modules ‘Ad’, ‘Ad report’, ‘Image Ad’, ‘Ad click filter’ and any others you require.
Set limit on image size and dimensions via Administer -> Site building -> Ad, Settings tab -> Image Ad tab.
Grant ‘show advertisments’ permission for all roles that need to view ads via Administer -> User management -> Permissions.
Create a new ad via Create content -> Advertisment.
Display ads in blocks via Administer -> Site building -> Blocks.

Note: One “out of the boxes” options for creating auto rotating ads:

Use the Views Slideshow module, if you’re prepared to have all images pre-loaded and switch via javascript & css.

Instead, I created a module which could rotate any block via AJAX, then set it to load the block provided by the Advertisement module (with output set to Raw and otherwise configured to show only the linked ad image).

Views Slideshow

Install as normal. Module can be found in ‘Views’ section of Administer -> Site building -> Modules.
Create new view as normal via Administer -> Site building -> Views.
Set Style to ‘Slideshow’.

Note: If you’d like the first “slide” to be randomly selected, add ‘Global: Random’ to view’s Sort Criteria.

Also see ‘Create rotating adverts’ below.

Taxonomy Menu

Allows you to create menus from taxonomies.

Note that this is superior to the default menu handling of taxonomies, which can only list nodes that have a particular vocabulary term - you can’t make a menu that links to all terms within a vocabulary (e.g. If you’ve a ‘sections’ taxonomy you can’t link to all sections).

Install the module as usual, enabling at least ‘Taxonomy Menu’.
A new ‘Taxonomy menu’ section will have been added to a vocabulary’s edit page in Administer -> Content management -> Taxonomy.

To create site sections:

Create a menu for the sections via Administer -> Site building -> Menus.
Set the menu to display somewhere via Administer -> Site building -> Blocks.
Create a new vocabulary called “Sections” via Administer -> Site building -> Taxonomy.
Choose the content types that can be in the sections.
Set the vocabulary’s menu to ‘Sections’ and deselect ‘Item for Vocabulary’ (‘Auto Expand Menu Item’ should be selected by default).
Add a term for each section e.g. ‘Section One’, ‘Section Two’, etc.
Create some new content, choosing a section.

By default, a section menu item will link to the taxonomy term, which will show a summary of all content associated with the term. To have a single node as the section landing page:

TODO

Nodecarousel

Can display a node of a particular type in a block and rotate via AJAX (i.e. doesn’t load all nodes into markup).

Trigger

Trigger: Assign actions to system events

A core module. Allows you to perform basic actions (available at Administer -> Site configuration -> Actions), e.g. emailing someone, when a system event occurs. The events are very high level (e.g. node created) so the Rules module is far more useful.

Rules

Allows you to trigger actions via custom rules for system events.

Note: Rules 6.x-1.0 required Tokens > 27/08/2008 e.g. 6.x-1.12 (i.e. not the 6.x-1.11 version from Drupal 6.11).

Install module as usual, enabling ‘Rules’, ‘Rules Administration UI’ and ‘Rules Scheduler’ “sub”-modules.
Administer -> Rules -> Triggered rules.
Add a new rule, giving it a descriptive label and choosing the event e.g. Node: After saving new content.
Add a condition e.g. Node: Content has type: Page.
The icon on the right of the condition can be used to add AND/OR logic.
Add an action e.g. System: Send a mail to all users of a role.
You can use tokens e.g. [node:title] in the email message.

Note that a rule based on user role will not be triggered if the role is created via the Auto Assign Role module via Automatic Role Assignment.

Flag

TODO

Meta tags

Nodewords

Allows you to set meta tags for nodes (e.g. keywords and description).

Install and enable at least Nodewords and ‘Nodewords - basic meta tags’.
Configure at Administer -> Content management -> Meta tags.
Grant permission to users to use the available metatags via Administer -> User management -> Permissions, ‘nodewords_basic module’ section.
To enable/disable for particular content type, see the ‘Allow editing of meta tags’ option in the workflow settings for a content type when edited via Administer -> Content management -> Content types.

Filter By Node Type

Adds checkboxes to each node type (Administer -> Content Types) which allows you to choose which input filters are available.

TODO

Filter By Content ?

Doesn’t seem to exist, e.g. if you add a comment (i.e. reply) to a forum topic, you’ll get a choice of input filters according to your role settings. Would be nice if you could configure the available filters like you can with the Filter By Node Type module.

TODO

Devel module

Includes a Theme Developer component that helps find out the function/hook used for different parts of the UI.

BUG: When Theme Developer is enabled, jquery is broken on the page to add/edit a new content type (Administer -> Content Management -> Content types -> type -> Add/Edit), preventing the various settings menus expanding.

TODO

Mass Contact

Allows contact form to send email to everyone in a set of roles.

Install as normal.
The form itself can be found at /mass_contact.
Administer -> Site building -> Mass Contact form.
Add a category for a collection of roles via the ‘Add category’ tab.
Email settings are in ‘Settings’ tab.
May want to disable ‘Allow sender to override BCC setting’, ‘Save a copy as a node by default’ and ‘Allow sender to override node copy setting’.
The module creates various permissions, including ones to set which categories are available. Administer -> User management -> Permissions, ‘mass_contact module’ section.
The permissions define which categories can be selected by the user, hence which people they can contact.
Enable (and rename) the mass contact menu item in the navigation menu via Administer -> Site building -> Menus.

Note: There can be problems assigning permissions to a category which has a single quote in its name.

Auto Assign Role

Automatically assign roles when a user registers and optionally give the user a choice of roles.

Install as normal.
Administer -> User management -> Auto assign role.
Allow user to choose role on registration and configure wording in the ‘User Role Assignment’ section.

Drawbacks

Can not prevent ‘authenticated user’ being one of the choices, despite the fact it’s automatically added to every user.

Note: At time of writing (23/06/2009) I believe the dev version 6.x-1.x-dev of this module hides ‘authenticated user’ (6.x-1.0-beta3 doesn’t).

Dev version

Install as normal.
Administer -> User management -> Auto assign role.
Allow user to choose role on registration and configure wording in the ‘Allow User to Choose’ section.

Apply for role

Allow user to apply for roles when they register and presumably later.

Install as normal.
Configure how user is presented with choice of role at Administer -> Site configuration -> Apply for role administration.
After a user registers, they are not automatically assigned the role. Instead, you have to view “role applications” via Administer -> User management -> Manage role applications.

Drawbacks

Can not configure wording.
User not automatically given the role but instead has to be administrated via a different interface.

Location

Install the module and enable Location in the ‘Location’ section and Location CCK in the ‘CCK’ section.
Administer -> Site configuration -> Location to select country.
There should now be a Location field type available to CCK.
Add the field to a form, then configure.
‘Locative information’ section -> ‘Collection settings’ to add/remove location related fields (e.g. street, city, etc).

Pros

Location data is exposed to Views via its own group.
You can reorder location fields for each content type that uses them.
Links to a google map are auto-created for some countries (though not all configured with a map by default).

Cons

County/province offers auto-completion when country is chosen. However, you can’t choose a county/province that isn’t on the module’s list because validation will fail. Values stored in sites/all/modules/location/supported/location.uk.inc. This appears to be very similar to the file used by the Addresses module.
You can not limit the countries available in the countries field, though you can change the default selection.
It doesn’t gracefully degrade well in the sense that you don’t get a select box but have to type in the field value without any validation of the value entered.
It can’t work with the Conditional Fields module.

Addresses

Install and enable Addresses and Addresses-CCK (in the ‘Other’ section).
Administer -> Site configuration -> Addresses to select country.
There should now be an Address field type available to CCK.
Add the field to a form, then configure ‘Global settings’ section for address details to show (e.g. street, city, etc).

Pros

You can limit the countries available in the countries field.
Address data is exposed to Views via CCK fields.

Cons

County/province changes to a dropdown of available options once country has been selected. However this does not allow you to choose a county/province that’s not in the dropdown because validation will fail. Values stored in sites/all/modules/addresses/countries/uk.inc. This appears to be very similar to the file used by the Location module.
If you don’t enter any address details it defaults to the UK, showing an hcard as such, and you can’t change the default format to be blank.
You can’t reorder address fields for each content type, though you can on a site-wide basis.
You can’t seem to use address (CCK) fields as sort criteria for Views, though they are available as filters!
It doesn’t validate the e.g. State/Province field and doesn’t seem to complain if it’s set as required but no value is given.
If Javascript is disabled it shows province as code rather than full name.
It doesn’t work with the Conditional Fields module.

Hierarchical Select

Note fully ported to Drupal 6 at time of writing (28/06/2009). Most importantly, it isn’t integrated into CCK yet (via Content Taxonomy module).

Install as normal and enable ‘Hierarchical Select’ and ‘Hierarchical Select Taxonomy’.
You should now have various hierarchical select options when you edit a taxonomy’s vocabulary at Administer -> Taxonomy -> edit vocabulary.
Select the option to ‘Use the Hierarchical Select form element for this vocabulary’.

Now, when you create/edit a content type associated with the taxonomy the hierarchical select widget should be used for selecting taxonomy terms.

Content Taxonomy

For a CCK field that can pull content from a taxonomy.

Note that I haven’t found a use for this because taxonomy terms available to a new content type anyway, without the use of a custom field. Could prove useful when it has a larger/better set of display widgets available.

Install as normal and enable ‘Content Taxonomy’ and others (‘Content Taxonomy Autocomplete’, ‘Content Taxonomy Options’). If Taxonomy Manager module is installed can also enable ‘Content Taxonomy Tree’.
Not progressed any further.

Administer Users by Role

Allows users with ‘administer users’ permission and a role (specified in ‘Access control’) to edit and/or delete other users with a specified role.

Install module as normal.
Grant a role permission to ‘administer users’ in the ‘users module’ section of Administer -> User management -> Permissions.
Grant the role permission to ‘edit/delete users with role XXX’ in the ‘administerusersbyrole module’ section.
Users in that role should now be able to edit/delete users with role XXX. They will not be able to change those user’s roles, for obvious reasons (for that see the Role Delegation module).

MAJOR flaws

Does not apply role-based restriction on the administration of users who are only in the ‘authenticated users’ group, hence all authenticated users can be administered by any role granted permission using this module regardless of which roles they should have control over. As soon as a user is added to a role the problem goes away.

Another flaw is that the user can see all the list of all other users. They only get ‘access denied’ when attempting an operation they’ve not been granted access to. One (inadequate) workaround is to create a custom view that lists all users in whatever roles, but this doesn’t stop access to the users list via direct input of URL.

Role Delegation

Grant some roles the authority to assign selected roles to users, without them needing the administer permissions permission.

Install the module as normal.
Allow roles to assign roles via Administer -> User management -> Permissions, ‘role_delegation module’ section.

Content Management Filter

As possible way to remove the need for assigning ‘administer nodes’ permission in order to allow users to view the node creation pages (which defeats the points because it grants permission on all content types).

Taxonomy Delegate

Allow non admin roles to administer certain vocabularies within a taxonomy (without having access to all of them, as the ‘administer taxonomy’ permission grants).

Install the module as normal.
Administer -> Site configuration -> Taxonomy Delegate and hide fields that could undermine security (e.g. related terms).
There should be a new ‘Delegation’ section on a vocabulary’s edit page at Administer -> Content management -> Taxonomy, which allows you to choose which roles may administer the vocabulary.
An item in the navigation menu (called ‘Administer My Categories’ by default) will show up to any roles that have been delegated vocabularies.
A ‘Delegation’ tab on the taxonomy page shows an overview of all delegations for all vocabularies.
The roles do NOT need ‘administer taxonomy’ permission.

MAJOR flaw in v 6.x-1.3

Users in a role will only see their taxonomies if at least one of the other taxonomies is granted to ‘authenticated users’. Worse, this results in anonymous users also getting the ‘Administer My Categories’ menu item, though there are no vocabularies listed on the page. This has been fixed in v 6.x.1.x-dev, see Avoid unnecessary database hit when logged out.

User Read-Only

For read only profile fields.

Install as normal.
Allow/deny different roles the ability to see/edit the account/profile fields via Administer -> User management -> User ReadOnly.

MAJOR flaw

This does not actually prevent the user editing their profile because there is nothing server-side to prevent them submitting a modified form with all the edits they want - the module just adds a hidden field for each disabled one. You can circumvent a “resctricted” field in one of two ways.

Remove the hidden field then enable and edit the original field.
Edit the hidden field.

See Security problems.

Content Profile

Install as normal and enable ‘Content Profile’ and ‘Content Profile User Registration’.
Every existing content type should have a new option to use the type as a content profile and a new tab to configure settings.
There should be a new content type called Profile. We could edit that, but to avoid later confusion with permissions terminology, create a new content type called ‘Peronsal Details’.
Blank out the ‘Body field label’ from the ‘Submission form settings’ section.
Set ‘Use this content type as a content profile for users’ in the ‘Content Profile’ section.
On the ‘Content profile’ tab, set ‘Use on Registration’ in the ‘User Registration’ section and hide the title field.
Normal content permissions apply via Administer -> User management -> Permissions.
Only ‘access content’ permission is needed to allow the user to create their profiles on registration.
Grant ‘edit own personal_details content’ so that the user can edit the profile when they edit their account.
Grant ‘create personal_details content’ so that any new content profile types show up on the account edit page for existing users. This has the disadvantage that the profiles will also be available via the ‘Create content’ link (though it will only edit their existing profiles, it won’t create new ones). Could use the Menu Per Role module to get around this.
Finer grained permission over fields can be achieved using other modules, e.g. ‘Content Permissions’ CCK “sub”-module.

Watch out for the profiles missing from ‘My account’ view. Check permission related settings, e.g. Taxonomy Access Control. Remember to rebuild permissions via Content management -> Post settings -> Rebuild permissions.

Bugs

Even if the profile node’s title is being hidden on registration, it still shows up when the user edits the profile after registration.
If you set the ‘Use on administrative user creation form’ for the content type (‘Content Profile’ tab when editing the type) then the profile’s fields will show when an admin creates a user. However, it doesn’t work as of v6.x-1.0-beta4 with the message “This user already has a content profile of this type”.

Potential problem

If you create a new content profile content type, any existing users won’t have that profile associated with them. To give them the profile you’d have to create a new node of that profile content type and change its author to the user, but this isn’t possible if the user admin doesn’t have permission to change a node’s author. One solution is to use the Override Node Options module to grant them permission to change the author for only profile content types.

Create view of user data including their content profiles

Create the view as normal, adding whichever user fields you’d like to show.
Add a relationship to ‘Node: Content Profile’.
For the relationship settings, if there is a relationship dropdown (which there will be if a relationship already exists in the view) keep it as ‘Do not use a relationship’ because we don’t want to create a relationship that goes via an existing relationship.
Give it a descriptive label.
Select the content type and save.
All fields from the selected content profile type should now be available to add as with any other field.

Note: If you add multiple fields from a relationship at the same time you may get “Column ‘nid’ in field list is ambiguous” errors. This is because each field needs to be edited to specify which relationship to use. The error will go away once this is done.

Override Node Options

Allows node file/authoring/publishing options to be granted to users without ‘administer node’ permission on nodes they can edit.

Install as normal and enable.
Set whether file/authoring/publishing options are collapsable via Administer -> Site configuration -> Override node options.
Set which fields are accessible via Administer -> User management -> Permissions, ‘override_node_options module’ section.

Taxonomy Hide

Hide certain taxonomy terms from view or group them by vocabulary.

Mime Mail

An email module that can send attachments (which default Drupal mail functionality can’t do).

Install and enable as normal.

It provides the following method:

mimemail($sender, $recipient, $subject, $body, $plaintext = NULL, $headers=array(), $text = NULL, $attachments = array(), $mailkey = '');

Attachments is a 2D array, e.g…

$attachments = array(
  array('filepath' => $module_path .'/files/Some_PDF.pdf', 'filemime' => 'application/pdf'),
  array('filepath' => $module_path .'/files/Another_PDF.pdf', 'filemime' => 'application/pdf')
);

Mail key is a unique ID for the message.

To prevent site CSS being used for the email, override the [theme]_mimemail_message($body) method:
```
function [theme]_mimemail_message($body){
  return $body;
}
```

Note that [theme]_mimemail_message can also take the $mailkey as second argument.

See How to Send Email with an Attachment from Drupal.

Bug

It doesn’t seem able to send attachments twice in a row - i.e. when sending multiple emails, the first will have the attachments but latter ones won’t.

Private Download

Restrict access, by a single role, to files in a particular directory (with the help of .htaccess rules).

Install and enable as normal.
Administer -> Site configuration -> Private Download.
Save configuration and the sites/default/files/private directory will be created and contain the suitable .htaccess file.
Grant permission to files in the private directory via Administer -> User management -> Permissions, ‘private_download module’ section.

Bug

It does not work with files that have a + in their filename, e.g. when filename is date stamped using ISO 8610 format.

Best to use in-built private downloads functionality.

File Browser

Allows users to browse the contents of directories, with a number of additional features for e.g. security.

Install and enable as normal.
Create a new directory listing via Create content -> Directory listing.
Grant access to create, view, etc directory listings via Administer -> User management -> Permissions, ‘filebrowser_module’ section.
Remember that content permissions e.g. TAC will be applied, so if you’ve set up TAC to default to deny you’ll not be able to see the directory listing node.

Node Gallery

Feature rich image gallery functionality.

Requires ImageAPI and Imagecache. Lightbox2 used for “lightbox” display of images.

Install modules.
Enable Node Gallery, ImageAPI, ImageAPI GD2, Imagecache, Imagecache UI, Lightbox2, Node Gallery Lightbox2 Integration.
You will have a new gallery content type. Create a new gallery and upload images.

For Lightbox2 display:

Administer -> Site Configuration -> Node Gallery.
Click Edit next to the gallery you’d like to configure.
Click Next on the first config screen (where you choose the gallery and image types, which we’ll leave as default).
In the ‘Original Image Display’ section, set ‘View of The Original Image’ to ‘Enable as Lightbox2 Popup’.
In the ‘Teaser Setting’ section, set the ‘Display Type’ to ‘Thumbnails that open a lightbox2 Gallery’.
In the ‘Gallery Langing Page Setting’ section, set the ‘Gallery Display Type’ to ‘Thumbnails that open a Lightbox2 Gallery’.

Accessibility: With javascript disabled…

All images show as thumbnails like normal but click is to the image only.
Under each thumbnail is a link to the image, but click displays the node that has the image attached!

Views Gallery

Basic image gallery functionality. Requires a whole load of modules, many of which were in beta at the time of writing (26/07/2010).

Install and enable all modules required.
Create a new node of the Gallery content type.
Add photos to it!
THIS DOESN’T WORK :-( … To have alt text set on the image, go to Administer -> Content management -> Content types -> Image -> Manage fields and set ‘[filefield-description]’ as the ‘Default ALT text’ (‘ALT text settings’ section) and tick ‘Enable custom title text’ (‘Title text settings’ section). This relies on the ImageField Tokens module for the [filefield-description] token.

Accessibility

With javascript disabled all images show as thumbnails like normal but click is to the image only.
With javascript disabled a “Start Slideshow” link is still present but does nothing.

Notes: No easy way to delete an image from a gallery.

Galleria

Basic image gallery functionality, though does more than Views Gallery. Based on jQuery. Seems like best gallery as simple, degrades the best and relies on mostly core features and a few common modules.

For good setup, requires the ImageField module (which requires FileField module) and the ImageField Tokens module (which requires FileField Paths module).

Use the ImageField module instead of the core Upload module because it shows thumbnails on the node (gallery) edit page.
So we can have the ALT text automatically set the same as the image title, we use the ImageField Tokens module, as mentioned above.

Install and enable the module as usual.
Install and enable ImageField module and FileField module (that it depends on).
Create or choose an existing content type that will display the Galleria, via Administer -> Content management -> Content types, ‘Add content type’ tab.
Add an Image field (select File in the field type dropdown and Image in the form element dropdown) to the content type in the “Manage fields” section.
Configure the content type Image field via Administer -> Content management ->< Content types -> Galleria -> Manage fields -> Image.
THIS SEEMS TO USE THE IMAGE URL! :-( … In the ‘ALT text settings’ set Default ALT text to [filefield-description] (requires ImageField Tokens module which requires FileField Paths module).
Set the ‘Number of values’ to Unlimited.
Click the “Display fields” section for the content type.
Change the output formatter for “Full node” and/or “Teaser” for the Image type to “Galleria”.
Create a node of this type, add images and view!

Accessibility

With javascript disabled all images show full size on the gallery.
You need to use the ImageField Tokens module so that the alt text can be automatically set the same as the title.

It’s also possible to have the entire gallery display inside a Lightbox or have the thumbnails in a jCarousel.

Simplenews

For mailing lists.

Install as normal, enabling ‘Simplenews’.
It will have created a new content type called “Newsletter issue” (though you can configure it to use your own content type).
It will have created a new tax vocab called ‘Newsletter’ (though you can configure it to use your own vocab).
To allow visitors to subscribe, grant ‘subscribe to newsletter’ to anonymous users via Administer -> User management -> Roles.
Configure via Administer -> Site configuration -> Simplenews.
Enable ‘Newsletter: drupal newsletter’ block via Administer -> Site building -> Blocks.
On subscription, a registered user will have an option to select their newsletters via My account -> Edit -> My newsletters tab.
Create newsletter issues (in a newsletter category aka vocab) via Create content -> Newsletter issue.
Manage subscriptions and send newsletters via Administration -> Content management -> Newsletters.

Note that the ‘Synchronize with account’ option (in Administer -> Site configuration -> Simplenews ‘Subscription’ section) will assume that if there’s an existing user account with the same email as a new subscription request, the user account is owned by the person requesting the subscription, hence will associate the account with the subscription.

There are associated modules to add things like stats.

Calendar

For an events calendar.

Install as normal.
Also enable Date, Date API and Date Timezone.

Then follow Installing Calendar 2.x for Drupal 6. Reproduced here…

Go to admin/settings/date-time/formats
Under Date formats section. Set the 3 date formats to match your needs.

Click on Save configuration button.
Go to admin/settings/date-time
Set the Default time zone: field.

Leave other setting to their default.

Click on Save configuration button.
You must make a custom ‘event’ content type using CCK. To do so go to admin/content/types/add

Under Identification section fill the following fields. Without the “ ”.

Name = “Group Event”
Type = “event”
Description = “Create a new event to appear on the sites calendar of upcoming events”

Under Submission form settings section fill the following fields. Note that those settings are largely a matter of site needs and personal preference
```
Title = “Event”
Body = “Details”
```
Under Workflow settings section decide to best fit your site. It is worth considering unchecking “Promoted to front page” if you expect to have numerous small events posted.
Under Comment settings section make decisions which are appropriate for your site.
Click on Save content type button
On the next screen click on the manage fields link next to your new content type. Note: In this example this screen can be found at admin/content/node-type/event/fields
Add a new field with the following values. Feel free to modify to match your needs.
```
Label = “Date”
Field name = “date”
Type of data to store = “Date”
Form element to edit the data (Widget type) = “Select List”
```
Note: There is some debate over the correct Form element to edit the data (Widget type). The widget type dictates the input UI and is really a matter of preference. It’s easy to change after the fact so try them all and see what you like best.
Click on Save button
On the next page under Group event settings section. Leave the Default value field to Blank.

Note: The calendar module provides a couple of submodules called “Date Popup” and “Date Repeat API”, which allow for nice JS date selection in the first instance and selection of repeated dates in the second. Use the “Date Popup” or “Date Popup and Repeated Options” widget for dates if these submodules have been enabled.

Set the Default value: field to Now.
Note: End user can easily change this value when filling the form.

Set the Input format: field to a format that match your needs. In my case May 12 2010 - 1:00:00pm

Under Global settings section. Check Required option.

Set the Set the To Date: field to Optional.

Leave all other options to their default settings.
Click on Save field settings button.
Note: This is optional but on the next page you can of course add any number of additional fields to your event content type at this point using CCK. I’ve added location and contact information for my application and tied those to weather and profiles which is kind of cool (but way beyond this little write up) and testament to how amazing and powerful Drupal really is :)
We are now going to create a first event. To do so go to node/add In this example click on Group event link.
Fill out the form for your event. In this example we set a From date and a To date
Click on Save button.
In the following steps we will configure your calendar view.
Go to admin/build/views
Click on Enable link located on the right side of the calendar view item.
Click on Edit link located on the right side of the calendar view item.
The next screen is the view edit screen. With the Defaults view already selected. (Screenshot available at original article)

Note: Many types of calendar views are available. Such as Calendar page, Calendar block, etc. But first we will just work with the Defaults view to start.
In the Fields panel. Click on the + button to add a field. (Screenshot available at original article)

Scroll down the list of filters. Then check Content: Date (field_date) - From date option.
Click on Add button.

On the next screen leave all options to their default settings. Then click on Update button.
Still in the Fields panel. Click on the Node: Updated date link.
Click on the Remove button.

Click on Save button.

On the next screen leave all options to their default settings. Then click on Update button.
In the Arguments panel. Click on Date: Date (node) link. (Screenshot available at original article)

Uncheck Node: Update date option.

Check Content: Date (field_date) - From date Note: This set the start time of your event instead of the node update time as the argument for the view.
Click on Update button.
On the Filters panel click the + button to add a new filter.
Scroll down the list of filters. Then check Node: Type option.

Click on Add button.

On the following screen leave Operator to Is one of.

Then check Group events option. This will limit your calendar to only the Group events content type.

Click on Update button.
On the Sort criteria panel click the + to add a new criteria.
Scroll down the list of filters. Then check Content: Date (field_date) - From date option.

Click on Add button.
On the next screen leave default settings to Ascending.
Then click on Update button.
Click on Save button to save all your edits.
To test click on View "Calendar page" link. (Screenshot available at original article)
That’s it. You have successfully install and configure the Calendar module 2.x for Drupal 6.x (Screenshot available at original article)
Note that this handbook will at least get you to a working calendar of coming events for your site. Obviously you’ve got a ton of configuration options to play with form here.

Events list view, filtered by date

Add new page display to calendar view.
Override trivial items like page name, path, etc.
Override ‘distinct’ to be ‘Yes’ to prevent repeated events showing multiple times (this also works around a bug whereby repeated events only show from date not date of repeat).
Override default sort criteria and to have list newest events first set to order by from date desc then updated date desc.
Override filters and add exposed date (node) filter, with ‘in between’ operator, looking at from date and to date, using OR condition.
To prevent repeated dates showing on event, as there can be way too many, edit the event content type and change its date display to show only 1 value.

Webform

For creating online forms to gather info for email. Each form is associated with a content type. Form submission sends email only, it doesn’t create a node (as would be the case if you used normal Content Types (with CCK) and Trigger to send email).

Install as normal.
Settings are at Administer -> Site configuration -> Webform settings. Defaults are fine.
Create a new Webform via Create Content -> Webform. Give the form a title that indicates its purpose (e.g. “Feedback”).
After creation, visit the form and add/remove fields from the form via Webform -> Form components.
Add email recipients via Webform -> E-mails.
Change behaviour after submission via Webform -> Form settings.

Note: If you’re using a “section menu” via f3’s custom section menu module, you can have the webform confirmation page show in the correct section by adding a disabled menu item for it.

Webform Validation

Adds extended validation support to webforms, e.g. regexp based validation.

Content Display Order

Adds a ‘Display order’ tab to content types, so the order of fields can be changed for all displays.

Install as normal.
Edit content type and reorder fields as desired!

Modules good for development

Devel

Devel and Theme developer.

Install package as usual.
Enable ‘Devel’ and ‘Theme developer’ modules.
Enable the Development block in Administer -> Site building -> Blocks.
Tick ‘Themer info’ box at bottom left of screen to activate.
Move mouse over page element you’re interested in and click to see template/function hierarchy.

Others

As recommended by developer of CCK and date stuff.

CCK
Views
Token
Devel & Devel Generate
Advanced Help
Backup and Migrate or Demo
Reroute Email
Admin Menu or Admin
Admin Role
Admin theme:
- Root Candy
- Seven
- Cleanr

Potential modules

Kaltura

Kaltura for video.

Last modified: 16/11/2011 Tags: drupal, drupal 6

Skip to

Current location

Drupal 6 modules

Index

Essential Modules

User protect

Token

Pathauto

Auto-generate all aliases

Configure alias formats

Create aliases for pages that don’t yet have them

Recreate pathauto URL aliases

XML sitemap

i18n

Menu Breadcrumb

Gotchas

Menu block

Conditional Stylesheets

Search

Customisation

Search configuration

Better Formats

WYSIWYG

IMCE

IMCE Wysiwyg bridge

IMCE mkdir

Custom Permissions

Access Control

Core private downloads

Core permissions

View own

Content Access

Block Access

Bugs

Forum Access

Taxonomy Access Control (TAC)

Taxonomy Access Control Lite

Data import

Table Wizard

Schema

Additional modules

Secure Pages

Editable blocks

Backup and Migrate

Filefield Sources

Filefield Paths

Imagefield Tokens

MultiLink

CKEditor

CKEditor Link

Link Checker

Upload

Profile Category Weights

Protect Critical Users

Menu Subtree Permissions

Caveats

Menu Admin per Menu

WYSIWYG Filter

Embedded Media Field

Node Picker

Poor Man’s Cron

Locale, Content Translation, i18n and Language Icons

URL aliases

Gotchas

Translation 404

Forums

YUI Editor

Advertisement

Views Slideshow

Taxonomy Menu

Nodecarousel

Trigger

Rules

Flag

Meta tags

Filter By Node Type

Filter By Content ?

Devel module

Mass Contact

Auto Assign Role