public ConfigBase::getCacheContexts() The cache contexts associated with this object. These identify a specific variation/representation of the object. Cache contexts are tokens: placeholders that are converted to cache keys by the @cache_contexts_manager service. The replacement value depends on the request context (the current URL, language, and so on). They're converted before storing an object in cache. Return value string[] An array of cache context tokens, used to generate a cache ID. Ov

hook_file_copy(Drupal\file\FileInterface $file, Drupal\file\FileInterface $source) Respond to a file that has been copied. Parameters \Drupal\file\FileInterface $file: The newly copied file entity. \Drupal\file\FileInterface $source: The original file before the copy. See also file_copy() Related topics Hooks Define functions that alter the behavior of Drupal core. File core/modules/file/file.api.php, line 50 Hooks for file module. Code function hook_file_copy(Drupal\file\FileInterface $f

The wrapped response object. Type: \Symfony\Component\HttpFoundation\Response; File core/lib/Drupal/Core/Form/EnforcedResponse.php, line 28 Class EnforcedResponse A wrapper containing a response which is to be enforced upon delivery. Namespace Drupal\Core\Form Code protected $response;

Exception thrown by ContentLanguageSettings when target bundle is not set. Hierarchy class \Drupal\language\ContentLanguageSettingsException extends \RuntimeException File core/modules/language/src/ContentLanguageSettingsException.php, line 8 Namespace Drupal\language Members

protected Tasks::fail($message) Assert test as failed. File core/lib/Drupal/Core/Database/Install/Tasks.php, line 92 Class Tasks Database installer structure. Namespace Drupal\Core\Database\Install Code protected function fail($message) { $this->results['fail'][] = $message; }

public ThemeHandlerInterface::refreshInfo() Refreshes the theme info data of currently installed themes. Modules can alter theme info, so this is typically called after a module has been installed or uninstalled. File core/lib/Drupal/Core/Extension/ThemeHandlerInterface.php, line 110 Class ThemeHandlerInterface Manages the list of available themes. Namespace Drupal\Core\Extension Code public function refreshInfo();

The entity type. Type: string File core/lib/Drupal/Core/Entity/Entity.php, line 33 Class Entity Defines a base entity class. Namespace Drupal\Core\Entity Code protected $entityTypeId;

Provides an interface defining a node entity. Hierarchy interface \Drupal\Core\Entity\ContentEntityInterface extends \Traversable; interface \Drupal\Core\Entity\EntityChangedInterface; interface \Drupal\user\EntityOwnerInterface; interface \Drupal\Core\Entity\RevisionLogInterfaceinterface \Drupal\node\NodeInterface File core/modules/node/src/NodeInterface.php, line 13 Namespace Drupal\node Members Name Modifiers Type Description AccessibleInterface::access public function

public MenuLinkFormInterface::extractFormValues(array &$form, FormStateInterface $form_state) Extracts a plugin definition from form values. Parameters array $form: An associative array containing the structure of the form. \Drupal\Core\Form\FormStateInterface $form_state: The current state of the form. Return value array The new plugin definition values taken from the form values. The plugin ID must be returned as part of the definition. File core/lib/Drupal/Core/Menu/Form/MenuLinkFormIn

Returns cached responses as early and avoiding as much work as possible. Dynamic Page Cache is able to cache so much because it utilizes cache contexts: the cache contexts that are present capture the variations of every component of the page. That, combined with the fact that cacheability metadata is bubbled, means that the cache contexts at the page level represent the complete set of contexts that the page varies by. The reason Dynamic Page Cache is implemented as two event subscribers (a la