User login

Modules to Use: Drupal 5

Drupal 5 contributed modules as of 2007 January 29

(+ means included in the default Agaric's site recipe creator)

+image
+http://drupal.org/project/image

+imagecache
http://drupal.org/project/imagecache

+http://drupal.org/project/article
The article module allows for nodes of any type to be organized and displayed in a centralized location. This allows the site administrator to organize nodes of several different types in one place. The user can navigate the nodes by selecting different categories in the taxonomy tree associated with the article module.

+http://drupal.org/project/autosave
The autosave module automatically saves a node after a period of time using AJAX. All autosaved content are saved as revisions to ensure no content is overwritten.
This module requires the Form plugin (with AJAX) for jQuery: http://jquery.com/dev/svn/trunk/plugins/form/form.js?format=txt

CCK
+ http://drupal.org/project/email
+ http://drupal.org/project/text_regexp

At the simplest level, this module allows to hide a menu until some of its items has become the active item (by reaching the corresponding url). This is easier than configuring the menu's block visibility for each possible path contained in the menu.

This module can be used to make a "contextual secondary menu" based on the primary links (e.g. you set the Primary links menu for "Allow trimming for this menu, hide menu when no item is active", activate the "Primary links (Menu trim)" block, then edit the menu's top-level items to check the "Trim parent items" option). After that, when an item is selected in the primary links, the contextual menu appears, showing only the subitems of the selected item. Drupal already allows contextual "secondary links" based on the primary links, but these secondary links are limited to a flat list of items. Menu Trim, on the other hand, can display complete menu subtrees.

This module can also be used in any menu to trim parents when reaching deep menu items. This can make deep menus more usable, and the breadcrumb will still show the full path.

Release Monitor
+ http://drupal.org/project/releasemonitor

[My module must work with this!]

This is a Site Administrator Module that assists with keeping contributed modules up to date and summarizing their upgrade availability.

The current CVS head version (5.x-1.x-dev snapshot) works in both 4.7 and 5.

The Release Monitor reads the current version information of enabled contributed modules from the module.info file if they are available, from CVS/Tag and the CVS $Id$ string. Using cron, it gets the current version information to determine if there are minor or major upgrades available. The Monitor displays this information on a single page and creates watchdog events when an upgrade is available. To make downloading easier, it gives links to the Drupal project page, and the CVS repositories (if appropriate).

The monitor currently gets version information from cvs.drupal.org, but future versions whould get this information from the drupal.org project.module. The monitor pulls module information once per day, although this is a configurable option.

http://drupal.org/project/gsitemap (XML Sitemap)

Drupal 5 contributed modules as of 2007 January 29

(+ means included in the default Agaric's site recipe creator)

+image
+http://drupal.org/project/image

+imagecache
http://drupal.org/project/imagecache

+http://drupal.org/project/article
The article module allows for nodes of any type to be organized and displayed in a centralized location. This allows the site administrator to organize nodes of several different types in one place. The user can navigate the nodes by selecting different categories in the taxonomy tree associated with the article module.

+http://drupal.org/project/autosave
The autosave module automatically saves a node after a period of time using AJAX. All autosaved content are saved as revisions to ensure no content is overwritten.
This module requires the Form plugin (with AJAX) for jQuery: http://jquery.com/dev/svn/trunk/plugins/form/form.js?format=txt

CCK
+ http://drupal.org/project/email
+ http://drupal.org/project/text_regexp

At the simplest level, this module allows to hide a menu until some of its items has become the active item (by reaching the corresponding url). This is easier than configuring the menu's block visibility for each possible path contained in the menu.

This module can be used to make a "contextual secondary menu" based on the primary links (e.g. you set the Primary links menu for "Allow trimming for this menu, hide menu when no item is active", activate the "Primary links (Menu trim)" block, then edit the menu's top-level items to check the "Trim parent items" option). After that, when an item is selected in the primary links, the contextual menu appears, showing only the subitems of the selected item. Drupal already allows contextual "secondary links" based on the primary links, but these secondary links are limited to a flat list of items. Menu Trim, on the other hand, can display complete menu subtrees.

This module can also be used in any menu to trim parents when reaching deep menu items. This can make deep menus more usable, and the breadcrumb will still show the full path.

Release Monitor
+ http://drupal.org/project/releasemonitor

[My module must work with this!]

This is a Site Administrator Module that assists with keeping contributed modules up to date and summarizing their upgrade availability.

The current CVS head version (5.x-1.x-dev snapshot) works in both 4.7 and 5.

The Release Monitor reads the current version information of enabled contributed modules from the module.info file if they are available, from CVS/Tag and the CVS $Id$ string. Using cron, it gets the current version information to determine if there are minor or major upgrades available. The Monitor displays this information on a single page and creates watchdog events when an upgrade is available. To make downloading easier, it gives links to the Drupal project page, and the CVS repositories (if appropriate).

The monitor currently gets version information from cvs.drupal.org, but future versions whould get this information from the drupal.org project.module. The monitor pulls module information once per day, although this is a configurable option.

http://drupal.org/project/gsitemap (XML Sitemap)

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.