Update to drupal 8.0.0-rc1. For more information, see https://www.drupal.org/node/2582663
This commit is contained in:
parent
eb34d130a8
commit
f32e58e4b1
8476 changed files with 211648 additions and 170042 deletions
|
@ -28,8 +28,8 @@ function node_requirements($phase) {
|
|||
$requirements['node_access'] = array(
|
||||
'title' => t('Node Access Permissions'),
|
||||
'value' => $value,
|
||||
'description' => t('If the site is experiencing problems with permissions to content, you may have to rebuild the permissions cache. Rebuilding will remove all privileges to content and replace them with permissions based on the current modules and settings. Rebuilding may take some time if there is a lot of content or complex permission settings. After rebuilding has completed, content will automatically use the new permissions. <a href="@rebuild">Rebuild permissions</a>', array(
|
||||
'@rebuild' => \Drupal::url('node.configure_rebuild_confirm'),
|
||||
'description' => t('If the site is experiencing problems with permissions to content, you may have to rebuild the permissions cache. Rebuilding will remove all privileges to content and replace them with permissions based on the current modules and settings. Rebuilding may take some time if there is a lot of content or complex permission settings. After rebuilding has completed, content will automatically use the new permissions. <a href=":rebuild">Rebuild permissions</a>', array(
|
||||
':rebuild' => \Drupal::url('node.configure_rebuild_confirm'),
|
||||
)),
|
||||
);
|
||||
}
|
||||
|
@ -197,10 +197,7 @@ function node_update_8003() {
|
|||
// The 'status' and 'uid' fields were added to the 'entity_keys' annotation
|
||||
// of \Drupal\node\Entity\Node in https://www.drupal.org/node/2498919, but
|
||||
// this update function wasn't added until
|
||||
// https://www.drupal.org/node/2542748. In between, sites could have
|
||||
// performed interim updates, which would have included automated entity
|
||||
// schema updates prior to that being removed (see that issue for details).
|
||||
// Therefore, we check for whether the keys have already been installed.
|
||||
// https://www.drupal.org/node/2542748.
|
||||
$manager = \Drupal::entityDefinitionUpdateManager();
|
||||
$entity_type = $manager->getEntityType('node');
|
||||
$entity_keys = $entity_type->getKeys();
|
||||
|
@ -212,10 +209,10 @@ function node_update_8003() {
|
|||
// @todo The above should be enough, since that is the only definition that
|
||||
// changed. But \Drupal\Core\Entity\Sql\SqlContentEntityStorageSchema varies
|
||||
// field schema by whether a field is an entity key, so invoke
|
||||
// onFieldStorageDefinitionUpdate() with an unmodified
|
||||
// $field_storage_definition to trigger the necessary changes.
|
||||
// SqlContentEntityStorageSchema::onEntityTypeUpdate() should be fixed to
|
||||
// automatically handle this.
|
||||
// EntityDefinitionUpdateManagerInterface::updateFieldStorageDefinition()
|
||||
// with an unmodified field storage definition to trigger the necessary
|
||||
// changes. SqlContentEntityStorageSchema::onEntityTypeUpdate() should be
|
||||
// fixed to automatically handle this.
|
||||
// See https://www.drupal.org/node/2554245.
|
||||
foreach (array('status', 'uid') as $field_name) {
|
||||
$manager->updateFieldStorageDefinition($manager->getFieldStorageDefinition($field_name, 'node'));
|
||||
|
|
Reference in a new issue