Developer tools

Usecase: let's imagine you want to create some specific tools to allow your users reviewing some nodes (for instance a CCK-audio review, a CCK-text review, a complex-type-CCK review, ...). Let's also imagine you want them to review specific (ie, an admin can set that before) CCK-node types, then you've got it, it's basically what custom review is about.

Some vocabulary :

• the reviewer: the CCK-node type seen as a tool set by an admin to allow users reviewing specific other CCK-node-types
• the reviewee: the CCK-node type seen as the type one can review with a specific reviewer
• the review: an instance of reviewer (like an advanced comment if you want)
• the (node) reviewed: an instance of reviewee (the node the user has been reviewing)

It allows only one review by person and by reviewer type on each node. So it's neither
a tool to make comments nore supercomments, but real nodes associated in a specific way to an original one. These reviews are usually seen from the original reviewed node.

The Blog Reactions module monitors Technorati, Google Blogsearch, Yahoo! Bloglines and Blogato for reactions - trackbacks - on your posts. It displays a date and a short summary and links back to the original reaction on the web.

By default, the Drupal 6 trigger module displays appropriate actions for each trigger. Each action has declared which hooks it is appropriate for.

Parallel to the Services module, the Clients module provides the ability to implement pluggable clients to external web services, including external Drupal sites running the Services module, the main use case being connecting to other Drupal installs via the Services module with either the REST or XMLRPC server.

Clients module allows you to create connections to remote services with an admin UI. These handle fetching a result from a remote service. Different types of connection are provided for different types of services. There is a Drupal client connection type for different versions of Services (5.x-0.92, 6.x-2.x, 7.x-3.x), hence Clients can be used to connect to sites with different versions of Drupal.

Resources can be defined on top of connections, which provide an abstraction layer so that other parts of Drupal can work with remote data without needing to know anything about the connection. An example module for remote Views blocks is included.

Connections and resources can be exported to Features. The UI also provides a system for testing connections are correctly set up and functioning, which can be extended to provide site-specific tests.

Requirements

3.x branch:

• Entity API
• CTools

2.x branches:

• CTools

This module provides a set of blocks which show 'related' content based on a selected term.

Post Also lets you post simultaneously to multiple sites.