Unsupported

(abandoned)

tobedeleted

This project is a wrapper for all the core features that is distributed with the NodeStream profile.

Although these features aren't meant to be used outside of NodeStream, the goal is to be Kit compliant so features independently can be turned on and off.

For bug tracking, please refer to the NodeStream profile issue queue.

Comment and Share with friends.

Note: As of 2013-08-30, this module appears to no longer be supported. If you are interested in taking this module over, or you as the module maintainer feel this message has been posted in error, please reply to https://drupal.org/node/2035581.

Module Description

Chuck provides a set of "roundhouse kicks" - extreme[ly effective] solutions to common Drupal problems. Each roundhouse kick can be enabled/disabled.

It's hard sometimes to find certain module if you're using a bunch of modules. This module helps you to find the module faster.

This module provides a views style plugin that outputs sparkline style charts using the Flot Javascript library. It has options for style (bar or line) and color, as well as default styles that are appropriate for sparklines.

This module is obsolete, since this way to install PEAR no longer works.

Provides integration with the PEAR framework.

Includes a helper that downloas the library through http://pear.php.net/go-pear.

Most PEAR's contributed libraries try to include files directly from the root, example:

require_once 'PEAR/library.php';

Go pear provides a way to swich on/off the default include_path to work easily with them.

Allows Drupal to create Kwicks-like menus.

Official kwicks website:

http://www.jeremymartin.name/projects.php?project=kwicks

INSTRUCTIONS

1. Go to admin/build/modules and enable Kwicks.
2. Go to admin/settings/kwicks and set the number of Kwick menus you will use.
3. Go to admin/build/block and configure your Kwicks block. Then move the block to the desired region.
4. Enjoy!

CCK reference filter enhances the user experience and ensures data integrity in a number of common use-cases involving node references:
o from an originating node to a destination node, or
o from an originating node to a destination user.