Migrating Assets in 5.2

Development Pipeline & Plugins
, , , , ,
1

Does anybody used the migrate feature lately on 5.2? It seems you can’t migrate them like the previous engine where you can put the migrated assets to any folder (outside Content) instead they insists you to migrate them to the another project instead.

Someone recommended to copy paste them manually but I think it’s not effecient because you need to sort it out the un-related folder of the assets, which is a handful.

2

Yes on 5.2.1, works fine at least to a content folder. You could create a new plugin and migrate there, this usually makes the most sense.

Things are going to break that way.

3

I wonder though why they’ve changed these, because previously the migrate features works fine and easy to use.

1 Like