BUG Fix documentation for permissions

silverstripe · Oct 18, 2017 · 0b3363d · 0b3363d
1 parent 3e9dc5c
commit 0b3363d
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/docs/en/00_Getting_Started/01_Installation/05_Common_Problems.md b/docs/en/00_Getting_Started/01_Installation/05_Common_Problems.md
@@ -90,9 +90,10 @@ If you are running on a server instance where users other than the webserver use
 read / write access to files in the assets folder, then you will need to adjust the
 permissions of the filesystem to a more permissive setting.
 
-By default private files and `.htaccess` are written with permission `0600`.
+By default private files and `.htaccess` are written with permission `0644`.
 You could enable other users to access these files with the below config.
-Note: Please adjust the values below to those appropriate for your server configuration:
+Note: Please adjust the values below to those appropriate for your server configuration.
+You may require `0666` for combined files generated during requests where they are cleared or refreshed only during a flush.
 
 *mysite/_config/assetperms.yml*
 

diff --git a/docs/en/04_Changelogs/4.0.0.md b/docs/en/04_Changelogs/4.0.0.md
@@ -2254,6 +2254,7 @@ The below methods have been added or had their functionality updated to `DBDate`
 * `AssetControlExtension` is applied by default to all DataObjects, in order to support the management
   of linked assets and file protection.
 * `ProtectedFileController` class is used to serve up protected assets.
+* `AssetAdaptor` has a new config `default_server` which helps tell the code which server type to use if no matching type was found by scanning the server software - defaults to `apache`
 
 #### <a name="overview-filesystem-removed"></a>Filesystem removed API