First draft of the Macro migration inspiration tutorial #6944
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
15/umbraco-cms/tutorials/inspiration/migrating-macros/block-backoffice.md
Outdated
Show resolved
Hide resolved
15/umbraco-cms/tutorials/inspiration/migrating-macros/tiptap-blocks.md
Outdated
Show resolved
Hide resolved
15/umbraco-cms/tutorials/inspiration/migrating-macros/rte-tipttap.png
Outdated
Show resolved
Hide resolved
| --- | ||
|
|
||
| # Introduction | ||
| As with many things in Umbraco, there are a multitude of ways on how to migrate away from macros and use the blocks in the RTE instead. In this article we will be showcasing a solution that lets you scan and then fix each macro one by one (or in batch). This solution will most likely not be used in a production setup, but we hope it canserve as an inspiration on how you can build your own solution specific your current setup. At the end of the article we will discuss a few other ways of running a larger migration. |
There was a problem hiding this comment.
Why shouldn't this be used in a production setup? If anything, we should clarify the potential issues or risks when doing so or otherwise suggest a way to test this on development/staging and then transfer the migrated content to the production/live environment (e.g. using Deploy).
There was a problem hiding this comment.
The clarification is in the last sentence. I will see if I can reword things.
15/umbraco-cms/tutorials/inspiration/migrating-macros/migrating-macros.md
Show resolved
Hide resolved
15/umbraco-cms/tutorials/inspiration/migrating-macros/migrating-macros.md
Outdated
Show resolved
Hide resolved
15/umbraco-cms/tutorials/inspiration/migrating-macros/migrating-macros.md
Outdated
Show resolved
Hide resolved
15/umbraco-cms/tutorials/inspiration/migrating-macros/migrating-macros.md
Show resolved
Hide resolved
15/umbraco-cms/tutorials/inspiration/migrating-macros/migrating-macros.md
Outdated
Show resolved
Hide resolved
15/umbraco-cms/tutorials/inspiration/migrating-macros/migrating-macros.md
Outdated
Show resolved
Hide resolved
Migaroez
changed the title
|
|
||
| In this article we will be doing a one on one conversion from macro to block with each paramater matching the same named properties on an element document type. We are also keeping it relatively simple and are using pure text as values. If your migration deals with more complex types, we advice you to create an instance of the new data format and compare the old value against the new as there might have been more differences between the paramater type on the macro and the propertyEditor/datatype on the element document type. | ||
|
|
||
| Because most people will be dealing with this kind of migrations when they move between LTS version from 13 to 15, we chose to do just that in this article. More precisly from 13.7.2 to 15.2.3 |
There was a problem hiding this comment.
Could we mention something in this line:
"Notice this example would also be compatible if you where to migrate from 13 to 17".
In this way a future read do not think they have to go to the v.15 version, but they need to understand that they can go from LTS to LTS. :-)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What did you add/update/change?
Type of suggestion
Product & version (if relevant)
CMS v15
Deadline (if relevant)
When should the content be published?