on a 'content type' created with the Date field,
at
admin/content/types/event/display
-changing date format i.e from 'default' (default is 'short') to 'Long'
gets
warning: Invalid argument supplied for foreach() in /home/movimien/public_html/sitio/sites/all/modules/cck/content_admin.inc on line 418.
-changing date format i.e from 'Long' to 'default' (default is 'short')
gets

warning: Invalid argument supplied for foreach() in /home/movimien/public_html/sitio/sites/all/modules/cck/content_admin.inc on line 418.
warning: Invalid argument supplied for foreach() in /home/movimien/public_html/sitio/sites/all/modules/cck/content_admin.inc on line 418.

warnings point the CCK but yet the warnings exist when the date format changes, I am not sure i should cross post this bug to CCK too if its related to that

content tupe Date field specs:
Widget: * Select List
Data settings: Required
To date: Optional

Comments

karens’s picture

karens commented
Status: Active » Fixed

There was a database update and it sounds like you did not run it. Go to http://www.example.com/update.php and run the update.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)
sonicthoughts’s picture

sonicthoughts commented
Status: Closed (fixed) » Active

I have the latest version of the date and calendar module, ran the update code and still get this error.

iaminawe’s picture

iaminawe commented

I receive this too after updating the date and calendar modules... I unchecked the modules and the error still persists.
I have run the update.php and it completed with no errors.

mavimo’s picture

mavimo commented

I've the same problem, fresh installation of Drupal (5.9) and only cck+date 2.0-rc1

karens’s picture

karens commented
Status: Active » Closed (won't fix)

@mavimo - if you are indeed using date 2.0 rc-1 you are posting to the wrong place because this is an issue about version 1 of the Date module. And version 5.2 rc1 is WAY out of date, we're up to rc 5 or 6. Unless you're using the version for Drupal 6, which has a new 6.2 rc1, which is also the wrong version for this issue. If you're using Drupal 5, I recommend the LATEST 5.2 version. If you're using Drupal 6, this is totally the wrong place to post your comment and you won't get any meaningful feedback.

To the others, I'm no longer updating the 5.1 version, I'm focusing all my effort at getting version 2 to a final release ASAP so it can become the official supported version. All new features, bug fixes, etc. are going into 5.2 (for Drupal 5) and 6.2 (for Drupal 6). If you have a working installation of 5.1, wait for a final release of 5.2. If you are having problems in 5.1, try the 5.2 version and help me get it polished.