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: The permissions page now provides a search field that will filter the permissions UI on-the-fly, allowing you to instantly find the permission that you are looking for. You can also filter on the module a permission belongs to using the @ symbol:permission@module For example, if you want to show only permissions that contain the word admin for the comment module you would enter:admin@comment Quick module filter: You can click on module names in the list to the left to instantly show only that module's permissions. If you already have a filter value, it will apply that to the newly selected module. System name filtering: The basic permission@module filtering now matches on the system name as well, as they can be different.
Advanced User. Details The advanced user module allows the filtering of users based on the user.module fields and optionally the profile.module fields. The fields available for filtering can be configured using the module settings. Eg. Site admin may search through 1000s of users to display all users who have not accessed their account. Once the group of users with selected common denominators are filtered, the module can be used to perform functions that email, block, unblock, add or remove roles, or delete. I am looking for a co-maintainer of this module. NOTE: Version 6.x-3.x or 7.x-3.x is the release to use. Advuser-6.x-3.x Pay close attention I have begun the modifications for feature enhancements.
Advuser-7.x-3.x The -dev version is functional I have converted the Advanced User to Drupal 7 using the 3.x series. Module Functions Known to work The filtering process works great. I have tested using the devel module mail wrapper the email functionality and have seen that the mail appears to work. Devel. A suite of modules containing fun for module developers and themers ... Devel Helper functions for Drupal developers and inquisitive admins. This module can print a summary of all database queries for each page request at the bottom of each page. The summary includes how many times each query was executed on a page (shouldn't run same query multiple times), and how long each query took (short is good - use cache for complex queries).Also a dprint_r($array) function is provided, which pretty prints arrays. Generate content Accelerate development of your site or module by quickly generating nodes, comments, terms, users, and more.
Devel Node Access (DNA) View the node access entries for the node(s) that are shown on a page. 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. By moving field group to a separate module, this may open some new perspectives.
Available group types FieldsetsHorizontal tabsVertical tabsAccordionsDivsMultipage steps: Note: This is only client side.HTML5 elementsHtml elements Notes This project will NOT include the multigroup feature as it existed for drupal6. Modules that depend on fieldgroup Contact me if you know a module that can get in this list! Related modules Extra screenshots and video's Video with Multipage feature in field_group Maintenance. 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.
By itself, this module doesn't do much; it requires another module to support it, but it does come with a nice little sample of text from Wikipedia to demonstrate the system. Accessing Advanced_help When this module is installed, users with the view advanced help index permission can access the advanced help index by going to Administer -> Advanced 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 Works in all themes and all browsers.Exposes all administration links including all tabs/tasks and actions to provide direct access to any page.Extensible with add-on features by other modules. Related modules Installation Documentation Credits Current maintainers: This project has been sponsored by: unleashed mind Drupal consulting and development. 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 #D7CX: The basic token API is now a part of Drupal 7! #D7AX - I pledge to make this module as accessible as it can be. 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 The 7.x-1.x and 6.x-2.x branches are currently accepting new feature requests and are kept in sync as much as possible. Known issues Multilingual URL alias support is still a little unstable and should be tested before used in production. Recommended modules Redirect (D7) / Path Redirect (D6) when installed Pathauto will provide a new "Update Action" in case your URLs change. Co-Maintainers Pathauto was originally written by mikeryan and maintained by Greg Knaddison (greggles) . Pledges #D8CX : I pledge that Pathauto will have a full Drupal 8 release on the day that Drupal 8 is released.
Downloads. 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 Drupal 7.2 or later; suggested Drupal >= 7.15 Documentation You can find documentation in the handbooks.
Overview For site-builders This is an API module, so it doesn't provide any end-user features. A Views display plugin and field to render or link to any entity (by view-mode)A CTools content plugin to render any entity (by view-mode)It ships with the Entity tokens module which makes sure there are tokens for most entity properties and fields, i.e. it provides token replacements for all entity properties (or fields) that have no tokens and are known to the entity module (read about the entity property info API below). For developers Changes Credits The project has been sponsored by Maintainer Wolfgang Ziegler (fago) 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. Other included modules Context UI provides an administrative interface for managing and editing Contexts. The inline editor for 7.x The inline editor has been redone for 7.x and is activated via a "Configure Layout" contextual link on blocks that appear on the page. Dependencies Required Chaos Tools 1.7 or higher Recommended for 6.x jQuery UI in order to use the Context inline editorAdmin 2.x in order to use the Context inline editor Upgrading from Context 2.x for Drupal 6.x Thanks.
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. For the moment, it includes the following tools: Plugins -- tools to make it easy for modules to let other modules implement plugins from .inc files. 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. Views can do a lot more than that, but those are some of the obvious uses of Views.
Views for Drupal 8 Views is in Drupal 8 Core! Recommended versions of Views! For new installs of Drupal 6, we recommend the 6.x-3.x branch. The 6.x-2.x branch of Views is in critical/security maintenance mode only. Dependencies The Drupal 7 version of Views requires the Chaos Tool Suite also known as CTools. Views' bug squad The Views' bug squad is a group of people who have dedicated a few hours a week to help provide support and fix bugs in the issue queue. Views documentation Sponsorship This project is sponsored by IO1.