Hey,
Trying to migrate a project from umbraco 8 to 13, that uses a lot of DTGE.
I already was able to create my project v8, and import that v8 into my clean solution of Umbraco13.
Everything migrated but the pages don’t seem to be working, at least the preview. I think the problem is because the original website was using DTGE and from what i’ve read, is not supported on Umbraco 13 anymore.
Take a look at Jumoo/uSyncMigrations: Rough and ready migration code. for migrating DTGE over to BlockGrid (there are a few shortcomings depending on your use.. cell settings in DTGE don’t exist as settings on the equivalent areas in blockgrid for instance)
Hey, thanks for the response. I’ve used that git for the initial migration aand I’ve noticed that there are a DTGE MIgrator in the folder MyMigrations, but im kinda confused on how to use it.
In my umbraco 8 i installed the Nugget of the Sync, and made a folder called V8, and then i did the same installation in the project of umbraco 13, and i point it to the folder of the V8, but i think it only migrated nested content and some other type, the DTGE it didn’t do anything.
As far as I remember, using the convert grid to blockgrid, should convert your DTGE elements from your legacy grid without doing anything else.
As there is a core.. DTGE Migrator for use in blockgrid..
PS you do need to rebuild your legacy grid DTGE partials as BlockGrid Block renders… perhaps that’s your missing step?
Alternatively, you could fork the source code and upgrade it to work with v13. That’s what we did on one project as content migration wasn’t viable.
IIRC it’s just a case of updating dependencies and a few namespaces/obsolete methods.
Was quite straight forward.
I think the latest Usync.Migrations does work with v13, for an in place conversion?
Or do you mean fork DTGE, as the legacy grid isn’t removed until v14? Just to mention we did have some issues with that approach with sites locking up which logs seemed to suggest was a reflection issue in DTGE.. though am trying to remember a while back now.
Interested to know why content migration wasn’t possible… Usync.Migrations is quite easy to extend with custom migrators/override existing migrators ??
