Articles
In past articles, we have already encountered hooks. In this article, we’ll take a closer look at hooks that help you work with entities.
In this article, you can read in general what hooks are and why they are needed:
http://drupalbook.org/drupal/92-what-hook-drupal-8
We will use hooks to add our custom code that will fire on certain events related to entities: add, delete, update.
You can see all the Drupal hooks on this page:
The events system allows you to build more complex systems with the ability to change functionality using custom code for certain events. Many hooks from Drupal 7 have been replaced by events. This allowed to unify the work of many parts of Drupal and additional copy modules. The events system itself came from Symfony and consists of the following parts:
Event Subscribers - “Subscribers” to specific events are functions or methods that fire on certain events. In code, is a class that implements the class:
In this article we will consider Field Formatters, that allow us to edit the display of fields and display them on the page.
In past articles, we created field type Link, in this article we will look at how these fields are displayed on the page and which class is responsible for it. Each field that you add through Drupal can be displayed on the page and edit its settings on the page Manage display.
It's common case to execute in developing Drupal modules. You should use entityQuery where it's possible, but sometimes it's needed to use SQL query to get more sophisticated data.
You can add to bookmarks this page to always have a cheat sheet on hand how to execute MySQL queries select, insert, update, delete in Drupal.
Select
Get single value:
In previous articles we have seen how the Link field type works: Storage, Widget, Formatter. In this article we will make our own bone field type for outputting video from youtube on a page with two different formats and settings.
This article focuses on the Fields API, and if you need to add the Yotube video field to your site, it is better to use the ready-made module:
In this article we will consider Field Formatters, that allow us to edit the display of fields and display them on the page.
In past articles, we created field type Link, in this article we will look at how these fields are displayed on the page and which class is responsible for it. Each field that you add through Drupal can be displayed on the page and edit its settings on the page Manage display.
In this tutorial we will look at how the Field Widget of the Link module works. This is a review article, so if you want to start writing your File Widget, please skip to the following articles.
In the last lesson we added Link fields for nodes and blocks. Now let's look at what the form for the Link field is formed by.
We have already met with autoloading of PHP classes in Drupal, and there is also a WidgetBase field widget class for fields:
core/lib/Drupal/Core/Field/WidgetBase.php
In this article we will understand how fields in Drupal work, why they are needed and how fields help to quickly develop sites in Drupal.
We have already worked with fields in previous articles:
Very often access to 3rd party services must be different on dev and live instans. In order to do this with the help of configurations, you need to use the Configuration Split module:
https://www.drupal.org/project/config_split
After you enable the Config Split module, you will be able to specify the folders for the instances. Let's go to the Configuration Split settings page of the Configuration module:
/admin/config/development/configuration/config-split
When you import a configuration from one site to another, some configurations are needed to output content, but the configuration content itself does not contain any. In this tutorial, we will explain how to transfer blocks, nodes and taxonomy terms from one site to another.