-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOC Update change log to reference updated migration task #8945
DOC Update change log to reference updated migration task #8945
Conversation
* File with hotfix applied (SS 4.2.3): `assets/[new-content-hash]/myfile.pdf` (redirects to `assets/myfile.pdf`) | ||
* File with full fix applied (SS 4.3.x) : `assets/myfile.pdf` (no redirect required) | ||
* Newly uploaded file with full fix applied: `assets/my-other-file.pdf` (no redirect required) | ||
* File with hotfix applied (SS 4.2.3): `assets/myfile.pdf` and `assets/[old-content-hash]/myfile.pdf` redirects to `assets/[new-content-hash]/myfile.pdf` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The point here was to describe the location of the file on the filesystem, not the different virtual or physical paths which get redirected. Those are two different pieces of info, you can't replace one with the other
|
||
#### Can I still choose legacy_filenames=true when starting new upgrades? | ||
|
||
Technically yes, but you need to be aware of the tradeoffs. | ||
Once the regression has been fixed, we don’t see the need for people to choose this option any more. | ||
Technically yes, but you need to be aware of the tradeoffs. Once the regression has been fixed, we don’t see the need |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If that second part is true, the first part is redundant (there are no tradeoffs?)
I'm merging this as-is since it's getting pretty crazy with different WIP PRs making changes to the changelog, e.g. #8924. |
* DOC Update change log to reference updated migration task * Update docs/en/04_Changelogs/4.4.0.md
Parent issue