This module provides a new view style which lets you assign taxonomy terms to the nodes in the view. Use this to quickly add tags to a group of images or other content.
The module supports all the default taxonomy module form widgets as well as the widgets provided by the Active Tags and Hierarchical Select modules.
This module will restrict URLs that can be shortened by the shorten module by top level domain (TLD). You can use it to allow only .gov URLs to be shortened, for example.
This module provides a simple select list above the node body field on all node add and edit forms (for users appropriately permissioned) allowing users to pick the name of a saved snippet of mark-up to place in the node body field. It will replace the contents of the node body field entirely with the saved snippet.
Users can save a snippet by creating mark-up in the node body field and specifying a new snippet name in the Mark-up Snippets interface. If a name is provided (and it is unique) then a new snippet will be saved in the database when the node is saved for later use.
Permit own permissions provides a new permission, share permissions, and anyone given this permission can add or remove any permission she has from any role. They will be able to access admin/people/permissions
A site is beautifully set up and guards against catastrophic user error (blowing things up) while giving the person you made it for as much flexibility and power to add to it as is possible... almost.
This module was created to fill the need for *two-dimensional* environment/host management.
* What's an environment? An environment is a development or server location where a full Drupal build (possibly including multiple hosts) is set up. In our work, we tend to have
1) a primary 'dev' environment (site.dev.ourwork.com),
2) local environments for each developer (site.dev.local),
3) a staging environment (staging.site.com),
4) a live site (www.site.com), etc.
But each of these environments can have multiple sites/hosts, making the number of actual hosts to track and toggle grow exponentially.
The domain_access module does a good job of tracking hosts, but in only one environment.
The goal for now is not to manage deployment between multiple environments, but rather to allow for managing content between the environments, and more generally to have code- and user-level context awareness of each environment. The module is currently a barebones API, to be expanded upon for various use cases. I'm interested in hearing what use cases people have.
Envts has no UI yet, but simply allows other modules to define environments with a hook. (Anyone is welcome to create a UI for the module, since my time is limited!)
This module enables you, with very easy UI, to set or unset cookies for users when they login or logout from your site.
use cases:
* Some CDN allow bypassing CDN cache when a special cookie with specific value is set for a site visitor.
* *add more use cases*
This module lets the administrator see all administration pages in her preferred language.
You can use this to display the frontend of the site in one language and still keep most of the backend in English (or another language of your choice).
CASAA is a framework that allows admins to group systems such as Omniture Site Catalyst, Google Analytics, Yahoo APT, and other such services, and manage them from a single interface.
Through the interface, mappings, or tags as some refer to them, can be created across the site using URL paths or taxonomy terms to place specific values over content, sections, and other areas of the site.
With the developer's API, developers can easily create new plug-ins for the framework to support any service you wish.
What's new in 2.x:
This module has been integrated within Views Hacks. Its development will continue there.
This module exposes blocks as Views objects.
Sentry client is the lightweight client component for the central site monitoring tool Drupal Sentry. It allows administrators to monitor any number of Drupal based sites from one central location.
Feature requests (sentry should monitor this or that) should be submitted to the server issue queue as the client module will be updated together with the server.
