Upgrading to Craft 5 - field merge woes

[darylknight]

I'm doing an upgrade of Craft 4 to Craft 5 on a very old, very large site.

The docs on upgrading advise that you can run the Craft 4 > 5 upgrade, deploy, then merge fields later, then merge entry types. However I've generally found this isn't the case because I nearly always find that in Craft 5, I've now got lots of Entry Types that previously used to have the same handle (which was fine in Craft 4), but now because all the Entry Types are dumped in one section and handles are unique, Craft has renamed them to have sequential numbers like entryTypeHandle2, entryTypeHandle3 etc. This breaks my templates because I dynamically include the matrix block using the block type's handle as the filename, like this:

{% for block in entry.contentMatrix.all() %}
    {% include '_includes/content/' ~ block.type %}
{% endfor %}

So I have a bunch of content blocks that break because their handles changed, so I'm doing all the merging before deploying. However, I just merged two asset fields, and got this notice afterwards:

⚠️ Be sure to run this command on other environments before deploying these changes:
   php craft resave/all --with-fields=image4,image

Which I can't do, because --with-fields doesn't exist in Craft 4, and I now can't run this command on staging/production before deploying. What do I do?

[brandonkelly]

Thanks for pointing that out!

I’ve been meaning to make it possible to override entry type names and handles on a per-usage basis (#14779), and this was a good nudge. So that’s now coming in Craft 5.6 🎉

For Craft sites that upgrade from Craft 4 to 5.6+, all sections and Matrix fields will continue have the same entry type handles as they did in Craft 4. (Sites that have already upgraded will need to add the name/handle overrides manually.)

[brandonkelly]

Craft 5.6.0 is out now 🚀