Fast Permissions Administration. This module is here to alleviate frustration when trying to manage permissions in Drupal.
By providing a better permissions interface hopefully a few innocent keyboards and mice can be saved. All features work on all modern browsers and IE8+, unless otherwise noted. Filtering: Advanced User. Details.
Devel. A suite of modules containing fun for module developers and themers ...
Devel Helper functions for Drupal developers and inquisitive admins. Field group. Fieldgroup will, as the name implies, group fields together.
All fieldable entities will have the possibility to add groups to wrap their fields together. Fieldgroup comes with default HTML wrappers like vertical tabs, horizontal tabs, accordions, fieldsets or div wrappers. The field group project is a follow-up on the field group module in CCK. The release will only exist for Drupal 7 release and higher, so since the existence of the Fields API in core. Advanced help. The advanced help module allows module developers to store their help outside the module system, in pure .html files.
The files can be easily translated simply by copying them into the right translations directory. The entire system can appear in a popup or not as the module prefers (and by taking away access to view the popups, a site can force the popups to not exist). The system ties into Drupal's search system and is fully indexed, so the entire contents can be searched for keywords. the help files can be placed in a hierarchy as well, allowing for top down navigation of the help. Administration menu. Provides a theme-independent administration interface (aka. navigation, back-end).
It's a helper for novice users coming from other CMS, a time-saver for site administrators, and useful for developers and site builders. Administrative links are displayed in a CSS/JS-based menu at the top on all pages of your site. It not only contains regular menu items — tasks and actions are also included, enabling fast access to any administrative resource your Drupal site provides. Showcase and Quality Assurance Test-drive in various themes on the demonstration site or watch a short demo reel or a installation tutorial video. Behaviour and Integration.
Token. Tokens are small bits of text that can be placed into larger documents via simple placeholders, like %site-name or [user].
The Token module provides a central API for modules to use these tokens, and expose their own token values. Note that Token module doesn't provide any visible functions to the user on its own, it just provides token handling services for other modules. For Drupal 6, the Token module provides a "Token Actions" module which can be enabled separately. This provides several "actions" for the Drupal core Actions/Trigger modules to use that take advantage of the Token replacement functionality. Modules that use the Token module and provide tokens via the API include Organic Groups, Pathauto, Comment Notify, and Commerce. Pledges. Pathauto. The Pathauto module automatically generates URL/path aliases for various kinds of content (nodes, taxonomy terms, users) without requiring the user to manually specify the path alias.
This allows you to have URL aliases like /category/my-node-title instead of /node/123 . The aliases are based upon a "pattern" system that uses tokens which the administrator can change. Requirements Versions. Entity API. This module extends the entity API of Drupal core in order to provide a unified way to deal with entities and their properties.
Additionally, it provides an entity CRUD controller, which helps simplifying the creation of new entity types. Requirements. Rules. The Rules module allows site administrators to define conditionally executed actions based on occurring events (known as reactive or ECA rules).
It's a replacement with more features for the trigger module in core and the successor of the Drupal 5 workflow-ng module. Example use cases Build flexible content publishing workflows changesSend customized mails to notify your users about importantCreate custom redirections, system messages, breadcrumbs, ...Build an eCommerce store using Drupal Commerce And many more... Features Obviously, you may use reaction rules to react upon any event with custom conditions and actions.Allows functionality to be re-used via components (Drupal 6: Rule sets only).Flexible scheduling system that allows scheduling any component / action.Users can share their customizations by using the built-in import/export feature.
Integrations Modules may use the Rules module's API to provide new events, conditions, actions or default rules, which can be customized by users. Context. Context Context allows you to manage contextual conditions and reactions for different portions of your site.
You can think of each context as representing a "section" of your site. For each context, you can choose the conditions that trigger this context to be active and choose different aspects of Drupal that should react to this active context. Think of conditions as a set of rules that are checked during page load to see what context is active. Any reactions that are associated with active contexts are then fired.
Chaos tool suite (ctools) This suite is primarily a set of APIs and tools to improve the developer experience. It also contains a module called the Page Manager whose job is to manage pages. In particular it manages panel pages, but as it grows it will be able to manage far more than just Panels. Views.
You need Views if You like the default front page view, but you find you want to sort it differently. You like the default taxonomy/term view, but you find you want to sort it differently; for example, alphabetically. You use /tracker, but you want to restrict it to posts of a certain type. You like the idea of the 'article' module, but it doesn't display articles the way you like. You want a way to display a block with the 5 most recent posts of some particular type.
Views can do a lot more than that, but those are some of the obvious uses of Views.