opdavies/drupalcampbristol
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update to Drupal 8.0.1. For more information, see https://www.drupal.org/node/2627402

Browse source
This commit is contained in:
Pantheon Automation 2015-12-02 11:38:43 -08:00 • committed by Greg Anderson
parent 013aaaf2ff
commit 1a0e9d9fac
153 changed files with 1268 additions and 670 deletions
Download patch file Download diff file Expand all files Collapse all files

6
core/lib/Drupal/Core/Render/Element/FormElement.php
View file

@ -30,9 +30,9 @@ use Drupal\Core\Url;
* additional information, as well as a list of properties that are common to
* all render elements (including form elements). Properties specific to a
* particular element are documented on that element's class.
* Here is a list of properties that are used during the rendering and
* form processing of form elements:
*
* Here is a list of properties that are used during the rendering and form
* processing of form elements:
* - #after_build: (array) Array of callables or function names, which are
* called after the element is built. Arguments: $element, $form_state.
* - #ajax: (array) Array of elements to specify Ajax behavior. See

12
core/lib/Drupal/Core/Render/Element/MachineName.php
View file

@ -190,7 +190,17 @@ class MachineName extends Textfield {
}
$element['#attached']['library'][] = 'core/drupal.machine-name';
$element['#attached']['drupalSettings']['machineName']['#' . $source['#id']] = $element['#machine_name'];
$options = [
'replace_pattern',
'replace',
'maxlength',
'target',
'label',
'field_prefix',
'field_suffix',
'suffix',
];
$element['#attached']['drupalSettings']['machineName']['#' . $source['#id']] = array_intersect_key($element['#machine_name'], array_flip($options));
$element['#attached']['drupalSettings']['langcode'] = $language->getId();
return $element;

27
core/lib/Drupal/Core/Render/theme.api.php
View file

@ -68,12 +68,12 @@
* receives are documented in the header of the default Twig template file.
*
* hook_theme() implementations can also specify that a theme hook
* implementation is a theme function, but that is uncommon. It is only used for
* special cases, for performance reasons, because rendering using theme
* functions is somewhat faster than theme templates. Note that while Twig
* templates will auto-escape variables, theme functions must explicitly escape
* any variables by using theme_render_and_autoescape(). Failure to do so is
* likely to result in security vulnerabilities.
* implementation is a theme function, but that is uncommon and not recommended.
* Note that while Twig templates will auto-escape variables, theme functions
* must explicitly escape any variables by using theme_render_and_autoescape().
* Failure to do so is likely to result in security vulnerabilities. Theme
* functions are deprecated in Drupal 8.0.x and will be removed before
* Drupal 9.0.x. Use Twig templates instead.
*
* @section sec_overriding_theme_hooks Overriding Theme Hooks
* Themes may register new theme hooks within a hook_theme() implementation, but
@ -98,7 +98,8 @@
* default function is again a good starting point for overriding its behavior.
* Again, note that theme functions (unlike templates) must explicitly escape
* variables using theme_render_and_autoescape() or risk security
* vulnerabilities.
* vulnerabilities. Theme functions are deprecated in Drupal 8.0.x and will be
* removed before Drupal 9.0.x. Use Twig templates instead.
*
* @section sec_preprocess_templates Preprocessing for Template Files
* If the theme implementation is a template file, several functions are called
@ -998,7 +999,7 @@ function hook_page_attachments(array &$attachments) {
* @param array &$attachments
* Array of all attachments provided by hook_page_attachments() implementations.
*
* @see hook_page_attachments_alter()
* @see hook_page_attachments()
*/
function hook_page_attachments_alter(array &$attachments) {
// Conditionally remove an asset.
@ -1080,8 +1081,7 @@ function hook_page_bottom(array &$page_bottom) {
* element or tree in preprocess and process functions.
* - file: The file the implementation resides in. This file will be included
* prior to the theme being rendered, to make sure that the function or
* preprocess function (as needed) is actually loaded; this makes it
* possible to split theme functions out into separate files quite easily.
* preprocess function (as needed) is actually loaded.
* - path: Override the path of the file to be used. Ordinarily the module or
* theme path will be used, but if the file will not be in the default
* path, include it here. This path should be relative to the Drupal root
@ -1094,9 +1094,10 @@ function hook_page_bottom(array &$page_bottom) {
* specified, a default template name will be assumed. For example, if a
* module registers the 'search_result' theme hook, 'search-result' will be
* assigned as its template name.
* - function: If specified, this will be the function name to invoke for
* this implementation. If neither 'template' nor 'function' are specified,
* a default template name will be assumed. See above for more details.
* - function: (deprecated in Drupal 8.0.x, will be removed in Drupal 9.0.x)
* If specified, this will be the function name to invoke for this
* implementation. If neither 'template' nor 'function' are specified, a
* default template name will be assumed. See above for more details.
* - base hook: Used for theme suggestions only: the base theme hook name.
* Instead of this suggestion's implementation being used directly, the base
* hook will be invoked with this implementation as its first suggestion.