Merge pull request #770 from chapter-three/upgrade/drupal-9.4.3

Upgrade from 9.4.2 to 9.4.3

composer-manifest.yaml

@@ -45,10 +45,10 @@ packages:
     drupal/config_filter: 1.9.0
     drupal/config_ignore: 2.3.0
     drupal/config_split: 1.8.0
-    drupal/core: 9.4.2
+    drupal/core: 9.4.3
     drupal/core-composer-scaffold: 9.4.1
     drupal/core-project-message: 9.4.1
-    drupal/core-recommended: 9.4.2
+    drupal/core-recommended: 9.4.3
     drupal/core-vendor-hardening: 9.4.1
     drupal/crop: 2.2.0
     drupal/csv_serialization: 2.1.0

web/sites/default/default.settings.php

@@ -490,6 +490,29 @@
  */
 # $settings['file_public_path'] = 'sites/default/files';
 
+/**
+ * Additional public file schemes:
+ *
+ * Public schemes are URI schemes that allow download access to all users for
+ * all files within that scheme.
+ *
+ * The "public" scheme is always public, and the "private" scheme is always
+ * private, but other schemes, such as "https", "s3", "example", or others,
+ * can be either public or private depending on the site. By default, they're
+ * private, and access to individual files is controlled via
+ * hook_file_download().
+ *
+ * Typically, if a scheme should be public, a module makes it public by
+ * implementing hook_file_download(), and granting access to all users for all
+ * files. This could be either the same module that provides the stream wrapper
+ * for the scheme, or a different module that decides to make the scheme
+ * public. However, in cases where a site needs to make a scheme public, but
+ * is unable to add code in a module to do so, the scheme may be added to this
+ * variable, the result of which is that system_file_download() grants public
+ * access to all files within that scheme.
+ */
+# $settings['file_additional_public_schemes'] = ['example'];
+
 /**
  * Private file path:
  *