Developer

Module to easily perform real-time external REST requests and converted to Drupal REST endpoints from your app.

This helps in hiding your Access Key as the external url(ex: https://api.meetup.com/2/cities?&key=xxxxxxxxxxxxxxxxxx) is internally called from your app and not from the client browser.

The module creates a content type "Guzzle Drupal Endpoint" which is as shown in the figure and currently supports GET, PUT and POST calls only using Guzzle.

Drupal 8 export of highlight,js module.

This module provides an Excel encoder via LibXL Library (commerce) for the Drupal 8 Serialization API. This enables the XLS and XLSX format to be used for data output.

A module built to resolve or avoid the error "Unable to install already exists active configuration" when re installing/un installing the drupal 8 modules , it works even if a module's configs not contains enforced in yml or not added configs in optional folder. It removes active configuration object of uninstalled modules and helps to remove configuration object while uninstalling a module without using Drush / Devel / Drupal Console / Features Modules

Features

Are you missing the Symfony's dependency injection container? This is what you're looking for!

Usage

To start using this package you must install it via Composer. Thereafter add the next line to the *.info file of the module which is going to populate dependencies to the container:

Purpose

Reinstall provides extra tools for the Drupal 8 Migrate (Migrate Plus / Migrate Tools) modules, to ease deployment from existing content, including complex hierarchies combining core entities and Paragraphs via both EntityReference and EntityReferenceRevisions.

Comparison with alternatives

Unlike Default Content and other existing similar solutions,

// WIP

Drupal 8 serialization system is pretty flexible but it causes serious time cost
to recursively process all entities, their fields, embed entities if they are
exist and etc.
This module provides caching for normalized entities (+embedded entities)
using different caches for different accesses (checking "view" for entity and
its fields).

Some websites might contain elements that are considered content by the Drupal CMS while they might not only be used as content. For example custom blocks might be used for a footer that is shared between all environments. Structure sync tries to give you a tool to get around this issue by allowing you to synchronize taxonomy terms, menu links and custom blocks through the configuration. The module will prevent you from having to create content multiple times and also decrease the risk of some elements being out of sync between environments, the main menu for example.