CLI utilities for resaving entry types and fields

[sweetroll]

After migrating a site to Craft 5 I've noticed new attributes added to the project config only after resaving an entry type or field and not by running the rebuild utility. Some of these many minor things like cardView, viewMode and availableTransforms but in a number of cases I had the title field missing that was only fixed when the entry type was resaved.

Our migration process now involves having to manually resave all fields and entry types via the CMS which can be hundreds of items to ensure all settings are correctly committed. Is it feasible to create utilities to save these via the CLI or is there an alternative?

[brandonkelly]

The two things I’m seeing are:

• Field layout element configs get new dateAdded values on each rebuild, for field layouts that hadn’t been explicitly saved since Craft 5.3.0.
• User and address field layouts get recreated with new UUIDs on each rebuild, if they hadn’t even been explicitly saved.

The first one was a known issue that happens as a side effect of #15400, however I thought of a way to prevent it from happening going forward. And I was able to resolve the second issue by completely omitting the user and address field layouts from the built project config data, unless the field layouts have been explicitly saved. (b1066a5)

However I’m not able to reproduce any field properties changing between rebuilds. If you can send your Craft 5 database and Composer files over to support@craftcms.com (before having manually reaved any fields/entry types), I can look into it with those files.

[brandonkelly]

Craft 5.7.0 is out with the fix for dateAdded.

[sweetroll]

Hey Brandon,

Nearly 12 months on this has popped up again after another migration. This time, entries that had title fields in Craft 3 (3.9.13) have lost them in Craft 5 (5.8.23) The project config shows hasTitleField: true but no title field listed in the fieldLayouts. Rebuilding the project config doesn't change anything but resaving the entry type in the CMS adds the field to the PC and fixes the problem.

Adding a CLI command for bulk resaving entry types/section/fields would fix this issue for us but there maybe another issue you can see. Let me know if its still worthwhile to send you something. Cheers.

[brandonkelly]

@sweetroll If you can send your Craft 4 database backup and Craft 5 Composer files into support@craftcms.com, we can look into it from there.

[jamesmacwhite]

I would say there is potential value in having CLI commands to resave entry types. If new schema is added on fields or similar, this doesn't always get updated unless a migration or resave of the entry type/field occurs. Depending on what it is, it would usually be handled I guess, but keeping the schema in sync seems like the best thing across any entry type.