Site administrators

Taxonomy Access Control

Workbench Menus is a collection of menus that utilizes the taxonomy access control provided by Workbench Access. Each workbench menu is broken down into a collection of links (or placeholders) called menu items.

Url Path Based Menus

For every term in the vocabulary associated with Workbench Access, Workbench Menus provides a menu for that term at a specific URL path. The workbench menu associated with a vocabulary term will be presented only on that URL path and sub-paths.

Menu Items are Active at Specific paths

Each menu item can be represented by a given URL path in which is considered active. This allows for highlighting and displaying specific menu items as currently selected, or active, when the appropriate URL path is being viewed.

Multiple Types of Menu Items

Each menu item can be broken down into different categories, or types, that define how that menu item interacts with and presents itself to the viewer. These different types are: Node, Link, Label, File, Menu Item, and Menu.

Breadcrumbs Reflect Menu Path, not Url Path

Unlike normal breadcrumbs, which often reflect the URL path tree of the currently viewed page, workbench menus changes the breadcrumbs to reflect the tree structure defined by a given workbench menu at a given URL path.

Tweakable Menu Structure

DevShop is a collection of different modules.

• DevShop Projects
  Project nodes allow you to add a Git URL to your site and create unlimited environments for that site. Create dev, test, live, and "branch platforms" from branches in your git repository. A web-based UI allows users to Pull Code, Sync Data, Commit Features, and Run Tests.
• DevShop Pull - This module connects to your git repository to automatically pull environments' code when a commit is detected.
• DevShop Logs - This module provides git logs and error logs to the DevShop front-end. This makes keeping track of the state of your git powered platforms much easier.
• DevShop Tests - This module allows users to run a Run Tests task from within your browser. DevShop stores the tests you wish to run per project, and allows you to adjust those on every test run.
• DevShop Live - Store (and change) a project's Live Domain.

Place holder for documentation of the process for upgrading from OG1 -> OG2.

The step described in this page is not at all necessary. If you want to customise the products list presented on page admin/commerce/products , first go to modules: Views, and enable the "Views UI" module.
Then go to store → products , click on the gear at the right top corner of the page, then on "Edit View", because the product list page is produced by the Views module.

Follow the instructions on that page, section called "Customizing On-site Product Administration".

Transliteration provides a central transliteration (romanization) service to other Drupal modules, and cleans file names during upload by replacing unwanted characters.

Generally spoken, it takes Unicode text and tries to represent it in US-ASCII characters (universally displayable, unaccented characters) by attempting to transliterate the pronunciation expressed by the text in some other writing system to Roman letters.

According to Unidecode, from which most of the transliteration data has been derived, "Russian and Greek seem to work passably. But it works quite bad on Japanese and Thai."

In Drupal 8 core

Transliteration is part of Drupal 8 core. See #567832: Transliteration in core.

Install

Install the module in the usual way

If you are installing to an existing Drupal site, you might want to fix existing file names after installation, which will update all file names containing non-ASCII characters. However, if you have manually entered links to those files in any contents, these links will break since the original files are renamed. Therefore it is a good idea to test the conversion first on a copy of your web site. You'll find the retroactive conversion at Configuration and modules >> Media >> File system >> Transliteration.

Configure

This release is a complete rewrite and it started as its own project at Environmental Indicator. After a while it became a new release of Environment Indicator.

Key differences with the 7.x-1.x release:

• You can configure all your indicators from one place.
• You can position your indicator to not to interfere with your design.
• You can control permissions per environment. This way you can show the indicator for anonymous users in all the environments except for production.
• You can export your configurations to code and include them in GIT.
• It can be used on dynamically generated environments.
• Your site builders won't need to access your settings.php.
• It's integrated with the features module.
• It's integrated with the Toolbar module.
• Integration with Admin menu module.

Usage