Under active development

Finds all external links on a web page and adds an "external" icon to the link indicating it will take the user offsite or a "mail" icon for mailto: links.

This module allows you to take snapshots of your site. It turns a Drupal installation into a sandbox that you can use to:

• Try out and test new modules, configuration, etc.
• Set up a public demonstration site for a contributed module or theme.
• Develop and test update and upgrade paths.

Whenever you need to reset your site to the state of a saved snapshot a click of your mouse will do so.

With cron enabled, a site can be automatically reset to a chosen snapshot in a definable interval.

With the Protected Node module, users can restrict access to a node with a password they provide when creating the node (or a site wide password or a per node type password).

Flickr Rippr reads flickr.com for users latest public photos, and turns these into content (nodes) on your drupal website.

You need only publish to flickr.com, and they will automagically appear on your drupal website after each cron run. Join this up with the Views module and make photo galleries, blocks, and other awesomes.

Example available on author's blog: http://coffee.geek.nz/photos

requires the Flickr API module.

Features

• Import latest (or all) photos for a flickr user
• Multiple flickr accounts per drupal user
• syncs tags from flickr.com as terms in a drupal taxonomy vocab.
• syncs comments from flickr, saved as drupal comments
• Can be configured to only import photos with a chosen tag or tags
• Views Integration - photos, metadata, comments, tags, geo data, flickr accounts
• Import latest photos from flickr group (new, beta, nodes will be owned by anoymous)
• Configurable size of jpegs on teaser or full page view
• Option to save jpeg photo file locally on your sever instead of serving from flickr.com
• Import latest photos on hook_cron and/or manual update of individual accounts.
• Integration with Shadow Box module

Icecast YP directory.

Assign permissions to vocabularies by user role.

The core taxonomy system allows vocabularies to be assigned to node types. This module extends that by allowing the editing and/or display of the vocabulary to be controlled by user role. It attaches itself to the vocabulary add/edit form and gives the administrator three options for each role - (1) edit and view, (2) view only, and (3) none.

This module makes it possible to create a vocabulary for administrator purposes, hide this category from most users, and then use the category as a views filter.

Here are two use cases:

• a vocabulary that had the terms "special offers", "front page", "user advertisement", etc; this vocabulary could be used in various views to pull the tagged content into a particular block or page.
• a vocabulary that had the terms "editor post", "editor tagged", and "community post" and a role type of "editor" that was less than an admin, but had privilige to write editorial content (as opposed to unedited community content), but also had permission to tag community content as something that was propogated to higher visibility.