Administration

Add client-side dependency checking to Modules Administration page.

If you have ever been frustrated having to submit the Modules page multiple times to turn off a set of nested modules, this module is for you. When you click a checkbox to turn on a module, it also turns on all the modules it depends on. And when you turn off a module, it turns off all of the modules that depend on it.

Super simple, and on my list of things to try and get into Drupal 7.

This module allows an administrator with "administer taxonomy" permission to delegate the administration of a vocabulary to a non-admin role.

The role to which this authority has been delegated may add, modify, and delete terms from a vocabulary. They may, not however, modify the vocabulary itself, nor may they create new vocabularies.

Given that Forums are controlled by a vocabulary, one might give the ability to control them to someone who has no other administrative rights. They can then change the "containers" (parent terms) and forums (child terms). Other popular modules that are vocabulary driven are Image Gallery and Glossary, so they are functions that can be easily delegated. There are many ways in which this module can help.

Adds an "Apply" button to the block configuration forms which saves any changes and redirects back to the block configuration page. Enables quicker custom block development.

Note: The code on CVS here is out-of-date. Please use the repository on github.org: http://github.com/tomm/drupal-indymedia-alba/tree/master

A set of modules intended to make drupal more suited to an open publishing website such as Indymedia. Modules include:

Drupal's block module is limited by the fact that a block can only have one instance. Each block has a 1:1 relationship with its region, weight, visibility (and other) settings. This means that it is impossible to have blocks in multiple regions or to have blocks that have different settings on different pages.

MultiBlock module solves this problem by allowing you to create multiple Block Instances of already existing blocks. Please read the README for more information.

Drupal 8

The functionality this module provides is included in Core

This is a quick little module to allow you to selectively apply nofollow to menu items and taxonomy terms to allow 'sculpting' of pagerank - effectively allowing you to focus search engines' attention on particular areas of your website by controlling the flow of link juice around your website.

This can be useful for large websites, by moving the focus away from links repeated on every page (About us, Contact Us, Privacy Policy, T&Cs etc) and onto the content itself, whilst still allowing you enough granularity to ensure these pages are indexed, somewhere.

This module enables granular publish and unpublish permissions which allows you to grant roles on your site the ability to publish or unpublish specific content types without having to give them the administer content permissions. This is a lightweight solution to managing your content workflows.

Version 8.x-1.x

This is now under development!

This module was meant as a proof of concept and has been abandoned. Drupal 7 has vertical tabs out of the box (huzzah!), while the Vertical Tabs module provides vertical tabs for Drupal 6.

Complex websites and web applications can be created by combining configurations of Modules, Content Types (CCK,) Views, Panels, Menus, Blocks, Categories, Roles / Permissions, etc. This site setup and configuration process is a very time consuming and repetitive bottleneck.

Patterns module is built to bypass this bottleneck by managing and automating site configuration. Site configuration is stored in XML or YAML (requires SPYC YAML parser, which needs to be downloaded separately from http://code.google.com/p/spyc/) called Patterns which are easy to read, modify, manage, & share and can be executed manually or as a part of an automated web site deployment.

This module generates an RSS feed for node revisions. This allows users to subscribe to updates to individual nodes. This functionality is particularly useful for tracking changes to collaboratively developed content on auto-revisioning node types.