[Breaking change]: Grid Layout (Umbraco.Grid) to be deprecated from version 11 and removed in version 14

[lassefredslund]

Description

The old Grid Layout introduced in version 7 will not be implemented with the new backoffice that is currently expected to be introduced in version 14.

Note: Grid Layout will not be removed from existing projects in Heartcore.

Version

Umbraco 14

Previous behavior

Grid Layout could be used to present a grid for the content editor.

New behavior

Block Grid Editor can be used to present a grid for the content editor.

Type of breaking change

• Binary incompatible: Existing binaries may encounter a breaking change in behavior, such as failure to load/execute or different run-time behavior.
• Source incompatible: Source code may encounter a breaking change in behavior when targeting the new runtime/component/SDK, such as compile errors or different run-time behavior.

Reason for change

With the new backoffice we want to streamline both the developer- and editor experience while we invest our effort in property editors that we foresee usable on a long term.

Recommended action

Start using Block Grid Editor.

Affected APIs

N/A

[UmbracoReynolds]

This is more of a uSync question, but because that is the most official tool for migrating away from gridlayout I am going to post here. When I migrate gridlayout to blockgrid layout, how do I get the content to transfer as well?

[marcemarc]

@UmbracoReynolds lots of information here... https://github.com/Jumoo/uSyncMigrations but essentially you create a migration pack from your v7 site. And this uses uSync Content edition to export onto disk xml files for each content and media item... Along with uSyncs normal files for Doctype definitions... And with your grid.editors.config.js file...

You copy this pack of files to your vanilla new Umbraco site and run the first step, which is conversion... This runs the files through a set of migrators, which turn the XML for the content and media into a format for the latest edition of uSync. Transforming known legacy property editors into their modern equivalents, you can write your own migrators too...

Once converted the next step is to import the settings, this brings across all the DocTypes and DataTypes etc then third step is to import content and media across...

In the case of old grid to shiny new block grid... It will depend on whether you have created custom grid editors or not as to how successful this will be without customisation... If you are using DocTypeGridEditor to define your custom grid editors, then the existing uSync migrator will create new Element Types for use in block grid to match the DTGE definitions, and migrate everything across.. Content and Media wise...it is surprisingly successful, that said new block list can do so much more than old grid, so it can feel odd to see layout blocks called 3-3-3...

The best way to understand if it will help for your site is to give it a go in a development environment.

Also you can run Migrations from other versions other than V7, for selected editors etc, but in answer to your question it is uSync content edition that moves the content!

[UmbracoReynolds]

Thank you for the quick and helpful reply!

What is a step-by-step sequence of events to do an in-place migration (or a migration from v10 to v12) for content and data types?
e.g. Do we need to install Usync + Usync Migrations?
Then run Usync Migrations?
Then import the migration?

We currently have Usync and Umbraco version 10.7.1 and Usync Migrations version 4.0.0 installed.

Currently when I do the migration, I get an error that says: "An item with the same key has already been added. Key: "

Situation:
We are trying to migrate from Umbraco v10 to Umbraco v10 (v10 to v12 would be fine if easier than v10 to v10) in order to move away from NestedContent and GridLayout to the new supported datatypes. Our dilemma is none of the content that was within GridLayout is visible within BlockGridLayout after migrating.

Possible errors:

• It seems as if maybe the newest uSync.migrations is only setup to allow migrations from a v7 or v8 project to a newer version. I am trying to be optimistic with their wording and tried migrating under the assumption it would work. Is it possible to migrate from v10 to v10 or v10 to v12?
• I didn't delete all the content manually because I assumed importing the migration would automatically replace. The error message is firing "An item with the same key has already been added. Key: " though so does that mean we need to wipe the content manually before importing?