Drupal from 10.6.17 to 11.4.7

This commit is contained in:
2026-09-26 01:10:59 +02:00
parent 89d68ac548
commit 62c814d57d
83 changed files with 4122 additions and 1745 deletions
+46 -52
View File
@@ -67,10 +67,10 @@
* during the same request.
*
* One example of the simplest connection array is shown below. To use the
* sample settings, copy and uncomment the code below between the @code and
* @endcode lines and paste it after the $databases declaration. You will need
* to replace the database username and password and possibly the host and port
* with the appropriate credentials for your database system.
* sample settings, copy and uncomment the code below and paste it after the
* $databases declaration. You will need to replace the database username and
* password and possibly the host and port with the appropriate credentials for
* your database system.
*
* The next section describes how to customize the $databases array for more
* specific needs.
@@ -144,7 +144,7 @@ $databases = [];
* in deadlocks, the other two options are 'READ UNCOMMITTED' and 'SERIALIZABLE'.
* They are available but not supported; use them at your own risk. For more
* info:
* https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html
* https://dev.mysql.com/doc/refman/8.0/en/innodb-transaction-isolation-levels.html
*
* On your settings.php, change the isolation level:
* @code
@@ -312,7 +312,7 @@ $settings['hash_salt'] = '';
$settings['update_free_access'] = FALSE;
/**
* Fallback to HTTP for Update Manager and for fetching security advisories.
* Fallback to HTTP for Update Status and for fetching security advisories.
*
* If your site fails to connect to updates.drupal.org over HTTPS (either when
* fetching data on available updates, or when fetching the feed of critical
@@ -475,30 +475,6 @@ $settings['update_free_access'] = FALSE;
*/
# $settings['class_loader_auto_detect'] = FALSE;
/**
* Authorized file system operations:
*
* The Update Manager module included with Drupal provides a mechanism for
* site administrators to securely install missing updates for the site
* directly through the web user interface. On securely-configured servers,
* the Update manager will require the administrator to provide SSH or FTP
* credentials before allowing the installation to proceed; this allows the
* site to update the new files as the user who owns all the Drupal files,
* instead of as the user the webserver is running as. On servers where the
* webserver user is itself the owner of the Drupal files, the administrator
* will not be prompted for SSH or FTP credentials (note that these server
* setups are common on shared hosting, but are inherently insecure).
*
* Some sites might wish to disable the above functionality, and only update
* the code directly via SSH or FTP themselves. This setting completely
* disables all functionality related to these authorized file operations.
*
* @see https://www.drupal.org/node/244924
*
* Remove the leading hash signs to disable.
*/
# $settings['allow_authorize_operations'] = FALSE;
/**
* Default mode for directories and files written by Drupal.
*
@@ -516,6 +492,15 @@ $settings['update_free_access'] = FALSE;
*/
# $settings['file_assets_path'] = 'sites/default/files';
/**
* Asset aggregate garbage collection threshold.
*
* During cache clears, JavaScript and CSS aggregates older than this threshold
* will be deleted. Set this to 0 to immediately delete all files, e.g. during
* development.
*/
# $settings['aggregate_gc_threshold'] = 86400 * 45;
/**
* Public file base URL:
*
@@ -625,6 +610,18 @@ $settings['update_free_access'] = FALSE;
*/
# $settings['file_temp_path'] = '/tmp';
/**
* Automatically create an Apache HTTP .htaccess file in writable directories.
*
* This setting can be disabled if you are not using Apache HTTP server, or if
* you have a web server configuration that protects the various writable file
* directories.
*
* @see \Drupal\Component\FileSecurity\FileSecurity::writeHtaccess()
* @see https://www.drupal.org/docs/administering-a-drupal-site/security-in-drupal/securing-file-permissions-and-ownership
*/
# $settings['auto_create_htaccess'] = FALSE;
/**
* Session write interval:
*
@@ -647,7 +644,7 @@ $settings['update_free_access'] = FALSE;
*/
# $settings['locale_custom_strings_en'][''] = [
# 'Home' => 'Front page',
# '@count min' => '@count minutes',
# 'Last run @time ago' => 'Last run was done @time ago',
# ];
/**
@@ -710,6 +707,24 @@ $settings['update_free_access'] = FALSE;
# $config['system.site']['name'] = 'My Drupal site';
# $config['user.settings']['anonymous'] = 'Visitor';
/**
* Enable HTML5 form validation.
*
* Drupal 12 will disable HTML5 form validation by default due to issues with
* usability and accessibility. Setting this to TRUE will allow user agents to
* continue performing client-side HTML5 validation. This prevents Drupal's
* Form API (FAPI) validation from executing, so FAPI validation error messages
* may not be displayed including those for required elements.
*
* Setting this to FALSE will cause HTML5 validation to be disabled on all
* forms. Only Drupal's server-side validation will be executed.
*
* This setting will be removed in Drupal 13.
*
* @see https://www.drupal.org/node/3537128
*/
# $settings['enable_html5_validation'] = TRUE;
/**
* Load services definition file.
*/
@@ -724,17 +739,6 @@ $settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml';
*/
# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container';
/**
* Override the default yaml parser class.
*
* Provide a fully qualified class name here if you would like to provide an
* alternate implementation YAML parser. The class must implement the
* \Drupal\Component\Serialization\SerializationInterface interface.
*
* This setting is deprecated in Drupal 10.3 and removed in Drupal 11.
*/
# $settings['yaml_parser_class'] = NULL;
/**
* Trusted host configuration.
*
@@ -809,16 +813,6 @@ $settings['entity_update_batch_size'] = 50;
*/
$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.
*