Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
Inline module allows users to display uploaded files and images inline, i.e. place links to files into a content using a simple [inline:filename.jpg] tag. The effect is a link to the file or the display of an image, depending on the file type.
Inline allows users to place an uploaded image or a file attachment anywhere in the content. During creation of a content, a user can simply enter the number or filename of the attachment that should be displayed inline. After submitting the content, the number is automatically converted to the corresponding filename.
The Node Revision Delete module lets you to track and prune old revisions of content types.
Define the max amount of revisions to keep per content type.
Run on Drush, cron run or on a different period (daily, weekly, etc).
Note content containing field_collections seems to be affected by this bug which deletes unexpected content. Follow this issue in field_collection module for further details https://drupal.org/node/2000690.
FeedAPI aggregates feeds on a Drupal website by generating light weight items or nodes from feeds. It provides a straightforward configuration for most use cases and is extensible through an API. FeedAPI integrates with OG (but does not require it).
The Computed Field module only updates its computed values on saves or on load (if no computed value is computed yet). This is not optimal when using computed values in lists etc., or if you should wish to change the logic in the computed field.
If you wish to avoid re-saving all the entities/nodes using the computing field, you can use this tool to re-compute all the values again.
The computed field tools module offers a way to re-compute the computed fields of existing entities/nodes. It does so through the Batch API.
When the batch is running it does not save the entire entity/node, but it only saves the computed field. This make it a fast way of updating the content.
Fast processing of all computed fields.
Select specific computed_field to process.
Select content types to process for selected computed field.
It processes ALL entities/nodes. Also the ones with no value computed yet.
Since we don't do an entity_save() we don't clear the cache on every(!) node processing and no search index updates are triggered, so there is a huge performance advantage here on high traffic sites over the VBO way.
The Node Clone module allows you to easily create a duplicate copy (clone) of an existing node, however if that node references a field collection, the new clone will reference the same field collection, rather than have its own distinct copy. This module generates a cloned field collection so that each node has its own collection.
Simplenews Scheduler sends a newsletter as a re-occurring item based on a schedule.
It does so by creating a new edition (rendered copy as HTML Format) of a node at the time that it required to be sent again. The editions have an extra tab (for those with permissions) for viewing all editions as well as the original newsletter they are generated from. The original newsletter is never sent but all editions are according to a pre-defined schedule which is triggered via cron and can be defined when you create or edit a simplenews node. Current options for sending are by day, week, and month.
Works great with Insert View to place the content of a view into a newsletter. (eg: [view:recent_articles=20])
An early Drupal 8 port is available. The Drupal 7 release is considered stable. It is recommended to use simplenews 6.x-2.x branch along with the 6.x-2.x release of this project for sending scheduled newsletters.
This module is currently being ported to Drupal 8, but is not usable yet. Help us by following this issue.
Provides a way for administrators to define email transitions and configurable email subject / messages between those transitions. Email transitions can be defined as when content moves from state to state. Based on those email transitions, configurable emails can be created / updated / deleted as the site admin see's fit.
Example: When a content creator moves a piece of content from draft to needs review, they will be presented with a list of users that they can email the content update to. Selecting user(s) will send emails with the subject / message defined in the workbench email configuration page.
Workbench is a suite of modules which provide easier content management for content administrators. Each of the "Workbench" modules has been tested to work with the main Workbench module, and with the other modules in the Workbench suite. The Workbench suite is modular, allowing site builders to build the workflow that best suits the content administrators on their site. The Workbench suite provides authors, editors, and publishers with a unified interface for managing content relevant to them. It allows people to focus on content, rather than on learning Drupal.
This module has a pre-release version for Drupal 8. To find out more, follow this issue or download below.
Provides various content administration enhancements and other elements required for Open Enterprise content apps. It's purpose is to bring handy Open Enterprise UI improvements into any Drupal 7 site and to enable Open Enterprise content apps to be used on any Drupal 7 site.
The main feature of this module is to provided some simple yet effective improvements to content admin workflows. The module adds a default admin view that is filtered by content types. This view can be overridden to show content type specific data, e.g. the date of an event. The module also adds two contextual links "+ Add [content type]" and "+ Administer [content type]" to any standard view that is filtered by content type.
There are a few ways you can quickly add this to a site:
Traditional manual install by downloading the Enterprise Base module and dependencies from Drupal.org
#D8CX: I pledge that Advanced Text Formatter will have a full Drupal 8 release on the day that Drupal 8 is released.
This module is just a formatter (display) of textfield, text area and text format. The idea behind this is to provide a simple solution, easy to setup, with few dependencies to display text on website.
The trim function in this module is taken from Views module with a few modifications.
Of course, this module is fully compatible with any modules that use entity formatters, such as Views or Panels
This is a tiny module that basically extends Drupal's comment statistics module by adding comment counts for day, week, month and year. It also integrates with Views and you can use it to select, filter, order the content as well.
This module plays well and has been tested with Views. You can use these fields
in Content group
Comments this week
Comments this month
Comments this year
You can also use those fields to order and filter content.
Download the module and simply copy it into your contributed modules folder:
[for example, your_drupal_path/sites/all/modules] and enable it from the modules administration/management page.
More information at: Installing contributed modules (Drupal 7)
After successful installation, you need to activate the counter by going to
settings page admin/config/system/comment and check on "Count comments".