Drupal 8's robust plugin system empowers backend developers with reusable functionality. This article (part one of two) details building a feature enabling custom forms with node entities, allowing configuration of node bundles to utilize various form types alongside node displays. New form types are easily defined by extending a provided base class. (For a complete code example, refer to this repository).
This tutorial avoids in-depth plugin mechanics, assuming familiarity with the underlying theory. We'll construct our custom plugin type using two interfaces and six classes—a seemingly large number, but mostly straightforward boilerplate code. Part two will demonstrate attaching these reusable forms to nodes.
Key Concepts:
- Drupal 8's plugin system facilitates reusable functionality, enabling custom forms for node entities. Node bundles can be configured to use multiple form types within node displays.
- The plugin manager, essential for plugin discovery and loading, leverages Drupal's default base class for easy extension. All plugins must implement a defined interface.
- Plugin definitions utilize annotations containing crucial information: the plugin subdirectory, the required interface, and the annotation class defining plugin properties.
- A custom plugin type requires a base class extensible by all plugins. This class implements the interface and uses dependency injection for the
form_builder
service, essential for form construction. The plugin interacts with form classes; the next step is integrating these forms with node displays.
Plugin Manager:
The plugin manager, crucial for discovering and loading plugins, extends Drupal's DefaultPluginManager
. Within the module's /src
directory, ReusableFormManager.php
contains:
<?php namespace Drupal\reusable_forms; use Drupal\Core\Plugin\DefaultPluginManager; use Drupal\Core\Cache\CacheBackendInterface; use Drupal\Core\Extension\ModuleHandlerInterface; class ReusableFormsManager extends DefaultPluginManager { public function __construct(\Traversable $namespaces, CacheBackendInterface $cache_backend, ModuleHandlerInterface $module_handler) { parent::__construct('Plugin/ReusableForm', $namespaces, $module_handler, 'Drupal\reusable_forms\ReusableFormPluginInterface', 'Drupal\reusable_forms\Annotation\ReusableForm'); $this->alterInfo('reusable_forms_info'); $this->setCacheBackend($cache_backend, 'reusable_forms'); } }
This extends DefaultPluginManager
, overriding the constructor. Key parameters define:
Plugin/ReusableForm
: Plugin subdirectory.Drupalreusable_formsReusableFormPluginInterface
: Required plugin interface.Drupalreusable_formsAnnotationReusableForm
: Annotation class defining plugin properties.
An alter hook (reusable_forms_info
) allows modules to modify plugin definitions, and the cache backend is configured.
Plugin Interface:
The interface (ReusableFormPluginInterface.php
in /src
) defines methods all plugins must implement:
<?php namespace Drupal\reusable_forms; use Drupal\Core\Plugin\DefaultPluginManager; use Drupal\Core\Cache\CacheBackendInterface; use Drupal\Core\Extension\ModuleHandlerInterface; class ReusableFormsManager extends DefaultPluginManager { public function __construct(\Traversable $namespaces, CacheBackendInterface $cache_backend, ModuleHandlerInterface $module_handler) { parent::__construct('Plugin/ReusableForm', $namespaces, $module_handler, 'Drupal\reusable_forms\ReusableFormPluginInterface', 'Drupal\reusable_forms\Annotation\ReusableForm'); $this->alterInfo('reusable_forms_info'); $this->setCacheBackend($cache_backend, 'reusable_forms'); } }
getName()
returns the plugin name; buildForm()
accepts an entity and returns a render array for a form implementing Drupalreusable_formsFormReusableFormInterface
. It extends PluginInspectionInterface
and ContainerFactoryPluginInterface
for added functionality and dependency injection.
Plugin Annotation:
The annotation class (ReusableForm.php
in /src/Annotation
) defines plugin properties:
<?php namespace Drupal\reusable_forms; use Drupal\Core\Entity\EntityInterface; use Drupal\Core\Plugin\ContainerFactoryPluginInterface; use Drupal\Component\Plugin\PluginInspectionInterface; interface ReusableFormPluginInterface extends PluginInspectionInterface, ContainerFactoryPluginInterface { public function getName(); public function buildForm($entity); }
id
, name
, and form
(the fully qualified form class name) are defined here.
Plugin Base Class:
The plugin base class (ReusableFormPluginBase.php
in /src
) provides defaults:
<?php namespace Drupal\reusable_forms\Annotation; use Drupal\Component\Annotation\Plugin; /** * @Annotation */ class ReusableForm extends Plugin { public $id; public $name; public $form; }
This extends PluginBase
, implements ReusableFormPluginInterface
, and uses dependency injection for form_builder
. getName()
and buildForm()
are implemented, using the form class specified in the annotation.
Form Interface and Base Class:
A simple form interface (ReusableFormInterface.php
in /src/Form
) and base class (ReusableFormBase.php
in /src/Form
) are created for consistency: (These are shown in the original response, and are not repeated here for brevity).
Conclusion (Part 1):
This first part sets up the custom plugin type, preparing it for integration with form classes. Part two will cover displaying these forms with nodes, involving node type configuration and form rendering within content view modes.
The above is the detailed content of Drupal 8 Custom Plugin Types. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Common problems and solutions for PHP variable scope include: 1. The global variable cannot be accessed within the function, and it needs to be passed in using the global keyword or parameter; 2. The static variable is declared with static, and it is only initialized once and the value is maintained between multiple calls; 3. Hyperglobal variables such as $_GET and $_POST can be used directly in any scope, but you need to pay attention to safe filtering; 4. Anonymous functions need to introduce parent scope variables through the use keyword, and when modifying external variables, you need to pass a reference. Mastering these rules can help avoid errors and improve code stability.

To safely handle PHP file uploads, you need to verify the source and type, control the file name and path, set server restrictions, and process media files twice. 1. Verify the upload source to prevent CSRF through token and detect the real MIME type through finfo_file using whitelist control; 2. Rename the file to a random string and determine the extension to store it in a non-Web directory according to the detection type; 3. PHP configuration limits the upload size and temporary directory Nginx/Apache prohibits access to the upload directory; 4. The GD library resaves the pictures to clear potential malicious data.

There are three common methods for PHP comment code: 1. Use // or # to block one line of code, and it is recommended to use //; 2. Use /.../ to wrap code blocks with multiple lines, which cannot be nested but can be crossed; 3. Combination skills comments such as using /if(){}/ to control logic blocks, or to improve efficiency with editor shortcut keys, you should pay attention to closing symbols and avoid nesting when using them.

AgeneratorinPHPisamemory-efficientwaytoiterateoverlargedatasetsbyyieldingvaluesoneatatimeinsteadofreturningthemallatonce.1.Generatorsusetheyieldkeywordtoproducevaluesondemand,reducingmemoryusage.2.Theyareusefulforhandlingbigloops,readinglargefiles,or

The key to writing PHP comments is to clarify the purpose and specifications. Comments should explain "why" rather than "what was done", avoiding redundancy or too simplicity. 1. Use a unified format, such as docblock (/*/) for class and method descriptions to improve readability and tool compatibility; 2. Emphasize the reasons behind the logic, such as why JS jumps need to be output manually; 3. Add an overview description before complex code, describe the process in steps, and help understand the overall idea; 4. Use TODO and FIXME rationally to mark to-do items and problems to facilitate subsequent tracking and collaboration. Good annotations can reduce communication costs and improve code maintenance efficiency.

ToinstallPHPquickly,useXAMPPonWindowsorHomebrewonmacOS.1.OnWindows,downloadandinstallXAMPP,selectcomponents,startApache,andplacefilesinhtdocs.2.Alternatively,manuallyinstallPHPfromphp.netandsetupaserverlikeApache.3.OnmacOS,installHomebrew,thenrun'bre

TolearnPHPeffectively,startbysettingupalocalserverenvironmentusingtoolslikeXAMPPandacodeeditorlikeVSCode.1)InstallXAMPPforApache,MySQL,andPHP.2)Useacodeeditorforsyntaxsupport.3)TestyoursetupwithasimplePHPfile.Next,learnPHPbasicsincludingvariables,ech

In PHP, you can use square brackets or curly braces to obtain string specific index characters, but square brackets are recommended; the index starts from 0, and the access outside the range returns a null value and cannot be assigned a value; mb_substr is required to handle multi-byte characters. For example: $str="hello";echo$str[0]; output h; and Chinese characters such as mb_substr($str,1,1) need to obtain the correct result; in actual applications, the length of the string should be checked before looping, dynamic strings need to be verified for validity, and multilingual projects recommend using multi-byte security functions uniformly.
