Skip to content
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

Grid content migration doesn't respect legacy rows #282

Open
ben-umble opened this issue Sep 26, 2024 · 0 comments
Open

Grid content migration doesn't respect legacy rows #282

ben-umble opened this issue Sep 26, 2024 · 0 comments

Comments

@ben-umble
Copy link

Hi,

I'm attempting a migration to Umbraco 13 from Umbraco 8, a site which uses the legacy grid extensively throughout. I've attempted a migration using uSync.Migrations which has got me quite a long way down the line. I do however have an issue with grid to block grid.

The problem is that on the legacy grid we have rows with settings, then we have areas with settings. Inside the area we mostly have one editor and this migrates pretty well. I do however have a few instances where we have two editors in a row but when the migration happens, both editors are put at the same level.

It may be easier to show you in images:

This is the legacy grid, you an see here we have an RTE and a form picker.

image

When it's migrated, the RTE and form picker do not have a surrounding row/block.

image

The migration does take into account multiple columns but in my use case I need to apply the settings at row/block level.

It's actually the case that I'd be able to put all editors in a row/block which would mimic the old layout.

Are there any settings or tweaks I can make to ensure that a surrounding row/block is always used?

Thanks,

Ben

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant