Maintenance fixes only

Most customers of company I work for use some sort of product management software for keeping track of their product inventory. All these applications have option to export product prices to a CSV file, so it is very important to offer our customers an option to easily update prices on their website, without creating complicated and often expensive API integrations. That is the main reason behind creating this Drupal 8 module.

Drupal core search module makes two requests when a search block form is submitted. The first is a POST request that results in a form redirect to a new URL (normally /search/node) where the search is performed based on the GET parameters. For sites that are more performance consious this operation is expensive especially if parameters of the search are already known.

This module assumes that search block form is used for searches on content (search/node/[terms]).

This Module helps you to add taxonomy term when we have large taxonomy terms trail and we want to add term child under specified parent item.

Installation

Install your module as
https://drupal.org/documentation/install/modules-themes/modules-7

How to use

• Visit overview vocabulary list terms form,
• admin/structure/taxonomy/[VOCABULARY_MACHINE_NAME],
• you'll see the add child link.

This module provides an alternative field storage backend. A table is created on a per-entity-type basis. All fields for each entity (well, those using our storage) are stored in one big serialized field.

This substantially reduces the number of database tables and database queries. It is an alternative to the caching approach offered by entitycache.

This project uses jQuery Favorite Widget plugin that allows users to put content to their favorites that are stored in a cookie.

For Drupal, there are modules available that allows you to reach this functionality such as Flag. This module however is useful when you want to provide this functionality:

Outputs a term label and all of its parents.

By default the Apachesolr Views module renders fields that are in the Solr-index.
This module adds a Views row plugin for 'Rendered entity'.
That way you can leverage modules like Display Suite for presenting your search-results.

The code is a straight copy from this issue:
https://www.drupal.org/node/2111363

A low-level utility module which facilitates entity edit forms which do not attach field forms by default, but rather allow the user to select which fields to edit. This is useful when an entity type has many fields but where individual entities populate relatively few of them.

This module provides no UI overrides or configurability on its own. It is designed to be used by other modules either for their own entity types, or to override the edit forms of existing entity types.

This module provides a single function:

PLEASE DONATE

Simplify per-bundle entity access checking for routes. Example: _entity_access: <ENTITY_TYPE>[:<BUNDLE>].<OPERATION>.

From the developer perspective, this module - just improvement of existing access_check.entity service. Default implementation - DrupalCoreEntityEntityAccessCheck - overridden and empowered with possibility to verify entity bundle, if it specified. That's all.