123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221 |
- <?php
- /**
- * @file
- * Hooks provided by the Block module.
- */
- use Drupal\Core\Access\AccessResult;
- /**
- * @defgroup block_api Block API
- * @{
- * Information about the classes and interfaces that make up the Block API.
- *
- * Blocks are a combination of a configuration entity and a plugin. The
- * configuration entity stores placement information (theme, region, weight) and
- * any other configuration that is specific to the block. The block plugin does
- * the work of rendering the block's content for display.
- *
- * To define a block in a module you need to:
- * - Define a Block plugin by creating a new class that implements the
- * \Drupal\Core\Block\BlockPluginInterface, in namespace Plugin\Block under your
- * module namespace. For more information about creating plugins, see the
- * @link plugin_api Plugin API topic. @endlink
- * - Usually you will want to extend the \Drupal\Core\Block\BlockBase class, which
- * provides a common configuration form and utility methods for getting and
- * setting configuration in the block configuration entity.
- * - Block plugins use the annotations defined by
- * \Drupal\Core\Block\Annotation\Block. See the
- * @link annotation Annotations topic @endlink for more information about
- * annotations.
- *
- * The Block API also makes use of Condition plugins, for conditional block
- * placement. Condition plugins have interface
- * \Drupal\Core\Condition\ConditionInterface, base class
- * \Drupal\Core\Condition\ConditionPluginBase, and go in plugin namespace
- * Plugin\Condition. Again, see the Plugin API and Annotations topics for
- * details of how to create a plugin class and annotate it.
- *
- * There are also several block-related hooks, which allow you to affect
- * the content and access permissions for blocks:
- * - hook_block_view_alter()
- * - hook_block_view_BASE_BLOCK_ID_alter()
- * - hook_block_access()
- *
- * Further information and examples:
- * - \Drupal\system\Plugin\Block\SystemPoweredByBlock provides a simple example
- * of defining a block.
- * - \Drupal\user\Plugin\Condition\UserRole is a straightforward example of a
- * block placement condition plugin.
- * - \Drupal\book\Plugin\Block\BookNavigationBlock is an example of a block with
- * a custom configuration form.
- * - For a more in-depth discussion of the Block API, see
- * https://www.drupal.org/developing/api/8/block_api.
- * - The Examples for Developers project also provides a Block example in
- * https://www.drupal.org/project/examples.
- * @}
- */
- /**
- * @addtogroup hooks
- * @{
- */
- /**
- * Alter the result of \Drupal\Core\Block\BlockBase::build().
- *
- * This hook is called after the content has been assembled in a structured
- * array and may be used for doing processing which requires that the complete
- * block content structure has been built.
- *
- * If the module wishes to act on the rendered HTML of the block rather than
- * the structured content array, it may use this hook to add a #post_render
- * callback. Alternatively, it could also implement hook_preprocess_HOOK() for
- * block.html.twig. See drupal_render() documentation or the
- * @link themeable Default theme implementations topic @endlink for details.
- *
- * In addition to hook_block_view_alter(), which is called for all blocks, there
- * is hook_block_view_BASE_BLOCK_ID_alter(), which can be used to target a
- * specific block or set of similar blocks.
- *
- * @param array &$build
- * A renderable array of data, as returned from the build() implementation of
- * the plugin that defined the block:
- * - #title: The default localized title of the block.
- * @param \Drupal\Core\Block\BlockPluginInterface $block
- * The block plugin instance.
- *
- * @see hook_block_view_BASE_BLOCK_ID_alter()
- * @see entity_crud
- *
- * @ingroup block_api
- */
- function hook_block_view_alter(array &$build, \Drupal\Core\Block\BlockPluginInterface $block) {
- // Remove the contextual links on all blocks that provide them.
- if (isset($build['#contextual_links'])) {
- unset($build['#contextual_links']);
- }
- }
- /**
- * Provide a block plugin specific block_view alteration.
- *
- * In this hook name, BASE_BLOCK_ID refers to the block implementation's plugin
- * id, regardless of whether the plugin supports derivatives. For example, for
- * the \Drupal\system\Plugin\Block\SystemPoweredByBlock block, this would be
- * 'system_powered_by_block' as per that class's annotation. And for the
- * \Drupal\system\Plugin\Block\SystemMenuBlock block, it would be
- * 'system_menu_block' as per that class's annotation, regardless of which menu
- * the derived block is for.
- *
- * @param array $build
- * A renderable array of data, as returned from the build() implementation of
- * the plugin that defined the block:
- * - #title: The default localized title of the block.
- * @param \Drupal\Core\Block\BlockPluginInterface $block
- * The block plugin instance.
- *
- * @see hook_block_view_alter()
- * @see entity_crud
- *
- * @ingroup block_api
- */
- function hook_block_view_BASE_BLOCK_ID_alter(array &$build, \Drupal\Core\Block\BlockPluginInterface $block) {
- // Change the title of the specific block.
- $build['#title'] = t('New title of the block');
- }
- /**
- * Alter the result of \Drupal\Core\Block\BlockBase::build().
- *
- * Unlike hook_block_view_alter(), this hook is called very early, before the
- * block is being assembled. Therefore, it is early enough to alter the
- * cacheability metadata (change #cache), or to explicitly placeholder the block
- * (set #create_placeholder).
- *
- * In addition to hook_block_build_alter(), which is called for all blocks,
- * there is hook_block_build_BASE_BLOCK_ID_alter(), which can be used to target
- * a specific block or set of similar blocks.
- *
- * @param array &$build
- * A renderable array of data, only containing #cache.
- * @param \Drupal\Core\Block\BlockPluginInterface $block
- * The block plugin instance.
- *
- * @see hook_block_build_BASE_BLOCK_ID_alter()
- * @see entity_crud
- *
- * @ingroup block_api
- */
- function hook_block_build_alter(array &$build, \Drupal\Core\Block\BlockPluginInterface $block) {
- // Add the 'user' cache context to some blocks.
- if ($some_condition) {
- $build['#cache']['contexts'][] = 'user';
- }
- }
- /**
- * Provide a block plugin specific block_build alteration.
- *
- * In this hook name, BASE_BLOCK_ID refers to the block implementation's plugin
- * id, regardless of whether the plugin supports derivatives. For example, for
- * the \Drupal\system\Plugin\Block\SystemPoweredByBlock block, this would be
- * 'system_powered_by_block' as per that class's annotation. And for the
- * \Drupal\system\Plugin\Block\SystemMenuBlock block, it would be
- * 'system_menu_block' as per that class's annotation, regardless of which menu
- * the derived block is for.
- *
- * @param array $build
- * A renderable array of data, only containing #cache.
- * @param \Drupal\Core\Block\BlockPluginInterface $block
- * The block plugin instance.
- *
- * @see hook_block_build_alter()
- * @see entity_crud
- *
- * @ingroup block_api
- */
- function hook_block_build_BASE_BLOCK_ID_alter(array &$build, \Drupal\Core\Block\BlockPluginInterface $block) {
- // Explicitly enable placeholdering of the specific block.
- $build['#create_placeholder'] = TRUE;
- }
- /**
- * Control access to a block instance.
- *
- * Modules may implement this hook if they want to have a say in whether or not
- * a given user has access to perform a given operation on a block instance.
- *
- * @param \Drupal\block\Entity\Block $block
- * The block instance.
- * @param string $operation
- * The operation to be performed; for instance, 'view', 'create', 'delete', or
- * 'update'.
- * @param \Drupal\Core\Session\AccountInterface $account
- * The user object to perform the access check operation on.
- *
- * @return \Drupal\Core\Access\AccessResultInterface
- * The access result. If all implementations of this hook return
- * AccessResultInterface objects whose value is !isAllowed() and
- * !isForbidden(), then default access rules from
- * \Drupal\block\BlockAccessControlHandler::checkAccess() are used.
- *
- * @see \Drupal\Core\Entity\EntityAccessControlHandler::access()
- * @see \Drupal\block\BlockAccessControlHandler::checkAccess()
- * @ingroup block_api
- */
- function hook_block_access(\Drupal\block\Entity\Block $block, $operation, \Drupal\Core\Session\AccountInterface $account) {
- // Example code that would prevent displaying the 'Powered by Drupal' block in
- // a region different than the footer.
- if ($operation == 'view' && $block->getPluginId() == 'system_powered_by_block') {
- return AccessResult::forbiddenIf($block->getRegion() != 'footer')->addCacheableDependency($block);
- }
- // No opinion.
- return AccessResult::neutral();
- }
- /**
- * @} End of "addtogroup hooks".
- */
|