From c165561580312114d6a827d71fed1fb72bd8815c Mon Sep 17 00:00:00 2001 From: Maxime Rainville Date: Mon, 9 Sep 2019 09:06:40 +1200 Subject: [PATCH] Fix typos Co-Authored-By: Robbie Averill --- docs/en/02_Developer_Guides/14_Files/05_File_Migration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/02_Developer_Guides/14_Files/05_File_Migration.md b/docs/en/02_Developer_Guides/14_Files/05_File_Migration.md index 891198b78..63f9097ab 100644 --- a/docs/en/02_Developer_Guides/14_Files/05_File_Migration.md +++ b/docs/en/02_Developer_Guides/14_Files/05_File_Migration.md @@ -184,9 +184,9 @@ The format for image variants was changed in SilverStripe 3.3. In SilverStripe 3 * `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 path might have been appended as variants. e.g.: `FitWzQwLDMwXQ-image__Uploads__resampled.jpg` +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 regenarated. 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 got improperly renamed can be removed manually. +Those variants will need to be regenarated. 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.