Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Thanks for the excellent module.
The instructions on the iCal import tab under Date Import/Export say, "Create a *new* CCK content type to import your events into." Apparently that is to be applied literally, in the sense that I can't get a pre-existing content type with a date field to show up in the "target type" drop down list.
I have a pretty standard calendar set up using date, calendar and views modules which works fine, but I just recently enabled the Date Copy module to try out ICS file import. I followed the instructions -- the event content type does have a Date type field field_date, with the "to" date set to optional, and time zone handling set to "date's time zone".
With a little experimentation I found that if I create a new date field in the event content type with the same settings, (and switch the view over to the new field) then my content type shows up in the target type drop down list. Of course then I am losing the data in the pre-existing date field. So apparently it doesn't so much want a new content type as that it wants a new *field*.
Is there any work around that would allow me to keep my data?
This is on drupal 5.9, PHP 5.2.4, MySQL 5.0, and all modules up to date as of today.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | DateFieldExport.tar_.gz | 1.2 KB | twowheeler |
Comments
Comment #1
KarenS CreditAttribution: KarenS commentedAny existing content type that has a date field should work, so if it didn't this is a bug. It may be too late now, but if you can still test this, try a couple things:
1) Can you post an export (using Content Copy) of the date field that showed up properly and the one that didn't.
2) After creating an export of the date field that didn't work, try editing that field's settings and saving it (save it even if you don't change anything) and see if it starts showing up.
Comment #2
KarenS CreditAttribution: KarenS commentedAlso try clearing cache_views (which is storing an array of available date fields). That may have been the original problem -- the cache was missing the field in question.
Comment #3
twowheeler CreditAttribution: twowheeler commentedOk thanks -- when I get a minute I will reload a copy from backup and see what happens.
Comment #4
twowheeler CreditAttribution: twowheeler commentedHere are the export results both ways. When using the pre-existing field, no amount of clearing cache, editing & saving, etc changes the outcome.
Pretty weird, huh?
Comment #5
KarenS CreditAttribution: KarenS commentedI think this might be the CCK bug at #294726: _content_type_info() does not reset (on content type changes), so marking this a duplicate.