Hi,

When you create a CCK date field and add it to multiple content types, the table containing the data gets altered without any warning when you change the widget type.

We hit this because we created a date field that was used in 3 different content types (so we could show them in the same view). One content type had a widget of "Text Field with Date Popup Calendar" and the others "Text Field with Date Popup and Repeat Options". Whenever you edit the CCK field options, even just the ones local to that content type, it would alter the table to match whatever widget type was listed for that type. So if it happened to be the one without repeat options, just changing the date range would delete ALL repeating rules in the database, with no warning!

So short term I think there needs to be a warning to make sure the date field uses the same widget types across all content types. But I think the "correct" solution is making a repeating field a different type, rather than just a different widget.

The workaround is to simply make sure the widget type is the same across all content types that share the field.

Comments

KarenS’s picture

KarenS CreditAttribution: KarenS commented
Title: CCK Widget type deletes date repeat rrule column in database without warning » Repeating date should be a different date type

Yeah, it probably should be a different type of date field. But that requires some refactoring of the code and a hairy update to get current dates transformed into the new type. Plus you will have to have *three* types -- a repeating iso date, a repeating timestamp date, and a repeating datetime date.

I'm open for patches.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Component: Date CCK Field » Code
Issue summary: View changes
Status: Active » Closed (won't fix)

Unfortunately the Drupal 6 version of the Date module is no longer supported. That said, we appreciate that you took time to work on this issue. Should this request still be relevant for Drupal 7 please feel free to reopen it. Thank you.