After a D7 update and migration of fields, most of our problems with converted fields result from invalid or incompatible field settings. Field settings are stored in the
field_config_instance.data column in the database as serialized php objects.
How can I, for any given field instance, generate a fresh field configuration string, as if the field was just created in D7, while leaving the already stored field data intact?
My manual approach seems to work but is very cumbersome:
- create a new content type
- add an existing field to the new content type, generating new settings string
- search the new and old field in the database
- using sql: replacing the string in the data column of the old field (with the same name) with the new data content.
There must be a way to automate this a bit.