Implements the warning message proposed by

This module adds ability to create role-specific registration pages.

Drupal 8

Users may select a specific revision, and it will be changed to a different moderation state at a specified date.

Timefield is a Field API field for storing simple non-timezone time values, with an optional end time, utilizing a simple JQuery timepicker widget for input. Normally, you will want to use a Date field for all date/time values; however, this field is for use when you don't want to implement a Date field or have time values that are not dependent on the Gregorian Calendar, i.e., when Year,
Month granularity is irrelevant.

If you have repeating events that occur regularly on a weekly basis and wish to provide a simple way to display and store this logic, this field may provide the functionality you seek.

There are 3 storage options:
1. Single Time Value
2. Start Time - End Time
3. Start Time (optional End Time), Weekday Repeat

There are a few display options as well:
1. List Display
2. Duration Display (for times with End Time)
3. Table Display (for weekly repeat options)

Currently, this module supports rudimentary views integration.

** DIFFERENCES FROM DATE MODULE **

This module provides "like" and "dislike" widgets for contents inside Drupal, making it easiers to promote features as the one seem on many social network websites.

Description

This plugin adds numbered list and ordered list properties dialogs (available in context menu).

They allow setting:

CKEditor Widgets Bootstrap Grid

Description

This is just another small module introducing the Bootstrap Grid to CKEditor.

The Search API spatial module (7.x-2.x branch) adds the possibility of location based searching to the Search API module.
D7: Currently only Apache Solr is supported as the service class.
D8: Search API Solr works and is fully tested. Elasticsearch connector should work, but problems may arise as this was not fully tested.

Requirements

• a content type/entity with a latitude/longitude field (currently geofield is supported, location fields probably work, but I haven't tested it yet)
• Apache Solr server 3.1+ (I only tested with 3.3 and 3.4, but spatial search is included since 3.1)
• Current versions of Search API and Search API Solr

Installation and configuration

• Put the module in sites/all/modules folder.
• enable the module and any sub-module(s) you want
• add/modify a Search API index which lies on a Solr server
  • on the index's "Fields" tab: index the field containing the latlng value ("LatLong Pair") and select the "Latitude/longitude" type.
    If you don't see the field, check the "Add related field" form at the bottom of the page (see screenshot 1 and screenshot 2)

Node read time is a module that provides an extra field for content types, which displays to the users the time it will take for them to read a node.

This module helps with developing configuration. Do not deploy in production environments. Exercise caution and always use version control.

It does three things:

Overview

A collection of field formatters which add classes to various elements (as opposed to the wrapper markup).

Extra Layouts for the Panels Module

Save Draft adds a 'Save as Draft' Button to the node_form for content types, allowing the user to click the 'Save as Draft' button to save the node as a draft.

Drupal 8 has this UX feature in the core!!

This helps improve usability, as the content creator no longer has to search for the published checkbox to publish or unpublish a node, as they can just click the 'Save as Draft' Button.

HTML Purifier is a standards-compliant HTML filter library.

The Colorbox Load module is an implementation of the core D7 colorbox feature of the same name, allowing you to load content into a colorbox via AJAX.

This module helps to export and/or import menus. Using it you can easily transfer menus from one Drupal site to another. The module can be used in ensemble with Node export (node content migration). In this case, it allows to batch-arrange existing content into a given menu structure, using a very simple text file.

Here is an example of the JSON-like file format understandable by the module:

Pages {"url":"pages/all"}
- Site {"url":"http://external-site.com/","description":"Visit our site."}
- Story {"url":"node/3","description":"A very interesting story!"}
-- Some node {"url":"node/4","lang":"da","description":"Links is in Danish language"}
Archive
- Admin zone {"url":"admin/appearance","description":"Internal link with description."}
A page {"description":"Description only, no link.","hidden":true,"expanded":true}

Important: please use Unicode (UTF-8) as file encoding, one-byte national charsets will not work. Also, JSON's name and value must be enclosed in double quotes, single quotes are not valid. Trailing commas are not allowed.

D6 users:
The export feature is now implemented! You can export menus and import them in D7 installations (and D8 when relevant version will be ready)

Patch #75 is available for Drupal 9.1.x and it works!

The nodeorder module gives users an easy way to order nodes within their taxonomy terms.

By default, the taxonomy module orders listings of nodes by stickiness and then by node creation date -- most recently posted nodes come first.

The nodeorder module gives the user the ability to manually put nodes in any order they wish within each category that the node lives.

There are two ways that a user can order nodes within a category. The first is to use the "move up" and "move down" links that can be configured to appear on each node (especially useful when looking at lists of taxonomy terms). The second is to use drag and drop, which appears on the administrative listings of nodes in a category.

For a comparison of nodeorder with other node ordering modules have a look at this handbook page: http://drupal.org/node/398508.

BPMN.iO is a BPMN modeller for ECA and is fully integrated into Drupal's admin UI.

Weaves together the chaos magic. Very cool stuff.

Migrate Extras extends Migrate to provide support for several contributed modules.

The best place to implement migration support for a contributed module is in that module, not in the Migrate or Migrate Extras modules. That way, the migration support is always self-consistent with the current module implementation - it's not practical for the migrate modules to keep up with changes to all other contrib modules. We are no longer adding support for other modules to Migrate Extras.

Status

Migrate Extras 2.5 is now available. This is planned to be the final Migrate Extras release - the only work to be done with Migrate Extras going forward will be to port the contrib module support here directly to the respective supported modules.

Block Classes allows users to add classes to block title, content, and wrapper of any block through the block's configuration interface. This module extends the Block Class module features.

The Entity Pager allows you to create new Navigation blocks in a few seconds. It provides next and previous navigation on any Entity (e.g. Nodes, Users etc..).