tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-09-29 20:59:23 +02:00
Code Issues Projects Releases Wiki Activity

DOCS Shortcode upgrade section

Browse Source
This commit is contained in:
Ingo Schommer 2019-06-18 09:20:38 +12:00 committed by GitHub
parent bb5b610636
commit 49c04bf9cc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/en/04_Changelogs/4.4.0.md
View File

@ -70,7 +70,8 @@ We have ironed out some edge cases since then:
* [Hash-less public asset URLs](#hash-less)
* [Legacy thumbnail locations](#legacy-thumb)
* [HTMLText short code migration](/Upgrading/Upgrading_projec#tagtoshortcode)
* [Remove artifacts from "secureassets" module](#secureassets)
* [HTMLText short code migration](#tagtoshortcode)
You can opt-in to performing these migration tasks on your already upgraded SilverStripe 4.x project.
@ -148,6 +149,18 @@ The task will auto-detect if you have any custom `.htaccess` files in folders, a
Note that you'll need to run your own migration scripts if you've used the module
with IIS and `web.config` files instead.
### Optional migration tasks: HTMLText Shortcode Migration {#tagtoshortcode}
The shortcode format in SilverStripe 4 has changed from SilverStripe 3. This means that when CMS editors try to edit existing content and alter image or file links, the reference to the file will not work.
After running the file migration, you can run the short code migration task to update your existing HTML content in your database:
```bash
vendor/bin/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.
### Hash-less Public Asset URLs FAQ {#hashless-faq}
#### How are files named and renamed?