The simplify_menu module uses a TwigExtension to gain access to Drupal's main menu's (or any other menu for that matter), render array so it can be accessed from a twig template.

Drupal 8 is here!!

Drupal 8 version includes local libraries as well as external CDN libraries.
Drupal 8 version of the module does not depend on libraries module.

Nodeaccess is a Drupal access control module which provides view, edit and delete access to nodes.

Enable bookmaking of AJAX views. Supports filters and paging.

In the 8.x version of the module, the AJAX History feature has to be enabled individually for each view that uses AJAX.

Session Limit allows administrators to limit the number of simultaneous sessions per user.

Menu Token module provides tokens, that could be used in title or in path of menu items (links). For example, if you create a menu item with path: "user/[current-user:uid]", the url will be changed "on fly" to: "user/1" (assuming you are user 1).

Tokens are provided by Token module. Menu Token allows to use both global tokens and entity ones: node, user, term, etc. Entity tokens have several methods of substitution: from context, random and user defined.

Menu Token Resources

Menu Token functionality can be extended gracefully. Following some examples:

• Menu Token module implements Ctools plugin system and allows to plug in new token handlers.
• Use Menu HTML module and select "Allow html" in your menu item.
• Superfish integrates jQuery Superfish plugin with your Drupal menus. Use Superfish 1.9-beta5 or greater.
• Use Extended path aliases to automatically translate paths like 'user/1/mycontent' to 'users/admin/mycontent'. Just need to create a 'root' path alias: 'users/admin'. See #1320842: Work with the Path Auto module.
• Menu item visibility exposes configurable and extendable visibility settings for menu links. You'll need to set module weights so that Devel node access > Menu item visibility > Menu Token.
• You can use Tokenize Request Parameters module along with the Menu Token to configure this sort of functionality without the need to code a new module. Tokenize Request Parameter allows you to define what URL parameters to convert into tokens. It makes the tokens available to any token module that consumes tokens (Token Filter, Menu Token, Rules, etc.)

Overview

Media file delete gives content editors the option to delete the associated file when deleting a media entity.

Provides integration between Slick and Paragraphs.

UUID Features 7.x-1.0-alpha3 fixes some HTML code that made the module completely unusable. Please update ASAP. If you're experiencing WSOD simply remove the module files completely then upload the latest version. The latest version now works with UUID 7.x-1.0-alpha3. Please report any bug you encounter in the issue queue.

Comparison with other modules with similar functionalities: #1311428: Comparison with Node export (and possibly other modules with similar functionalities)?

We need patches and reviews! Please contribute here!

Co-maintainer(s) wanted! Please contact us.

The UUID Features Integration module provides a mechanism for exporting content (nodes, taxonomy, fields) into a features module. What's that you say? You thought features was only for configuration? This module is meant to be used in the cases where certain pieces of content straddle the line between pure content and configuration.

Examples:

• There are relatively static pages (like an About Us page) that have links from your primary navigation. If these were to go missing, your client would certainly say the site is broken.
• You maintain page nodes for items like Terms of Service or Privacy Policy. These nodes appear on several sites and should always be the same.

This is the Drupal 8 module to bulk upload files and create the media

This module provides options to have views contextual filter for "Content:Has taxonomy term NAME with Depth".

Drupal core provides functionality to add multiple fields into node form by using "Add another item", but Drupal does not facilitate removing these fields after you have added them.

Send emails via SMTP using the latest PHPMailer library.

This module allows you to specify content type(s) 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 node in order to edit it.

We advice you to use this module together with Node Level Blocks or Block Reference module.

It is very handy to create a simple block content type and enable this content type for blocks and use these in place of the normal 'add block' functionality.

Now supports translatable content (Contrent translation with i18n and Entity Translation)

If Content Translation is enabled, then only a single node block per translation set is exposed and the node from the translation set with the appropriate language is loaded into the block.

Other modules

There are several other modules and approaches that allow nodes to be presented as a block. See a comparison at http://groups.drupal.org/node/93499

Drupal 7

The Drupal 7 version of this module enables the use of view modes. This gives the user even greater control over customizing the output of the node block. Default view modes and links display can now be assigned per content type and then overridden at block/node level.

Drupal 6

Make the end date in a Date range field (DateRangeItem) optional.

This module provides an Entity Browser for Media, inspired by File Entity Browser.

Provides a manual alternative to Composer for Drupal 8+ users.

This project integrates Drupal Commerce with various PayPal payment solutions. The primary integration method for both versions of the module (Drupal 9+ vs.

Drupal 8 includes jQuery UI in core, however it is no longer actively maintained and has been marked deprecated.

Paragraphs Editor Enhancements is intended to facilitate the editorial workflow and to simplify the work of the editors using Paragraphs.

Features Extra provides faux exportables (via Features) of several site-building components.

Taxonomy

Drupal 6: Supports exporting taxonomy vocabularies. To export a vocabulary, install FE taxonomy, go to vocabulary edit page, assign it a "machine name," then export it with Features as usual. As a bonus, this allows you to edit the "module" property of a vocabulary. Views support (by machine name) is also provided.

Drupal 7: Exporting vocabularies is supported natively by Features in Drupal 7 so it has been removed from this module. If you need to export taxonomy terms in addition to the vocabularies, you can do this with the UUID Features Integration module.

Nodequeue

Only nodequeue definitions are supported. To export a queue, install FE Nodequeue, edit your nodequeue, assign it a "machine name," then export it with Features.

Block

To export a block, install FE Block, edit your block, give it a "machine name," export it with Features. You can export block settings (region settings, visibility settings, ...) of any block, and the content of blocks created with the Block module from Drupal core.

Paragraphs Features

This module provides few additional features for paragraphs module.

ThemeKey allows you to define simple or sophisticated theme-switching rules which allow automatic selection of a theme depending on current path, taxonomy terms, language, node-type, and many, many other properties. It can also be easily extended to support additional properties exposed by other modules. In combination with Drupal's theme inheritance you can easily achieve features like:

• individually-styled channels
• a front-page / "splash" screen
• a date/time-selected Christmas theme
• mobile themes for different auto-detected mobile devices
• special themes for "limited" or "old" browsers
• content, user, or role -specific themes
• indicating your environment (production, staging, testing, sandbox, … )
• testing your redesign safely on a live server
• ...

And unlike other theme switching modules, ThemeKey should play well with internal and external page caches, like Boost or Varnish, even for anonymous users.

Feedback is welcome!

Damn, ThemeKey ... ROCKS! Really appreciate the kick ass work you did on this :) mortendk

The Frequently Asked Questions (faq) module allows users, with appropriate permissions, to create question and answer pairs which they want displayed on the 'faq' page. The 'faq' page is automatically generated from the FAQ nodes configured. Basic Views layouts are also provided and can be customised via the Views UI (rather than via the module settings page).