The Revisionator module clean up insightly old revisions! Revisionator removes
revisions older than the specified age, leaving a minimum number of revisions
per node.
If you read the Similar Projects section in the Node Revision Delete module you will see that at this moment there are 5 modules that works with Revisions:
A module that provides a tree-view Chart. It can use different content types for its items that can be selected through the admin interface.
The Repo Pages module is a solution to avoid putting Basic Pages (i.e. "About Us" or "Privacy Policy" types of pages) in the database - but rather store them in the file-system, where they can be tracked under a version-control system.
This concept works by you choosing a directory within the Drupal application, say sites/all/pages/, and declaring that all *.page.php files shall be perceived as a page to be used on the site.
For example:
The module provides month name handling.
It contains:
CTools relationship plugin which converts month number (12) into month name (December) with translation and grammar case selection.
This simple module allows anonymous users or users without permissions to submit basic node content to your site before login in/registering. (Currently, by "basic node contect" we mean title and body only.)
When the user finally register/log in and got to the node creation page, then the node form will be pre-filled with previously input data.
Tools for managing spam that gets past other filters.
In other words “Perform bulk operation to delete spam
content/comments/usersâ€.
Google Scholar Abstract implements a node content type named “HTML abstractâ€. This content type is designed to capture all metadata about a research paper that is required by Google Scholar according to its Inclusion Guidelines for Webmasters.
Google Scholar expects metadata to link to a full length PDF of the paper. This module lets the user upload the full length PDF to be linked.
This module is a successor of the nodeblock module for Drupal 8.
This module allows you to specify content type(s), users, or any other type of entity as being a block. This allows the content managers of the site to edit the block text and title without having to access the block administration page. Users only need edit access to that entity in order to edit it.
This module will help you get your content types out of features, and back into the database in a state where you can edit or delete them freely.
How to use:
1) Disable the feature (module) that owns your content type
2) Enable this module
(make sure you have permission to administer content types)
3) Visit admin/config/development/unfeaturize
4) check the boxes for the content types you'd like back
5) click the "Unfeaturize" button.
6) Profit.
This modules provides possibility to move site configuration from files to database with just a couple clicks!
How often did you expirience a situation when module or distribution provides default views, rules, entities and other configurations out of the box which you had to change and then deploy it with Features? We know it was a hard time full of your tears and screams like "Drupal, why?"
