Maintainers strive to actively monitor issues and respond in a timely manner.

Protected Node

A protected node

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

flickrrippr2.png

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

Vocabulary Permissions

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.

Drupal Developer

This is an install profile designed to jump-start module development. It rewrites the install forms, providing a default username and password of admin/drupal (this has changed from the old package which was drupal/drupal). It also installs and configures developer modules like devel and coder.

Default username and password: admin/drupal.

WARNING! This profile contains potentially dangerous user settings, permissions, do not use it on a live site.

Installation and update

Either download the large tarball below, or create a small makefile (also packaged with the distribution):

api = 2.x
core = 7.x
projects[] = drupal
projects[drupal_developer][type] = "profile"
projects[drupal_developer][download][type] = "git"
projects[drupal_developer][download][revision] = "7.x-1.x"

Use it with drush make like so: drush make dd.make [mysite], where dd.make contains the text above and [mysite] is the target directory to build the new site in.

Modules within the package

  • devel
  • admin menu
  • coder
  • features
  • grammar_parser
  • schema
  • xhprof

Suggestions and issues

Translation template extractor

The Translation template extractor provides a web based and Drush-integrated Gettext translation template extractor interface for Drupal as well as a reusable API to look for translatable strings and translatability errors.

Pages

Subscribe with RSS Subscribe to RSS - Actively maintained