From Things and Stuff Wiki
Jump to navigation Jump to search


needs major refactoring!!

  • Drupal dev docs - "Newcomers to Drupal development should read the conceptual information provided in the 'Components of Drupal' section, and then proceed to examine one of the heavily-documented example modules below. The examples are fully-functioning Drupal modules, so you can download them from the contributions repository and alter them as you experiment."



composer update 'drupal/*' --with-dependencies

php -d memory_limit=-1 composer require zaporylie/composer-drupal-optimizations

composer remove drupal/admin_toolbar_search


  • Drush - a command line shell and Unix scripting interface for Drupal. Drush core ships with lots of useful commands for interacting with code like modules/themes/profiles. Similarly, it runs update.php, executes sql queries and DB migrations, and misc utilities like run cron or clear cache. Drush can be extended by 3rd party commandfiles.
composer require drush/drush
composer require drush/drush:^10

  • https://github.com/drush-ops/drush-launcher - In order to avoid dependency issues, it is best to require Drush on a per-project basis via Composer (composer require drush/drush). This makes Drush available to your project by placing it at vendor/bin/drush.However, it is inconvenient to type vendor/bin/drush in order to execute Drush commands. By installing the drush launcher globally on your local machine, you can simply type drush on the command line, and the launcher will find and execute the project specific version of drush located in your project's vendor directory.


I have dr as an alias for drush.

drush updatedb --no-interaction --yes

drush watchdog:show

drush help
  alll the commands!
drush help --filter
  choose which help category to echo
drush cc all
  clear cache
drush pml
  list installed and enabled modules

drush dl [project]
  download project
drush dl sasson-7.x-3.x-dev
  download sasson dev release
drush updb
  run upgrade.php
drush en [project] -y
  enable project without confirmation
drush dis [project] -y
  disable project

drush pm-uninstall [project]
  remove project from db
drush sql-cli < example.sql
drush php-eval 'echo drush_get_context("DRUSH_DRUPAL_ROOT");'
drush php-eval 'echo drush_locate_root() . "/" . drupal_get_path('theme', 'sasson');'

drush eval 'echo theme_get_setting('sasson_compiler') . "\n" ;'
  otherwise gives trailing issue?
drush vset --yes site_offline_message "This site is being maintained";

drush vset --yes site_offline 1;

In Drupal 7 to simply put the site into maintenance mode:

drush vset --yes maintenance_mode 1;
drush user-login ryan
  displays a one-time login link for the user ryan. 
open `drush user-login ryan`
  open said link in browser
dr uli

Site aliases

Drush uses site alias files to store context data. (Aegir still uses Drush 4)

drush help site-alias

Copy to ~/.drush, rename aliases.drushrc.php or further.

drush ev 'print_r(array_keys(drush_sitealias_get_record("@server_master")))'
drush ev '$a = drush_sitealias_get_record("@gk.dev"); print_r($a["path-aliases"]);'


To sort with Aegir#Remote

drush help rsync
drush help sql-sync

Drupal Console



$config['system.logging']['error_level'] = 'verbose';
  # in sites/default/settings/php


  • https://drupal.org/project/devel_debug_log - a developer module that provides a way for developers to save and display debug messages on a separate page in the web browser. It serves as an alternative to using drupal_set_message() or watchdog() for debugging, and a complementary module to Devel for those who find viewing messages in the browser easier than looking for them, say, in a file.

  • https://www.drupal.org/project/devel_php - The Execute feature has been removed from the Devel module for Drupal 8 since version 2.0. This module re-adds back that feature as an external module. Hence the message "This project is not covered by Drupal’s security advisory policy".


  • https://www.drupal.org/project/admin_toolbar - The Admin Toolbar module intends to improve the default Toolbar (the administration menu at the top of your site) to transform it into a drop-down menu, providing a fast access to all administration pages.The module works on the top of the default toolbar core module and is therefore a light module and keeps all the toolbar functionalities (shortcut / media responsive).

  • https://www.drupal.org/project/module_filter - quickly find the module you are looking for without having to rely on the browsers search feature which more times than not shows you the module name in the 'Required by' or 'Depends on' sections of the various modules or even some other location on the page like a menu item.

  • https://www.drupal.org/project/total_control - Several overview panes are included for site stats and quick reference. Several administration panes are provided with quick links to content types, menus, taxonomy, and other scattered locations of important Drupal site administration. Several views panes are also provided as well as full-page comprehensive versions of the views with bulk operations. Each views panel pane is customizable via it's pane settings, or override the default views provided to suit your own needs.


  • http://drupal.org/project/features - The features module enables the capture and management of features in Drupal. A feature is a collection of Drupal entities which taken together satisfy a certain use-case. Features provides a UI and API for taking different site building components from modules with exportables and bundling them together in a single feature module. A feature module is like any other Drupal module except that it contains additional information in its info file so that configuration can be checked, updated, or reverted programmatically.

Users etc.

  • https://www.drupal.org/project/masquerade - allows site administrators (or anyone with enough permissions) to switch users and surf the site as that user (no password required). That person can switch back to their own user account at any time.


Editing of submitted unpublished nodes, updating coordinator contact info, etc.


  • http://drupal.org/project/rules - The Rules module allows site administrators to define conditionally executed actions based on occurring events (known as reactive or ECA rules).


  • https://www.drupal.org/project/maestro - This is not a just a clever saying. It's true. With Maestro, the method to automate your process starts with our visual workflow editor with which you drag, drop and connect your workflow steps together. The maestro workflow editor can be used by business users to map out their business process.

  • https://www.drupal.org/project/override_node_options - The Override Node Options module allows permissions to be set to each field within the Authoring information and Publishing options field sets on the node form. It also allows selected field sets to be set as collapsed and / or collapsible.
  • https://www.drupal.org/project/business_rules - The Business Rules module is inspired on Rules module and allow site administrators to define conditionally actions execution based on events. It's based on variables and completely build for Drupal 8.

  • https://www.drupal.org/project/custom_add_another - This is a very simple module that allows you to customise the text of the 'Add another item' button on multi-valued fields.If your field supports 'unlimited' values then you are offered the option of customising the 'Add another item' button text. This setting is stored per 'bundle', so you can have different button text if you use the same field in two places.







  • http://drupal.org/project/context - Context allows you to manage contextual conditions and reactions for different portions of your site. You can think of each context as representing a "section" of your site. For each context, you can choose the conditions that trigger this context to be active and choose different aspects of Drupal that should react to this active context.

Display Suite

  • http://drupal.org/project/ds - Display Suite allows you to take full control over how your content is displayed using a drag and drop interface. Arrange your nodes, views, comments, user data etc. the way you want without having to work your way through dozens of template files. A predefined list of layouts is available for even more drag and drop fun!


  • https://www.drupal.org/project/layout_options - This module provides a Layout plugin that allows configuration options to easily be added layouts using using Yaml files and LayoutOption plugins. In most cases, using no code just YAML files.

  • https://www.drupal.org/project/layout_builder_save_and_edit - adds Save and Edit Layout button in layout builder form page which will save Site Builders/Content Editors time by redirecting it to same page in which they can see there recently added changes and can add extra changes for there layout.

  • https://www.drupal.org/project/layout_builder_base - The layout_builder_base module provides you a plugin base to create complex Layouts. It can be used by developers as a base to save time and focus on your styling. This module also provides a submodule wich provides you different layouts that can be used to build pages.

  • https://www.drupal.org/project/layoutcomponents - This module has been based on "Layout Builder" and provides a complete package of components integrated with that system, functionality that is available on Drupal 8 and is already fully supported by Drupal 9.With this module we want to extend the user experience by creating an improved interface, much more customizable and with aspects that are essential for us, such as the live preview of the changes while editing the content.

  • http://drupal.org/project/panels_everywhere - Panels Everywhere is an advanced method to completely do away with Drupal's restrictive blocks system and instead use the much more freeing Panels Layout system to control how your pages look. Panels Everywhere modifies the page as it is being rendered to 'wrap' the content in a display and can even take over your page theme to do away with the need for a page.tpl.php.

  • https://www.drupal.org/project/page_manager - This is the Drupal 8 version of Page Manager, formerly part of the CTools module written by merlinofchaosIt supports the creation of new pages, and allows placing blocks within that page.Like Drupal 7's Page Manager, it provides a concept of "page variants", each with their own selection conditions.Additionally, it can be used to take over an existing page, like overriding /node/% to change what is displayed when viewing a node.It utilizes the core Conditions, Context, and Blocks APIs to accomplish this.


  • http://www.drupal.org/project/pathauto - The Pathauto module automatically generates URL/path aliases for various kinds of content (nodes, taxonomy terms, users) without requiring the user to manually specify the path alias. This allows you to have URL aliases like /category/my-node-title instead of /node/123. The aliases are based upon a "pattern" system that uses tokens which the administrator can change.
    • http://drupal.org/project/subpathauto - The Drupal Path module matches only full URLs when creating SEO-friendly aliases. This module extends that behavior by also matching known sub-paths and replacing them with their respective alias.

  • http://www.drupal.org/project/pathologic - an input filter which can correct paths in links and images in your Drupal content in situations which would otherwise cause them to “break;” for example, if the URL of the site changes, or the content was moved to a different server. Pathologic can also solve the problem of missing images and broken links in your site’s RSS feeds.

  • http://www.drupal.org/project/empty_page - The Empty Page module is a simple empty page solution. It provides an interface that assists in managing "empty" menu callbacks, mostly used for pages that only consist of blocks.

  • http://www.drupal.org/project/xmlsitemap - The XML sitemap module creates a sitemap that conforms to the sitemaps.org specification. This helps search engines to more intelligently crawl a website and keep their results up to date. The sitemap created by the module can be automatically submitted to Ask, Google, Bing (formerly Windows Live Search), and Yahoo! search engines. The module also comes with several submodules that can add sitemap links for content, menu items, taxonomy terms, and user profiles.


  • https://www.drupal.org/project/ot - provides an interface to override/change the title using the Node(node_id), Path/URL and View pages, providing a fast and full access to Administrator.


  • https://www.drupal.org/project/menu_position - Often times site builders want certain types of content to appear in a specific position in the navigational menu. The simplest solution, adding all of that content individually to the menu system, has performance and usability issues. (Imagine hundreds of menu items added to one spot in the menu.)This module allows for the creation of rules that will dynamically add the current page into the menu system at the requested spots.

  • https://www.drupal.org/project/ultimenu - the UltimatelyDeadSimple megamenu ever with dynamic region creation.An Ultimenu block is based on a menu.Ultimenu regions are based on the menu items.The result is a block contains regions containing blocks, as opposed to: a region contains blocks.



  • http://drupal.org/project/fancy_login - Fancy Login adds JavaScript based, lightbox-style login functionality to your site. When the user clicks on any link that links to /user/login, they screen dims and a login box is created in the center of the screen.

  • http://drupal.org/project/jeditable - The jEditable module provides integration between Drupal's CCK module and the excellent jQuery plugin, jEditable. It is implemented as a CCK formatter, which makes inline editing possible through regular node displays, Panels, Views, or anywhere else you can place a CCK field.


  • https://www.drupal.org/project/fontyourface - provides an administrative interface for browsing and applying web fonts (using CSS @font-face, supported in all popular browsers) from a variety of sources. Try it out on simplytest.me.


  • http://drupal.org/project/tipsy - Tipsy is a jQuery plugin for creating a Facebook-like tooltips effect to textareas, textfield, anchors or any other HTML element you specify.









  • Simplenews publishes and sends newsletters to lists of subscribers. Both anonymous and authenticated users can opt-in to different mailing lists. HTML email can be sent by adding Mime mail module.



  • https://www.drupal.org/project/entity_form_mode - This module lets you make use of form modes for default entities as nodes, taxonomy terms or comments. It hooks up form modes corresponding to entity form routes. The route to add or edit an entity is called "entity.taxonomy_term.add" or "entity.node.edit_form". All you have to do to display i.e. the edit form in its own form mode is to offer a form mode with the (machine) name "edit_form" (the last part of the route name). This is automatically selected by this module to display the form.

  • https://www.drupal.org/project/form_mode_manager - Provides an interface that allows the implementation and use of Form modes easily without specific development. This module provides different configurations/routes/UI/Additional access control to simplify and enhance the management and development of your different entity forms that allowing you to implement a complex content strategy in simple ways. Form mode manager provides a mechanism fully integrated with the event and routing system to support your custom content entities and flexibility to add some behaviors of entity forms.

  • https://www.drupal.org/project/form_mode_control - This module allows you: to define access to each form mode for the different roles, to define for each role, each bundle of each entity which form mode should be selected by default during the creation and edit of a content. Of course you should grant access before defining this. If a user has multiple roles, the weight of the roles is taken into account (heaviest one), to access any of the form modes—as long as you have the permission—by adding a simple parameter such as the following example: node/add/article?display=form_mode_machine_name.


See also WYSIWYG

Inplace / Inline

  • https://www.drupal.org/project/jeditable - The jEditable module provides integration between Drupal's CCK module and the excellent jQuery plugin, jEditable. It is implemented as a CCK formatter, which makes inline editing possible through regular node displays, Panels, Views, or anywhere else you can place a CCK field.



  • https://www.drupal.org/project/fillpdf - Most PDF modules generate PDFs from scratch; FillPDF is not one of those modules. Instead, it lets you fill in existing editable PDFs with data from your Drupal site. Editable PDFs are those forms that let you type into them.


  • http://drupal.org/project/delete_all - This module is used to delete all content and/or users from a site. This is mainly a developer tool, which can come in handy in several cases, listed below.


An entity can be a kind of content stack. An entity base table is tied to fields using bundles. Entity types include node, comment, taxonomy term, user profile, organic group, etc. Entity types can allow bundling or not (creating types of node vs. users, though see the Profile 2 module). Fields are used to store and display various data types, and can be reused across bundles and entities.

  • https://www.drupal.org/project/eck - The Entity Construction Kit (ECK) builds upon the entity system to create a flexible and extensible data modeling system both with a UI for site builders, and with useful abstractions (classes, plugins, etc) to help developers use entities with ease.ECK allows the creation and management of entity types with custom properties; adding bundles to entity types; and fields to bundles, with the help of the Field UI module.

  • http://drupal.org/project/auto_entitylabel - "Automatic Entity Label" is a small and efficient module that allows hiding of entity label fields. To prevent empty labels it can be configured to generate the label automatically by a given pattern.

  • https://www.drupal.org/project/entity_reference_revisions - Adds a Entity Reference field type with revision support.It's based on the core Entity Reference module but allows you to reference a specific entity revision. This is useful for modules like Paragraphs and Inline Entity Form.

  • https://www.drupal.org/project/entity_reference_layout - Entity Reference with Layout empowers content creators to design beautiful pages with structured content (aka Paragraphs). It borrows concepts from other paragraphs-inspired modules like Bricks, and provides authors with a way to visually manipulate referenced entities and create unique page layouts. Entity Reference with Layout leverages Drupal’s core Layout Discovery module.

  • https://www.drupal.org/project/external_entities - This module allow you to connect to datasets from external databases and use it in your Drupal 8 website. While content lives external, Drupal sees those remote entities as internal. This makes it possible to alter the field displays, add references, comments, pathaliases, share buttons, webshop products and more.


  • http://drupal.org/project/filefield_paths - The File (Field) Paths module extends the default functionality of Drupal's core File module, Image module and many other File upload modules, by adding the ability to use entity based tokens in destination paths and file names.

  • https://www.drupal.org/project/system_stream_wrapper - Provides stream wrappers to access module, theme, profile, and library files and directories. Note these stream wrappers are read-only as none of these files or directories should be write-able by your webserver.


  • https://www.drupal.org/project/bestreply - Best reply module allows node authors to mark a particular comment as the best reply. It aims to encourage quality comments and to give some recognition to people posting quality responses.


  • http://drupal.org/project/image_resize_filter - This filter makes it easy to resize images, especially when combined with a WYSIWYG editor such as tinyMCE, CKeditor etc. Users never have to worry about scaling image sizes again, just insert an image and set it's height and width properties in HTML (this is done automatically by WYSIWYG editors) and the image is resized on output to match the HTML.

  • http://drupal.org/project/insert - Insert is a utility that makes inserting images and links to files into the body field and other WYSIWYG editors or text areas much easier by adding a simple JavaScript-based button and optional controls to file and image fields. Images may be inserted using any image style preset. Insert may also be interfaced to by other modules for inserting custom content.

  • https://www.drupal.org/project/media_responsive_thumbnail - This module adds a new field formatter for Entity Reference fields which target Media entities. Essentially, it allows you to display a Media Entity Reference field just like you normally would an Image field with a Responsive Image formatter.
  • https://www.drupal.org/project/blazy - Provides integration with bLazy and or Intersection Observer API, or Native lazy loading to lazy load and multi-serve images to save bandwidth and server requests. The user will have faster load times and save data usage if they don't browse the whole page.

  • https://www.drupal.org/project/remote_stream_wrapper - Provides the ability to use external files with file fields without saving the files to your local files directory. Also provides a 'Remote URL' browser plugin for Media.By default the module adds support for any URL using http://, https://, or feed://. Also note these stream wrappers are read-only and cannot perform any writing operations.

  • https://www.drupal.org/project/media_entity_remote_image - This module provides a basic Remote Image media entity type which allows embedding of images from any remote URL. The entities are simply rendered as an <img> tag with the src attribute set the to the URL that is saved on the entity. The limitation to this approach is that you cannot leverage Drupal Core's image styles since the images are not copied to the site's local file system.

  • http://drupal.org/project/mediawiki_api - This module provides an input filter which allows the conversion of content marked up using MediaWiki syntax to html for display on your drupal site, by using the "parse" feature of the MediaWiki API.

  • https://www.drupal.org/project/representative_image - Allows you to define representative image or media fields for entities like nodes, taxonomy terms and the like. These can then be used in Open Graph meta tags (via tokens); as fields in views; or embedded as tokens. The media module is also supported. A default image can be defined for those entities without images.

  • https://www.drupal.org/project/background_image - If your site is designed around utilizing background images, then this module is for you! Whether you need a surgical implementation that only administrators/developers can implement or provide the ability to allow users to attach their own background images to entities, this module has you covered.

  • https://www.drupal.org/project/image_style_generate - Image Style Generate allows a site administrator to quickly create image styles in bulk, based on a defined set of rules and patterns. It provides examples of how migrations can employ the module's capabilities.

  • https://www.drupal.org/project/flexslider - Flex Slider module integrates the Flex Slider library with Drupal and several contributed modules which allows you to build responsive, resizable slideshows. Meaning the slideshows automatically adapt to the size of the browser window or device.

  • https://www.drupal.org/project/image_effects - The Image Effects module provides a suite of additional image effects that can be added to image styles. Image Effects tries to support both the GD toolkit from Drupal core and the ImageMagick toolkit.

  • https://www.drupal.org/project/textimage - adds text to image functionality using GD2 and FreeType, enabling users to create crisp images on the fly for use as theme objects, headings or limitless other possibilities.


  • http://drupal.org/project/audiofield - allows you to upload audio files and automatically displays them in a selected audio player. Currently it supports 6 players and it provides API for easy addition of new players.



Dates, times and events

  • http://drupal.org/project/calendar - will display any Views date field in calendar formats, including CCK date fields, node created or updated dates, etc. Switch between year, month, and day views. Back and next navigation is provided for all views. Lots of the Calendar functionality comes from the Date module, so any time you update the Calendar module you should be sure you also update to the latest version of the Date module at the same time.

  • https://www.drupal.org/project/smart_date_calendar_kit - Installs a preconfigured view to use Smart Date values in a Fullcalendar View. Extends on and requires Smart Date Starter Kit so review that module and its notes about the default configuration provided.This module is not intended to be a robust solution, but a starting point. It could be useful for evaluating the basic functionality of Smart Date and Fullcalendar View, or it could be the starting point for a more customized solution.


Chaos tool suite (ctools) 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'.
  • AJAX responder -- tools to make it easier for the server to handle AJAX requests and tell the client what to do with them.
  • Form tools -- tools to make it easier for forms to deal with AJAX.
  • Object caching -- tool to make it easier to edit an object across multiple page requests and cache the editing work.
  • Contexts -- the notion of wrapping objects in a unified wrapper and providing an API to create and accept these contexts as input.
  • Modal dialog -- tool to make it simple to put a form in a modal dialog.
  • Dependent -- a simple form widget to make form items appear and disappear based upon the selections in another item.
  • Content -- pluggable content types used as panes in Panels and other modules like Dashboard.
  • Form wizard -- an API to make multi-step forms much easier.
  • CSS tools -- tools to cache and sanitize CSS easily to make user-input CSS safe.
  • Ctools Plugin Stub is a Drush plugin that can help you generate code stub files for ctools plugins. I wrote this plugin after having consistently messed up names of hook implementations in plugins over a long period. Plugin Stub does not write actual code that *does* stuff for you, but it sets you up so that all you have to do to get started is to fill in the capitalized parts of the generated file and start writing code that *does* stuff.





  • http://drupal.org/project/semanticviews - This Views plugin makes unformatted styles, field row styles and other output more readily configurable without needing to override template files. Instead of overriding row style templates for views where you want to specify different HTML elements (tags) and class attributes, you can specify these inside the Views UI and avoid overriding templates for each view.

  • https://www.drupal.org/project/views_fieldsets - Creates fieldset (and details and div) in Views fields output, to group fields, by adding a new field: "Global: Fieldset" and a few preprocessors. Also introduces a new template: views-fieldsets-fieldset.tpl.php where you can customize your fieldset output.
  • https://www.drupal.org/project/views_ef_fieldset - This module provides options to render exposed filters and exposed sorts fields in fieldsets.This module uses the Display Extender plugin for Views and works for any kind of exposed form.It also works if you use your exposed form in a block.


  • http://drupal.org/project/views_slideshow - Views Slideshow can be used to create a slideshow of any content (not just images) that can appear in a View. Powered by jQuery, it is heavily customizable: you may choose slideshow settings for each View you create.

  • https://www.drupal.org/project/views_photo_grid - This module adds a responsive photo grid display style to Views. The photo grid style arranges photos such that the height in each row is consistent, and the photos always fill up all the available width.

  • https://www.drupal.org/project/views_filter_clear - The Views Filter Clear module allows 'Clear' links to be configured for individual exposed views filters. These links clear any submitted value from the view. They operate independently of one another. This is different from the Reset buttons available for exposed forms, which reset the entire form to its default

  • https://www.drupal.org/project/views_condition - This provides a condition based on if the page is a view page. For example, you can use it to specify that the page title block should only show on all view pages, or a specific block displays on a selection of different view pages.

  • https://www.drupal.org/project/slick_extras - Provides Slick carousel samples and extra utilities demonstrating various usages of Slick carousel. The provided samples are forward-compatible with next Slick versions.






  • http://drupal.org/project/double_field - Double Field is a small module written to provide extensions to Drupal's core Fields. By this module you can split your fields up into two separate parts.

  • https://www.drupal.org/project/clientside_validation - This module adds clientside validation (aka "Ajax form validation") for all forms and webforms using jquery.validate. The included jquery.validate.js file is patched because we needed to be able to hide empty messages.

  • http://drupal.org/project/field_group - Fieldgroup will, as the name implies, group fields together. All fieldable entities will have the possibility to add groups to wrap their fields together. Fieldgroup comes with default HTML wrappers like vertical tabs, horizontal tabs, accordions, fieldsets or div wrappers.

  • http://drupal.org/project/formatter_field - The formatter field module provides a mechanism for specifying a formatter and formatter settings to be used for displaying a field, on a per-entity basis. By default, Drupal provides formatters and settings per entity bundle, but in certain situations it is necessary to choose the formatter at the entity level.

  • https://www.drupal.org/project/linked_field - allows you to link fields in the field formatter settings. E.g. you have a content type teaser with an image and a link field and you want to link the image to the entered link.

  • http://drupal.org/project/field_slideshow - Provides a Slideshow formatter for Image fields, using JQuery Cycle plugin. Compared to Views slideshows, building the slideshow from multiple nodes, this module builds it from a single node, with a multi-valued Image/Media/Field Collection field.

  • http://drupal.org/project/fences - Fences is a an easy-to-use tool to specify an HTML element for each field. This element choice will propagate everywhere the field is used, such as teasers, RSS feeds and Views. You don't have to keep re-configuring the same HTML element over and over again every time you display the field.

  • https://www.drupal.org/project/bricks - a new way of building pages on top of Entity Reference, Display Modes, Layout API, tabledrag.js and Flat Tables. Everything is in Drupal core that makes Bricks ultra-lightweight and developer-friendly.

  • https://www.drupal.org/project/gridstack - GridStack provides integration with gridstack.js as a dynamic layout creator for both two-dimensional layouts (Masonry, Packery, Isotope, native browser Grid Layout), and linear or one-dimensional layouts (Bootstrap/ Foundation, etc.) with drag-and-drop. A few optional field formatters, and Views style plugin.

  • https://www.drupal.org/project/layout_builder_styles - This module allow site builders to select from a list of styles to apply to layout builder blocks and layout builder sections. A "style" is just a representation of one or more CSS classes that will be applied. Additionally, for blocks, a block template suggestion is added for the selected style.


  • https://www.drupal.org/project/paragraphs - Instead of putting all their content in one WYSIWYG body field including images and videos, end-users can now choose on-the-fly between pre-defined Paragraph Types independent from one another. Paragraph Types can be anything you want from a simple text block or image to a complex and configurable slideshow.

  • https://www.drupal.org/project/layout_paragraphs - Layout Paragraphs provides an intuitive drag-and-drop experience for building flexible layouts with paragraphs. The module was designed from the ground up with paragraphs in mind, and works seamlessly with existing paragraph reference fields.


  • http://drupal.org/project/webform - Webform is the module for making forms and surveys in Drupal. After a submission customizable e-mails can be sent to administrators and/or submitters. Results can be exported into Excel or other spreadsheet applications. Webform also provides some basic statistical review and has an extensive API for expanding its features.

  • http://drupal.org/project/formblock - Enables the presentation of user registration, site wide contact, or node creation forms in blocks. This is particularly useful for including forms on panels.

  • http://drupal.org/project/formtips - Form Tips module uses JavaScript to move form description/help text to tooltips. It helps to reduce form clutter by removing form descriptions from the page and only displaying them when needed.


  • https://www.drupal.org/project/feeds_tamper - Feeds Tamper provides a small plugin architecture for Feeds to modify data before it gets saved. Several plugins are available by default and are described in the examples section below. Additional plugins can be added in separate modules or through the issue queue.

  • https://www.drupal.org/project/feeds_ex - A set of extensible parsers for Feeds.Provided parsers, XPath XML & HTML, JSONPath JSON & JSON lines parser, JMESPath JSON & JSON lines parser, QueryPath XML & HTML

to sort

  • https://www.drupal.org/project/login_destination - The Login Destination module allows you to customize the destination that a user is redirected to after logging in, registering to the site (7.x), using a one-time login link or logging out (7.x). The destination can be an internal page or an external URL. It is possible to specify certain conditions like referring pages or user roles and make the destination depend upon them. You may use PHP snippets to provide custom conditions and destinations. It is also possible to keep users on the currently visited page after logging in or out.

  • http://drupal.org/project/linkit - Linkit provides an easy interface for internal and external linking with wysiwyg editors by using an autocomplete field. Linkit has by default support for nodes, users, taxonomy terms, files, comments and basic support for all types of entities that defines a canonical link template.

  • http://drupal.org/project/content_lock - Block concurrent editing: When a user is editing a node, any other user that attempts to edit the same node will be blocked from doing so, and notified that the content is already being edited.

  • https://www.drupal.org/project/faq - 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).

  • http://drupal.org/project/scheduler - Scheduler gives content editors the ability to schedule nodes to be published and unpublished at specified dates and times in the future.
  • http://drupal.org/project/diff - This module adds a tab for sufficiently permissioned users. The tab shows all revisions like standard Drupal but it also allows pretty viewing of all added/changed/deleted words between revisions.

  • https://drupal.org/project/markdown - Provides Markdown filter integration for Drupal input formats. The Markdown syntax is designed to co-exist with HTML, so you can set up input formats with both HTML and Markdown support. It is also meant to be as human-readable as possible when left as "source".

  • https://www.drupal.org/project/flippy - an ultra-simple module that generates previous/next pagers for content types. On the Node type administration screen, you can turn Flippy on or offfor each content type. It'll generate a unique pager for each content type, so you can page through Articles or page through Blog posts, but y


  • https://www.drupal.org/project/backup_migrate - Back up and restore your Drupal MySQL database, code, and files or migrate a site between environments. Backup and Migrate supports gzip, bzip and zip compression as well as automatic scheduled backups.

  • https://www.drupal.org/project/cms_content_sync - CMS Content Sync is a module that provides content synchronization features between Drupal sites using a Node.js based Sync Core. The service is built to support the synchronization of a huge amount of data, including content and media assets between many Drupal sites that can't be handled by Drupal itself.
  • https://www.drupal.org/project/deploy - The Deploy module is designed to allow users to easily stage and preview content for a Drupal site. Deploy automatically manages dependencies between entities (like node references). It is designed to have a rich API which can be easily extended to be used in a variety of content staging situations.


  • https://www.drupal.org/project/term_reference_tree - This module provides an expandable tree widget for the Taxonomy Term Reference field in Drupal 7. This widget is intended to serve as a replacement for Drupal's core Taxonomy Term Reference widget, which is a flat list of radio buttons or checkboxes and not necessarily fit for medium to large taxonomy trees.

  • https://www.drupal.org/project/taxonomy_manager - This module provides a powerful interface for managing taxonomies. A vocabulary gets displayed in a dynamic tree view, where parent terms can be expanded to list their nested child terms or can be collapsed.


  • http://drupal.org/project/userprotect - This module allows fine-grained access control of user administrators, by providing various editing protection for users. The protections can be specific to a user, or applied to all users in a role.


  • https://www.drupal.org/project/eu_cookie_compliance - This module addresses the General Data Protection Regulation (GDPR) that came into effect 25th May 2018, and the EU Directive on Privacy and Electronic Communications from 2012. It provides a GDPR cookie banner where you can gather consent from the user when the website stores cookies on their computer or otherwise handles their personal information.


  • http://drupal.org/project/spamicide - The purpose of Spamicide is to prevent spam submission to any form on your Drupal web site. Spamicide adds an input field to each form then hides it with css, when spam bots fill in the field the form is discarded. The field, and matching .css file, are named in such a way as to not let on that it is a spam defeating device, and can be set by admins to almost anything they like(machine readable please). If logging is set, the log will show if and when a particular form has been compromised, and the admin can change the form's field name (and corresponding .css file) to something else.

  • https://www.drupal.org/project/captcha_free - Try this module especially to eliminate those robot user registrations and having to go in and delete all the bogus users. All without having to use the annoying captcha.


  • http://drupal.org/project/captcha - A CAPTCHA is a challenge-response test most often placed within web forms to determine whether the user is human. The purpose of CAPTCHA is to block form submissions by spambots, which are automated scripts that post spam content everywhere they can. The CAPTCHA module provides this feature to virtually any user facing web form on a Drupal site.


  • https://www.drupal.org/project/remove_http_headers - The Remove HTTP headers module removes configured HTTP headers from the response. Also removes <meta name="Generator" content="Drupal 8 (https://www.drupal.org)"> from the <head> tag if the X-Generator HTTP header is configured to be removed. By default the X-Generator, X-Drupal-Dynamic-Cache and X-Drupal-Cache HTTP headers are configured to be removed.

  • https://www.drupal.org/project/autoban - Autoban allows to automatize IP ban using watchdog table by the module rules. Need enable Database logging module (core) and at least one IP Ban Providers submodule: Autoban Core Ban (integrated with core Ban module) and/or Autoban Advanced Ban (integrated with Advanced Ban module).


  • https://www.drupal.org/project/force_password_change - This module allows administrators to force users, by role, individual user, or newly created user, to change their password on their next page load or login, and/or expire their passwords after a period of time.


  • http://drupal.org/project/honeypot - Honeypot uses both the honeypot and timestamp methods of deterring spam bots from completing forms on your Drupal site (read more here). These methods are effective against many spam bots, and are not as intrusive as CAPTCHAs or other methods which punish the user.
  • https://www.drupal.org/project/httpbl - can prevent email address harvesters and comment spammers from visiting your site by using a centralized DNS blacklist. It requires a free Project Honey Pot membership. This module provides efficient blacklist lookups and blocks malicious visitors effectively.


  • http://drupal.org/project/flag - Flag is a flexible flagging system that is completely customizable by the administrator. Using this module, the site administrator can provide any number of flags for nodes, comments, users, and any other type of entity. Some possibilities include bookmarks, marking important, friends, or flag as offensive. With extensive views integration, you can create custom lists of popular content or keep tabs on important content.

  • http://drupal.org/project/message - The Message module is the core of the message stack. It enables logging and displaying system events in a number of different use cases. Events that are recorded over time are sometimes call activity streams. Exportable messages subtypes can be created for different use cases with custom fields and display (view) modes.
  • http://drupal.org/project/messaging


  • http://drupal.org/project/forward - Adds a "forward this page" link to each node. This module allows users to email a specific node or other entity on your site to a friend. You can customize the link text and icon and choose the view modes on which the link appears. You can also customize the email template to match the rest of your site. The module includes a report on which pages are forwarded the most and a log of all forwarding activity.


  • https://www.drupal.org/project/qwebirc - This module takes the qwebirc IRC client, which has created a very nice (AJAX) widget that gives your community members access to IRC channels via a window (iFramed widget) on one of your site's pages.



  • https://www.drupal.org/project/bootstrap_barrio - a Drupal 8/9 - Bootstrap 4 Base Theme. Drupal markup is completely overwrite as standard Bootstrap 4 markup using from roots twig templates referencing only to Bootstrap CSS, and little custom CSS. Barrio is Flex based for whatever is not covered by Bootstrap.
  • https://www.drupal.org/project/bootstrap_sass - This is a Barrio subtheme that simplifies integrating Bootstrap 4 SASS with Drupal.This subtheme overrides almost every CSS from Drupal and replaces where posible Bootstrap variables in order to generate from roots a new set of CSS files.

  • https://www.drupal.org/project/basic - boasts a clean HTML5 structure with extensible CSS classes for unlimited theming possibilities as well as a top-down load order for improved SEO. It is fully responsive out-of-the-box and provides an adaptive, elegant, SASS mixin library and grid system.Basic's goal is to provide themers the building blocks and best practices needed to get their designs up and running quickly and simply.


  • https://www.drupal.org/project/responsive_favicons - This module adds the favicons generated by http://realfavicongenerator.net/ to your site. The responsive name comes from the fact that many devices are catered for including iPhone, Android, iPad, other tablets and desktops. This module can prove to be really useful in Drupal multisite setups where you do not want to pollute the base of the docroot with loads of icons that pertain to only a single site. This module allows you to store per site variations of the icons, in each site's respective public files directory.


  • http://drupal.org/project/purge - The purge module facilitates cleaning external caching systems, reverse proxies and CDNs as content actually changes. This allows external caching layers to keep unchanged content cached infinitely, making content delivery more efficient, resilient and better guarded against traffic spikes.

  • http://drupal.org/project/fast_404 - This module combines a very common method of handling missing image/file 404 errors (discussed here and planned for Drupal 8) with a method created by dpardo (a co-maintainer of this project) to deliver super fast 404 error pages for both missing images and bad paths. Depending on which method of implementation you choose (aggressive or super aggressive) you can deliver 404 errors using less than 1MB of memory on your server.



  • http://drupal.org/project/metatag - The Metatag module allows you to automatically provide structured metadata, aka "meta tags", about a website. In the context of search engine optimization, when people refer to meta tags they are usually referring to the meta description tag and the meta keywords tag that may help improve the rankings and display of a site in search engine results. In addition, the module provides support for meta tags (Open Graph Protocol from Facebook, Twitter Cards from Twitter) that allow control of how content appears when shared on social networks.


Site provision

See Building, Aegir, Profiles

Two make files; mysite.build and mysite.make.

mysite.build is brief:

core = 7.x
api = 2
projects[drupal][type] = "core"
; Our distribution
projects[mysite][type] = "profile"
projects[mysite][download][type] = "git"
projects[mysite][download][url] = "git@gitserver.com:mysite.git"
projects[mysite][download][branch] = "develop"

mysite.make contains the list of modules, themes, and libraries to download and add to the site.


  • http://drupal.org/project/doabarrelroll - Habe you ever wondered how does Google do a barrel roll when you type in 'do a barrel roll' in the search bar? Have you ever wanted to have the same functionality in your web site? Look no further: this module will give all the barrel roll awesomeness you ever wanted.

  • http://drupal.org/project/konamicode - The Konami Code is a cheat code that appeared in many Konami video games. The Konami Code module makes it so that when users enter a given code on your website, it invokes a certain action.


See also Drupal Distros#E-commerce


  • Payment is a general payment platform which allows other modules to use any of the payment methods that plug into Payment. With Payment we only need one one Paypal, one credit card and one iDEAL module to use with every single webshop or payment form that you want (applies to any payment method that works with Payment). This shortens development time and improves support, because only one instead of three Paypal modules need to be maintained, and simplifies UX, because all payment (method) information is now located in one place.

Payment method controller modules;






  • http://drupal.org/project/module_builder - A module which auto-generates a skeleton or "scaffolding" for a module, along with hints on how to fill them in. Useful for newbie developers to learn how Drupal code works, and seasoned developers who are too lazy to look up what arguments a function has to take.

  • http://drupal.org/project/coder - Coder checks your Drupal code against coding standards and other best practices. It can also fix coding standard violations for you with the phpcbf command from PHP_CodeSniffer, see the installation instructions and usage examples. Those checks apply to all versions of Drupal, so you can use Coder 8.x-3.x to check Drupal 7 code.
  • https://www.drupal.org/project/libraries - The common denominator for all Drupal modules/profiles/themes that integrate with external libraries.This module introduces a common repository for libraries in sites/all/libraries resp. sites/<domain>/libraries for contributed modules.


patch -p1 < path/file.patch


git apply path/file.patch


"Drupal's module system is based on the concept of "hooks". A hook is a PHP function that is named foo_bar(), where "foo" is the name of the module (whose filename is thus foo.module) and "bar" is the name of the hook. Each hook has a defined set of parameters and a specified result type.

"To extend Drupal, a module need simply implement a hook. When Drupal wishes to allow intervention from modules, it determines which modules implement a hook and calls that hook in all enabled modules that implement it."

Menu system (path)


  • https://www.drupal.org/project/relaxed - This module provides a generic RESTful API for all content entities. It extends the core REST API with better support for translations, revisions, file attachments, UUID references etc.