tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-06-16 09:41:38 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #9202 from open-sausages/pulls/4/document-ss32-variant-migration

Browse Source 
DOC Explain how to mgirate SS3.2 variants
This commit is contained in:
Andre Kiste 2019-09-11 11:47:28 +12:00 committed by GitHub
commit 75cd9dc944
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -176,7 +176,19 @@ After running the file migration, you can run the short code migration task to u
sake dev/tasks/TagsToShortcode
```
This will rewrite your existing shortcodes to the newer format SilverStripe 4 expects as well as convert `img` and `a` tags to use shortcodes..
This will rewrite your existing shortcodes to the newer format SilverStripe 4 expects as well as convert `img` and `a` tags to use shortcodes.
### Migrating from SilverStripe 3.2 (or below) to SilverStripe 4.4
The format for image variants was changed in SilverStripe 3.3. In SilverStripe 3.2 and below variants would be included in the file name with a dash:
* `Uploads/_resampled/FitWzQwLDMwXQ-image.jpg` in SilverStripe 3.2 and below
* `Uploads/_resampled/FitWzQwLDMwXQ/image.jpg` in SilverStripe 3.3 and above
The file migration task didn't account for this nuance until the SilverStripe 4.4.4 release. If you ran the file migration task using a prior version, your SilverStripe 3.2 thumbnails might not have been migrated, or their paths might have been appended as variants. e.g.: `FitWzQwLDMwXQ-image__Uploads__resampled.jpg`
Those variants will need to be regenerated. Thumbnails generated through templates or code will automatically be regenerated on the next uncached request to SilverStripe. Thumbnails embedded in HTML fields will be regenerated when the page is republished. Variants that were improperly renamed must be removed manually.
If you are running SilverStripe 4.4.4 or greater, SilverStripe 3.2 variants will be migrated normally.
## Migrating from SilverStripe 4.3 or below to SilverStripe 4.4 or above