Global Redirect. Workflow. The workflow module allows the creation and assignment of arbitrary workflows to Drupal node types. Workflows are made up of workflow states. For example, a workflow with the states Draft, Review, and Published could be assigned to the Story node type. Transitions between workflow states can have actions assigned to them. In our example, we could assign an action so that when the story moves from the Draft state to the Review state an email is sent out. Another action could be assigned to the transition from Review to Published so that the node's status is set to Published (and becomes visible on your website). If you are interested in the future of the workflow module, please join the workflow group on groups.drupal.org .
Watch the FOSDEM 2005 video where John VanDyk presents actions and workflows if you are unfamiliar with the concepts (video is at homepage.mac.com/drupal/*-drupalconf-workflow.ogg (replace the * in the filename with the word 'please') and requires something like VLC ). 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. 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 Views documentation Views 1 Views 2 (This link goes to the Advanced Help project page. Sponsorship Our book. Variable. 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.
Panels. An Overview of Panels The Panels module allows a site administrator to create customized layouts for multiple uses. At its core it is a drag and drop content manager that lets you visually design a layout and place content within that layout. Integration with other systems allows you to create nodes that use this, landing pages that use this, and even override system pages such as taxonomy and the node page so that you can customize the layout of your site with very fine grained permissions. Integration with CTools module Panels 3 utilizes the CTools' system of "context" so that the content you place on the page can be aware of what is being displayed. For example, in the existing Drupal setup, a block has no real knowledge of what the primary page is displaying. Panels uses Contexts - What are they? In a Panel, you can create contexts, which represent the objects being displayed. Panels also includes simpler applications of the drag and drop system.
Other Features of Panels Known Issues. 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) Easy Social. Easily add share buttons to your nodes! Centered in a single place, you don't need to worry in including external javascript libraries, and enabling several social modules. Despite a bunch of other social modules, this module fits exactly if you want simple share buttons without worrying about messy configurations. Easy Social is available both as blocks, attached to nodes, comments and also as a Views field. The following widgets are included by default: TwitterFacebookGoogle+LinkedIn Extend!
Modules can also implement hook_easy_social_widget() to define new widget types: Example For a full description of the API with working examples, check out the documentation. Drupal 7 Version Easy Social for Drupal 7 depends on the Variable module. Drupal 6 Version The Drupal 6 version is being supported exclusively for bugfixes but no new features will be included. Maintainers The maintainers provides consulting services and paid development, e.g. for implementing a specific feature. 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. Exportables -- tools to make it easier for modules to have objects that live in database or live in code, such as 'default views'. 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 (