Updating drupal core.
This commit is contained in:
parent
fe8c772cc5
commit
10f3e81b55
@ -20,9 +20,9 @@
|
||||
"drupal/admin_toolbar": "^3.4",
|
||||
"drupal/bootstrap5": "^3.0",
|
||||
"drupal/config_split": "^2.0",
|
||||
"drupal/core-composer-scaffold": "^10.2",
|
||||
"drupal/core-project-message": "^10.2",
|
||||
"drupal/core-recommended": "^10.2",
|
||||
"drupal/core-composer-scaffold": "^10.3",
|
||||
"drupal/core-project-message": "^10.3",
|
||||
"drupal/core-recommended": "^10.3",
|
||||
"drupal/devel_entity_updates": "^4.1",
|
||||
"drupal/field_group": "^3.4",
|
||||
"drupal/gin": "^3.0@RC",
|
||||
@ -32,6 +32,7 @@
|
||||
"drupal/mailsystem": "^4.5",
|
||||
"drupal/migrate_plus": "^6.0",
|
||||
"drupal/migrate_tools": "^6.0",
|
||||
"drupal/openid_connect": "^3.0@alpha",
|
||||
"drupal/pathauto": "^1.12",
|
||||
"drupal/smtp": "^1.4",
|
||||
"drupal/stage_file_proxy": "^2.1",
|
||||
@ -40,7 +41,6 @@
|
||||
"drush/drush": "^12.4",
|
||||
"symfony/css-selector": "^6",
|
||||
"symfony/dom-crawler": "^6",
|
||||
"symfony/polyfill-iconv": "1.28",
|
||||
"symfony/polyfill-php80": "^1.29",
|
||||
"symfony/polyfill-php81": "^1.29",
|
||||
"symfony/polyfill-php82": "^1.29"
|
||||
|
||||
1557
composer.lock
generated
1557
composer.lock
generated
File diff suppressed because it is too large
Load Diff
@ -1,4 +1,8 @@
|
||||
parameters:
|
||||
# Toggles the super user access policy. If your website has at least one user
|
||||
# with the Administrator role, it is advised to set this to false. This allows
|
||||
# you to make user 1 a regular user, strengthening the security of your site.
|
||||
security.enable_super_user: true
|
||||
session.storage.options:
|
||||
# Default ini options for sessions.
|
||||
#
|
||||
@ -60,6 +64,11 @@ parameters:
|
||||
# \Drupal\Core\Session\SessionConfiguration::__construct()
|
||||
# @default 6
|
||||
sid_bits_per_character: 6
|
||||
# By default, Drupal generates a session cookie name based on the full
|
||||
# domain name. Set the name_suffix to a short random string to ensure this
|
||||
# session cookie name is unique on different installations on the same
|
||||
# domain and path (for example, when migrating from Drupal 7).
|
||||
name_suffix: ''
|
||||
twig.config:
|
||||
# Twig debugging:
|
||||
#
|
||||
|
||||
@ -77,7 +77,7 @@
|
||||
*
|
||||
* @code
|
||||
* $databases['default']['default'] = [
|
||||
* 'database' => 'databasename',
|
||||
* 'database' => 'database_name',
|
||||
* 'username' => 'sql_username',
|
||||
* 'password' => 'sql_password',
|
||||
* 'host' => 'localhost',
|
||||
@ -193,7 +193,7 @@
|
||||
* @code
|
||||
* $databases['default']['default'] = [
|
||||
* 'driver' => 'pgsql',
|
||||
* 'database' => 'databasename',
|
||||
* 'database' => 'database_name',
|
||||
* 'username' => 'sql_username',
|
||||
* 'password' => 'sql_password',
|
||||
* 'host' => 'localhost',
|
||||
@ -215,7 +215,7 @@
|
||||
* 'driver' => 'my_driver',
|
||||
* 'namespace' => 'Drupal\my_module\Driver\Database\my_driver',
|
||||
* 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/',
|
||||
* 'database' => 'databasename',
|
||||
* 'database' => 'database_name',
|
||||
* 'username' => 'sql_username',
|
||||
* 'password' => 'sql_password',
|
||||
* 'host' => 'localhost',
|
||||
@ -230,7 +230,7 @@
|
||||
* 'driver' => 'my_driver',
|
||||
* 'namespace' => 'Drupal\my_module\Driver\Database\my_driver',
|
||||
* 'autoload' => 'modules/my_module/src/Driver/Database/my_driver/',
|
||||
* 'database' => 'databasename',
|
||||
* 'database' => 'database_name',
|
||||
* 'username' => 'sql_username',
|
||||
* 'password' => 'sql_password',
|
||||
* 'host' => 'localhost',
|
||||
@ -355,14 +355,13 @@
|
||||
* security, or encryption benefits. In an environment where Drupal
|
||||
* is behind a reverse proxy, the real IP address of the client should
|
||||
* be determined such that the correct client IP address is available
|
||||
* to Drupal's logging, statistics, and access management systems. In
|
||||
* the most simple scenario, the proxy server will add an
|
||||
* X-Forwarded-For header to the request that contains the client IP
|
||||
* address. However, HTTP headers are vulnerable to spoofing, where a
|
||||
* malicious client could bypass restrictions by setting the
|
||||
* X-Forwarded-For header directly. Therefore, Drupal's proxy
|
||||
* configuration requires the IP addresses of all remote proxies to be
|
||||
* specified in $settings['reverse_proxy_addresses'] to work correctly.
|
||||
* to Drupal's logging and access management systems. In the most simple
|
||||
* scenario, the proxy server will add an X-Forwarded-For header to the request
|
||||
* that contains the client IP address. However, HTTP headers are vulnerable to
|
||||
* spoofing, where a malicious client could bypass restrictions by setting the
|
||||
* X-Forwarded-For header directly. Therefore, Drupal's proxy configuration
|
||||
* requires the IP addresses of all remote proxies to be specified in
|
||||
* $settings['reverse_proxy_addresses'] to work correctly.
|
||||
*
|
||||
* Enable this setting to get Drupal to determine the client IP from the
|
||||
* X-Forwarded-For header. If you are unsure about this setting, do not have a
|
||||
@ -808,6 +807,16 @@
|
||||
*/
|
||||
$settings['entity_update_backup'] = TRUE;
|
||||
|
||||
/**
|
||||
* State caching.
|
||||
*
|
||||
* State caching uses the cache collector pattern to cache all requested keys
|
||||
* from the state API in a single cache entry, which can greatly reduce the
|
||||
* amount of database queries. However, some sites may use state with a
|
||||
* lot of dynamic keys which could result in a very large cache.
|
||||
*/
|
||||
$settings['state_cache'] = TRUE;
|
||||
|
||||
/**
|
||||
* Node migration type.
|
||||
*
|
||||
|
||||
@ -1,7 +1,17 @@
|
||||
# Local development services.
|
||||
#
|
||||
# The development.services.yml file allows the developer to override
|
||||
# container parameters for debugging.
|
||||
#
|
||||
# To activate this feature, follow the instructions at the top of the
|
||||
# 'example.settings.local.php' file, which sits next to this file.
|
||||
#
|
||||
# Be aware that in Drupal's configuration system, all the files that
|
||||
# provide container definitions are merged using a shallow merge approach
|
||||
# within \Drupal\Core\DependencyInjection\YamlFileLoader.
|
||||
# This means that if you want to override any value of a parameter, the
|
||||
# whole parameter array needs to be copied from
|
||||
# sites/default/default.services.yml or from core/core.services.yml file.
|
||||
parameters:
|
||||
http.response.debug_cacheability_headers: true
|
||||
services:
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user