Minimally maintained

This module extends the functionality of the Personalize module, adding a decision agent for A/B testing that isn't dependent on any Third Party calls or services. It provides a personalization agent that leverages the Executors of Personalize but does straight A/B testing on two or more Variants. Editors can optionally specify more complicated splits that aren't even distributions.

search_api_solr_pro

Module extension to prevent the entities being loaded from solr results in views by a query setting.

Motivation:

The well know module search_api_solr (https://www.drupal.org/project/search_api_solr) force the entities to beign loaded from the solr results in views, ignoring if the user only want to display specific fields that are already indexed in solr. In that case we can improve the performance of view generation avoiding the load of the entities.

WARNING: Unless you are required to use this module to maintain UI backwards compatibility, do not install. Core provides an improved UX out of the box!

This module reintroduces two UI elements that existed in core 8.3 but were superseded in 8.4:

Don't like the layouts provided by the core layout_discovery module? This override will stop the layout_discovery module from providing any layouts. This is useful if you're using another module that displays layouts available (like Bricks), but the ones provided by core don't suit your site's needs.

REQUIREMENTS

You must have the layout_discovery core module installed.

INSTALLATION

Defines additional migrate plugins for file imports:

File Import

Imports a file from an local or external source. Files will be downloaded or copied from the source if necessary and a file entity will be created for it. The file can be moved, reused, or set to be automatically renamed if a duplicate exists.

Defines a new "Expression" field type which will evaluate a mathematical expression.

This module provides support for Search API in References Dialog modules.

Use case

The Search dialog should query a Search Index using views, and not directly the database.

Implementation

There is support only for entity reference fields at the moment.

This module is a tool for providing a machine name as a property (Base Field) on content entities.

There is no configuration form for this module... you have to edit the configuration yourself to tell the module which entities you would like the machine_name property applied to.

We are currently making one assumption about the entity: We assume it has a "label" property (standard content entity title field).

This module provides a new "Defined table" field type, that allows administrators and content builders to add tables to content.

Table header row and column (data labels) can be either predefined in field settings (the same for a field instance) or set to dynamic and definable per entity.

Possible label sources:

• Taxonomy vocabulary
• Custom input

Other table field modules:

This Composer plugin will display a warning when users install or update Drupal packages (via Composer) that are not supported by the Drupal Security team, as per the Security Advisory Policy.

Example

Installing or updating a "non-covered" Drupal package via composer install will display: