Replies: 1 comment 3 replies
-
|
The two things I’m seeing are:
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. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
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?
Beta Was this translation helpful? Give feedback.
All reactions