Token. Tokens are small bits of text that can be placed into larger documents via simple placeholders, like %site-name or [user].
The Token module provides a central API for modules to use these tokens, and expose their own token values. Note that Token module doesn't provide any visible functions to the user on its own, it just provides token handling services for other modules. For Drupal 6, the Token module provides a "Token Actions" module which can be enabled separately. This provides several "actions" for the Drupal core Actions/Trigger modules to use that take advantage of the Token replacement functionality. Modules that use the Token module and provide tokens via the API include Organic Groups, Pathauto, Comment Notify, and Commerce.
Pledges #D7CX: The basic token API is now a part of Drupal 7! Configuration installer. Tour Builder. Tour UI. Token. Entity Browser. Entity Embed. Entity Embed allows any entity to be embedded within a text area using a WYSIWYG editor.
Requirements 8.x-1.x 7.x-1.x. Mix Modules Up. Multiversion. Administration menu. Provides a theme-independent administration interface (aka. navigation, back-end).
It's a helper for novice users coming from other CMS, a time-saver for site administrators, and useful for developers and site builders. Administrative links are displayed in a CSS/JS-based menu at the top on all pages of your site. It not only contains regular menu items — tasks and actions are also included, enabling fast access to any administrative resource your Drupal site provides. Showcase and Quality Assurance. Module Filter. Admin Toolbar. What is Admin Toolbar module ?
Admin Toolbar intends to improve the default Drupal Toolbar (the administration menu at the top of your site) to transform it into a drop-down menu, providing a fast a full access of all the administration links. The module works on the top of the default toolbar core module and is therefore a very light module and keeps all the toolbar functionalities (shortcut / media responsive). How to use Admin Toolbar module ?
Just install like any other module. What more ? The module provide also a submodule called "Admin Toolbar Tools" providing extra links like what does Admin Menu in Drupal 7 to flush caches, run cron, etc. Please provide your feedback and ideas ! Page Manager. Layout plugin. Allows modules or themes to register layouts by simply providing a YAML file and some templates, and for other modules to list the available layouts and render them.
This is an API module to hold the Drupal 8 plugin manager for layouts. On it's own, it doesn't do anything - you'll need to install a module which (1) uses layout plugins to render something, (2) provides some layouts or (3) both. 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. The field group project is a follow-up on the field group module in CCK. The release will only exist for Drupal 7 release and higher, so since the existence of the Fields API in core. By moving field group to a separate module, this may open some new perspectives. Available group types FieldsetsHorizontal tabsVertical tabsAccordionsDivsMultipage steps: Note: This is only client side.HTML5 elementsHtml elements Notes This project will NOT include the multigroup feature as it existed for drupal6.
Media entity. Media entity provides a 'base' entity for a media element.
This is a very basic entity which can reference to all kinds of media-objects (local files, YouTube images, tweets, CDN-files, ...). Configuration Synchronizer. Configuration Synchronizer provides methods for safely importing site configuration from updated modules and themes.
By taking a snapshot of configuration as installed and comparing the snapshot to the current active configuration, Configuration Synchronizer, determines configuration that has not changed since being installed and therefore can safely be updated without overwriting customizations. Using Configuration Synchronizer This module does not yet have either a user interface (#2429951: Add UI for managing configuration updates) or a Drush support (#2445463: Add Drush support to Configuration Synchronizer). See #2445491: Document Configuration Synchronizer usage for some pointers on how to use the module's methods.
Background and use case The Drupal 8 model that sites, not modules, own their configuration creates significant issues for distributions; see the blog post Drupal 8 configuration management: what about small sites and distributions? Deploy - Content Staging. Skip to main content Skip to search Drupal Search form Download & Extend.
Configuration Interchange and Management. Configuration log. Configuration inspector for Drupal 8. Configuration Tools. Configuration development. This module helps with developing configuration.
Do not deploy in production environments. Exercise caution and always use version control. It does three things: Automated import of configuration files into the active storage. At the beginning of every request the changed files are saved the way as if it were dumped in the core config module provided "Single import" form.Automated export of configuration objects into files. Typically filenames wil be something like modulename/config/install/foo.bar.yml. Note: system.site, core.extension and simpletest.settings is not compatible with the auto import feature.
Configuration Update Manager. The Configuration Update Manager module supplements the core Configuration Manager module, by providing a report that allows you to see the differences between the configuration items provided by the current versions of your installed modules, themes, and install profile, and the configuration on your site. The report is available from the administration UI, or via Drush commands. If you run the report from the administration UI, you can also import new configuration provided by updates, and revert your site configuration to the provided values, on a case-by-case basis.
The main use case is: You update a module, and it has either changed default config that it provides, or added new config items.