Administration

Status Watchdog logs system status messages (admin/reports/status) to the watchdog. This is especially useful when combined with syslog and external monitoring solutions such as Splunk.

Dependencies

• xautoload

Installation

Simply turn on the module and watchdog messages will be logged during cron runs. By default, messages are logged once per hour and after a cache clear. This ensures that any changes in status after a deployment are immediately logged.

This modules provides possibility to move site configuration from files to database with just a couple clicks!

How often did you expirience a situation when module or distribution provides default views, rules, entities and other configurations out of the box which you had to change and then deploy it with Features? We know it was a hard time full of your tears and screams like "Drupal, why?"

The intent of this module is to provide a way to render general HTML as part of a entity form. This module provides a field that does that.

The main inspiration for this was build entityforms and needing a way to insert general HTML into the form being presented to the end user.

This module adds the ability to link directly to a file in the menu. A number of people have suggested adding the code to a module so here is an attempt at solving that issue.

Taxdropnomy (named as an awful combination of "Taxo + Drag'n'drop + nomy"
(please don't ask me what was I thinking...)

enables drag'n'drop functionality in updating node fields of type taxonomy term reference.

On its first version, it works only for node (no other entities) and classic taxonomy term reference fields (not the general entity reference)

This is a placeholder for a module idea.

Once would run some arbitrary code implemented within a hook a single time. The motivation was originally from issues surrounding writing install/update hooks that would pre-populate some entities, but were dependent on fields that would need to be created within a Features module revert. Reverts typically occur after database updates in continuous integration setups. So writing an update hook-like script that could be called on demand could provide a workaround.

The Configuration Update Manager project contains a base module and a reporting module.

Use the base module if another project has it as a dependency (example: Features).

The report 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.

This creates an Entity for use with the Slack messaging service. This entity does nothing by itself, but can be leveraged by other modules requiring it. Because it is an entity, this means that once you get data here via Slack it has Views, Field UI and RestWS integration automatically.

Demo sandbox for tutorial

Node template reaction allows to set node's template as context reaction.

In difference of context node template module, it allows to choose node.tpl file for node (not page.tpl) as context reaction.

Created by ADCI solutions team