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 #9458 from creative-commoners/pulls/4/doc-versioned-file-migration

Browse Source 
DOC CMS 3.x file migration section about versioned files
This commit is contained in:
Steve Boyd 2020-04-14 11:31:43 +12:00 committed by GitHub
commit 0f7fd35926
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/en/02_Developer_Guides/14_Files/05_File_Migration.md
View File

@ -23,6 +23,25 @@ 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.
### If you were using the versionedfiles on your 3.x site
If you have had [versionedfiles](https://github.com/symbiote/silverstripe-versionedfiles) module installed, it is very important to run
an extra task that would clean up the `_versions` folders. Otherwise, files in those folders may be left exposed to public access
through your web server via guessable URLs. This includes all the unpublished versions of your files.
The task for the job is `VersionedFilesMigrationTask`, and you may run it as follows:
`$ vendor/bin/sake dev/tasks/migrate-versionedfiles strategy=[delete|protect]`
Before you run it, it is important to choose an appropriate strategy that suits your project best.
- `delete` (default) - delete all `_versions` folders
- `protect` - create a protective `.htaccess` file in every `_versions` folder (Apache specific)
If you choose `delete`, it may be wise to take a snapshot of your `public/assets` folder.
Shall you consider `protect` as the method, please beware that it may not always work, depending on your server setup.
In that case it is important to make sure your web server is Apache and that it allows `.htaccess` for all subfolders.
## Automatic migration ## Automatic migration
Migration can be invoked by either this task, or can be configured to automatically run during dev build Migration can be invoked by either this task, or can be configured to automatically run during dev build