The name of the module providing the in-place editor plugin. Type: string File core/modules/quickedit/src/Annotation/InPlaceEditor.php, line 35 Class InPlaceEditor Defines an InPlaceEditor annotation object. Namespace Drupal\quickedit\Annotation Code public $module;

The plugin ID. Type: string File core/modules/quickedit/src/Annotation/InPlaceEditor.php, line 28 Class InPlaceEditor Defines an InPlaceEditor annotation object. Namespace Drupal\quickedit\Annotation Code public $id;

Defines an InPlaceEditor annotation object. Plugin Namespace: Plugin\InPlaceEditor For a working example, see \Drupal\quickedit\Plugin\InPlaceEditor\PlainTextEditor Hierarchy class \Drupal\Component\Annotation\Plugin implements AnnotationInterfaceclass \Drupal\quickedit\Annotation\InPlaceEditor See also \Drupal\quickedit\Plugin\InPlaceEditorBase \Drupal\quickedit\Plugin\InPlaceEditorInterface \Drupal\quickedit\Plugin\InPlaceEditorManager Plugin API Related topics Annotations Annotations fo

public static InlineTemplate::preRenderInlineTemplate($element) Renders a twig string directly. Parameters array $element: Return value array File core/lib/Drupal/Core/Render/Element/InlineTemplate.php, line 49 Class InlineTemplate Provides a render element where the user supplies an in-line Twig template. Namespace Drupal\Core\Render\Element Code public static function preRenderInlineTemplate($element) { /** @var \Drupal\Core\Template\TwigEnvironment $environment */ $environment

public InlineTemplate::getInfo() Returns the element properties for this element. Return value array An array of element properties. See \Drupal\Core\Render\ElementInfoManagerInterface::getInfo() for documentation of the standard properties of all elements, and the return value format. Overrides ElementInterface::getInfo File core/lib/Drupal/Core/Render/Element/InlineTemplate.php, line 31 Class InlineTemplate Provides a render element where the user supplies an in-line Twig template. Na

Provides a render element where the user supplies an in-line Twig template. Properties: #template: The inline Twig template used to render the element. #context: (array) The variables to substitute into the Twig template. Each variable may be a string or a render array. Usage example: $build['hello'] = [ '#type' => 'inline_template', '#template' => "{% trans %} Hello {% endtrans %} <strong>{{name}}</strong>", '#context' => [ 'name' => $name, ] ]; Plugin

public InlineFormErrorsServiceProvider::alter(ContainerBuilder $container) Modifies existing service definitions. Parameters ContainerBuilder $container: The ContainerBuilder whose service definitions can be altered. Overrides ServiceProviderBase::alter File core/modules/inline_form_errors/src/InlineFormErrorsServiceProvider.php, line 17 Class InlineFormErrorsServiceProvider Overrides the form_error_handler service to enable inline form errors. Namespace Drupal\inline_form_errors Code

Overrides the form_error_handler service to enable inline form errors. Hierarchy class \Drupal\Core\DependencyInjection\ServiceProviderBase implements ServiceModifierInterface, ServiceProviderInterfaceclass \Drupal\inline_form_errors\InlineFormErrorsServiceProvider File core/modules/inline_form_errors/src/InlineFormErrorsServiceProvider.php, line 12 Namespace Drupal\inline_form_errors Members Name Modifiers Type Description InlineFormErrorsServiceProvider::alter public fu

Types of information in Drupal. Drupal has several distinct types of information, each with its own methods for storage and retrieval: Content: Information meant to be displayed on your site: articles, basic pages, images, files, custom blocks, etc. Content is stored and accessed using Entities. Session: Information about individual users' interactions with the site, such as whether they are logged in. This is really "state" information, but it is not stored the same way so it's a separate ty

public InfoParserInterface::parse($filename) Parses Drupal module, theme and profile .info.yml files. Info files are NOT for placing arbitrary theme and module-specific settings. Use Config::get() and Config::set()->save() for that. Info files are formatted as YAML. If the 'version' key is set to 'VERSION' in any info file, then the value will be substituted with the current version of Drupal core. Information stored in all .info.yml files: name: The real name of the module for display purp