Content display

Top Commentators module provides a usable and easy way to create block of best commentators on your site.

Vertical Tabs module allows you to output form (in our case, node form) fieldsets as vertical tabs. Vertical Tabs Default Tab advances this behaviour, allowing you to move remaining top level node form elements (such as title and body) into default vertical tab, leaving only buttons below. This reduces height of node forms, greatly improving usability for complex content types with lots of fields/fieldgroups.
Contains code from #357300: Place all top level form elements into a default vertical tab group.

Custom Node Template allows one to specify different node templates to be used on a node by node basis.

While there are many options for customizing the display of pages, fewer options exist for customizing the display of nodes. There are many instances in which customizing the display of specific nodes might be useful, and this module provides a simple and efficient way to achieve this.

Using This Module vs. Other Solutions

If you are looking for a way to customize the display of all nodes within a content type this module would probably not be useful. While you can specify a node template to be used by default for a content type using this module, it only applies to nodes you create in the future. There are better solutions for customizing the display of content types - probably the best way is to just do this through your theme. You may also find some other helper modules to be useful. One of the main reasons for using this module would be to customize or override the display of specific nodes differently from the default display of those nodes. Please see the module's handbook page for additional information.

Please see the Custom Node Template Handbook page for additional information and use cases to help you decide if you should use this module/.

How do I Use This Module?

For users with appropriate permissions, a list of all node templates available in a theme are presented when creating or editing a node. Any node template can be selected to be used to display a particular node. Specific node templates can also be assigned to content types as a default. If a node template is not selected for a content type and specific node, then appropriate node template will be used by a theme as it normally would (per existing node template suggestions).

Successor of FeedAPI ImageGrabber, to support Feeds module.

Features

Feeds Image Grabber will concentrate more on efficiency, rather than features. Please put your feature requests in the queue except what is already in the FeedAPI ImageGrabber queue.

Road Map

Feeds Image Grabber for D6 will be released once Feeds overtake FeedAPI. D7 version will have to wait till D7 releases. :)

If anyone is interested in porting FeedAPI ImageGrabber to Feeds Image Grabber for D6 earlier than scheduled, please contact me (I will help you to get through this).

Widgets is a module that enables a site editor to, on a per node basis, select "widgets" that should be displayed when viewing a node. A "widget" in it's simplest form is just a regular node (page, story etc) but the power of the module is that you can create custom content types (with CCK) to use as "widgets". You could say that Widgets brings the power of the block right into the node edit form.

Prerequisites

Widgets depends on the modules jquery_update (version 6.x.2.x-DEV) and jquery_ui. The current version of jquery_ui, 6.x.1.3, ships with jQuery UI version 1.6. The jQuery Multiselect widget requires jQuery UI version 1.7. Follow the directions to upgraded jQuery UI to version 1.7 in the README.txt of the jquery_ui module.

Roadmap

Functionality that might be implemented in the future.

• Support for multiple regions
• Expose Widgets to site users
• Ability to create "sets" of widgets
• Inherit widgets from menu item higher in hierarchy

Drupal 7

Drupal 7 will implements CCK in core (Fields). This opens up for the possibility to use blocks instead of nodes for widgets as blocks now will support custom fields. Will have a look at this when D7 is released.

Credits

Block Content Per Role allows a block to be defined which contains content that is displayed depending on a weighted set of roles. This is useful, for example, if you want one block for a subscriber role, one for authenticated and one for anonymous.

This is difficult to do with Drupal out of the box as a users with the subscriber role will also be logged in and therefore also have the authenticated role. The Blocks system in Drupal does not allow a "complex" selection such as "Users with roles XYZ but not ABC".

Each role's content is run through Drupal's filter system. This allows you to use any of the contributed modules which provide new features. I can strongly recommend the Token Filter module (along with its dependency, Token). This module allows you to define an input format which converts tokens in the content to their value. Why is this useful? Using the Token Filter module you could (once an input format is configured) add the following to any content for an authenticated role: [token global user-name]. This block will then dynamically contain the current user's name in the block.