Hi Sebastien & Bertrand
I think there might be a bug here. Sebastien said "the settings are different per content type" but I'm not seeing this behavior.
When attaching a field to a part and then seeing its settings in the type editor certainly infers that it is expected that field settings will be different per
type, but when I add a field to a part and change the settings from the type editor page those settings are persisted between all types that have the part attached.
Steps to reproduce:
- Add an Orchard Date/Time field to the Title Part.
- Edit the Page content type and change the Display Option setting to Date Only.
- Now edit the Blog Post content type, note that the Display Option is Date Only. Change it to Time Only.
- Go back to the Page content type and notice that it is Time Only.
The settings appear to be saved in only one record in the [Settings_ContentPartFieldDefinitionRecord] table, there isn't any pointer to which type the settings are applied to, which seems to be why the same settings are used for each instance of the
<settings DisplayName="Date Time" DateTimeFieldSettings.Display="TimeOnly" DateTimeFieldSettings.Required="False" />
Is this behavior expected, or as Sebastien says should the settings be unique for each type?