tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #7329 from open-sausages/pulls/4.0/file-upgrade-docs

Browse Source 
DOCS Upgrading file docs
This commit is contained in:
Chris Joe 2017-09-01 13:39:18 +12:00 committed by GitHub
commit 9fb5a2a693
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/en/04_Changelogs/4.0.0.md
View File

@ -817,7 +817,7 @@ large amounts of memory and run for an extended time.
```yml ```yml
File: SilverStripe\Assets\File:
migrate_legacy_file: true migrate_legacy_file: true
``` ```
@ -828,11 +828,21 @@ that previously visible assets remain visible to the public site.
If additional security or visibility rules should be applied to File dataobjects, then If additional security or visibility rules should be applied to File dataobjects, then
make sure to correctly extend `canView` via extensions. make sure to correctly extend `canView` via extensions.
Note that any File dataobject which is not in the `File.allowed_extensions` config will be deleted
from the database during migration. Any invalid file on the filesystem will not be deleted,
but will no longer be attached to a dataobject anymore, and should be cleaned up manually.
To disable this, set the following config:
```yaml
SilverStripe\Assets\FileMigrationHelper:
delete_invalid_files: false
```
Note that pre-existing security solutions for 3.x (such as Note that pre-existing security solutions for 3.x (such as
[secure assets module](https://github.com/silverstripe/silverstripe-secureassets)) [secure assets module](https://github.com/silverstripe/silverstripe-secureassets))
are incompatible with core file security. are incompatible with core file security.
#### Upgrade code which acts on `Image` #### Upgrade code which acts on `Image`
As all image-specific manipulations has been refactored from `Image` into an `ImageManipulations` trait, which As all image-specific manipulations has been refactored from `Image` into an `ImageManipulations` trait, which