This is usually due to a mismatch between core version and CCK version.
CCK 4.7 is for drupal 4.7, CCK HEAD is, well, semi-5.0 converted (but not working I think)
I replaced the date.module with an earlier version...and it seems to work okay now.
Anyone else looking at this...the reason I was getting the error was because I wasn't using the very latest 4.7 version of cck.module with the very latest 4.7 version of the date.module.
In other words, I was using the 4.7 version of the cck.module from a month or two ago with the latest date.module.
There's quite a lot of changes with both recently, so double check when downloading that the versions match and make a back up of your database before updating/installing the modules.
Actually, rather than going back to an earlier version of the date module I would suggesting moving to the current version of the content module. The latest versions of each should work together but it would be hard to know what combination of earlier versions will work right.
Yes, it would be nice if dependent modules could provide some messages to tell you that you don't have the right version of the related modules, but there's really no way to do that now.
Also, anytime you update any of the cck modules (or any other modules) you need to visit the update.php page to see if database updates are involved. Again, since the install and update features are still new, they don't really have any built-in methods for alerting you to the fact that you need to make an update, you just need to get in the habit of checking any time you install or update a module.
Comments
Comment #1
joshk commentedWhoops... needed to update my CCK.module. Still, would be nice if there were some kind of alert here for whenn I try to add new stuff.
Comment #2
dublin drupaller commentedsame problem here. using latest Drupal 4.7 version:
// $Id: date.module,v 1.13.2.9 2006/10/06 12:27:20What's the fix for that?
Dub
Comment #3
yched commentedThis is usually due to a mismatch between core version and CCK version.
CCK 4.7 is for drupal 4.7, CCK HEAD is, well, semi-5.0 converted (but not working I think)
Comment #4
dublin drupaller commentedthanks Yched,
I replaced the date.module with an earlier version...and it seems to work okay now.
Anyone else looking at this...the reason I was getting the error was because I wasn't using the very latest 4.7 version of cck.module with the very latest 4.7 version of the date.module.
In other words, I was using the 4.7 version of the cck.module from a month or two ago with the latest date.module.
There's quite a lot of changes with both recently, so double check when downloading that the versions match and make a back up of your database before updating/installing the modules.
hope that helps someone else..
Dub
Comment #5
karens commentedActually, rather than going back to an earlier version of the date module I would suggesting moving to the current version of the content module. The latest versions of each should work together but it would be hard to know what combination of earlier versions will work right.
Yes, it would be nice if dependent modules could provide some messages to tell you that you don't have the right version of the related modules, but there's really no way to do that now.
Also, anytime you update any of the cck modules (or any other modules) you need to visit the update.php page to see if database updates are involved. Again, since the install and update features are still new, they don't really have any built-in methods for alerting you to the fact that you need to make an update, you just need to get in the habit of checking any time you install or update a module.