Under active development

Tagadelic provides an API and a few simple turnkey modules, which allows you to easily create tagclouds, weighted lists, search-clouds and such.

With the API you can build a module with a few lines of PHP, to turn anything that can be counted into a weighted cloud. Which can be presented to your users anyway and anywhere on your site.

With the turnkey modules, you can add a page that shows taxonomy-terms in a weighted cloud: terms that are used more often are bigger. Another module provides a page that shows article-titles in a cloud: titles from articles that are read more often appear bigger.

Tagadelic 2.x branch is work in progress and should only be used by people who plan to develop for and with it.

Tagadelic 1.x branch is stable for Drupal 6 but unstable for Drupal 7. End-users should use Drupal 6, 6.x-1.x versions. End-users are strongly advised not to use Drupal 7, 7.x-1.x of tagadelic; it has known bugs, yet is reported to work for some people. Use at own risk.

The User Badges module allows each user to be assigned 'badges' which can be displayed as a series of iconic images.

A popular use is to display the badges along with the user's information within forums, comments, or node postings. These badges can be assigned individually by the administrator or attached to a role so that, for example, all users in the 'admin' role will show the 'Administrator' badge which could display as a graphic letter 'A'.

Any badge can optionally be associated to a URL that links the image to a description page. If a user has more than one badge, there is also a mechanism that allows administrators to only show the highest-level badge. You can also set a special badge for blocked users and even override their role badges with this one.

User Badges can be used as a way to establish trust (in the same way as eBay's star graphics), or as an incentive for users. They can also be a quick way to identify moderators, administrators, or anyone with a given role.

Drupal 6

This module also works with the ecommerce package, allowing product purchases to trigger badge assignment. In order to upload badge images you need to have the Upload module enabled.

• The 6.x-1.x-dev now has rules integration.

CronPlus adds more "cron" hooks to Drupal beyond the basic one, with each of the new hooks being called at or near specified time intervals (hourly, daily, weekly, monthly, and yearly).

Component module (for use by other modules).

Useful for any other module that creates output outside of the Drupal website and need to include links back to the site which contain the identity of a site member. For example, it could be used in an email, personalised PDF, SMS, RSS feed, or voice message to identify the user it's for.

Features

1. Autoloader — @see go_autoload()

- To disable this feature, in settings.php, define GO_DISABLE_AUTOLOAD constant.
- Run faster with APC extension enabled.

2. go_cache()

Without go_cache()

  function your_data_provider($reset = FALSE) {
    $cache_id = '…';
    $bin = 'bin';
    $expire = strtotime('+ 15 minutes');

    if (!$reset && $cache = cache_get($cache_id, $bin)) {
      return $cache->data;
    }

    $data = your_logic();

    cache_set($data, $cache_id, $bin, $expire);

    return $data;
  }

With go_cache(), your logic becomes cleaner:

  function your_data_provider() {
    return your_logic();
  }

  $data = go_cache(array('cache_id' => '…'), 'your_data_provider');

3. Useful drush commands:

  # Download libraries
  drush godl ckeditor
  drush godl jquery.cycle
  drush godl jquery.cycle.2
  drush godl colorbox
  drush godl maxmind.geolite.country
  drush godl maxmind.geolite.country ipv6
  drush godl maxmind.geolite.city
  drush godl maxmind.geolite.city ipv6

  drush godev
    Shortcut for quick dev enviroments.

  drush golive --cache=1 --js=1 --update=1

    This is wrapper command for useful auto configuration for live site:
      - Enable page/block caching
      - Enable js/css aggregation

Taxonomy Defaults allows you to assign default terms from any vocabulary to any node-type. The default terms will be pre-selected on the /node/add form, but can be edited.

If a vocabulary is marked as "Hidden" for a particular content type, then that vocabulary will not be shown on the /node/add form and the default terms will be assigned automatically and cannot be edited.