Mercurial > hg > isophonics-drupal-site
comparison core/modules/layout_builder/layout_builder.api.php @ 18:af1871eacc83
Update to Drupal core 8.7.1
author | Chris Cannam |
---|---|
date | Thu, 09 May 2019 15:33:08 +0100 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
17:129ea1e6d783 | 18:af1871eacc83 |
---|---|
1 <?php | |
2 | |
3 /** | |
4 * @file | |
5 * Hooks provided by the Layout Builder module. | |
6 */ | |
7 | |
8 /** | |
9 * @defgroup layout_builder_access Layout Builder access | |
10 * @{ | |
11 * In determining access rights for the Layout Builder UI, | |
12 * \Drupal\layout_builder\Access\LayoutBuilderAccessCheck checks if the | |
13 * specified section storage plugin (an implementation of | |
14 * \Drupal\layout_builder\SectionStorageInterface) grants access. | |
15 * | |
16 * By default, the Layout Builder access check requires the 'configure any | |
17 * layout' permission. Individual section storage plugins may override this by | |
18 * setting the 'handles_permission_check' annotation key to TRUE. Any section | |
19 * storage plugin that uses 'handles_permission_check' must provide its own | |
20 * complete routing access checking to avoid any access bypasses. | |
21 * | |
22 * This access checking is only enforced on the routing level (not on the entity | |
23 * or field level) with additional form access restrictions. All HTTP API access | |
24 * to Layout Builder data is currently forbidden. | |
25 * | |
26 * @see https://www.drupal.org/project/drupal/issues/2942975 | |
27 */ | |
28 | |
29 /** | |
30 * @} End of "defgroup layout_builder_access". | |
31 */ |