when i try to apply the updtate i have this message...

* user warning: Table 'arrimagemaster.node_field_date_data' doesn't exist query: ALTER TABLE node_field_date_data ADD COLUMN nid int(10) NOT NULL DEFAULT 0 in /home.10/arrimage/www/includes/database.mysql.inc on line 120.
* user warning: Table 'amaster.node_field_date_data' doesn't exist query: SELECT COUNT(*) FROM node_field_date_data in /home.10/arrimage/www/includes/database.mysql.inc on line 120.
* user warning: Table 'arrimagemaster.node_field_date_data' doesn't exist query: SELECT nr.nid, nfdd.vid, nfdd.field_name, nfdd.delta FROM node_field_date_data nfdd LEFT JOIN node_revisions nr ON nr.vid = nfdd.vid LIMIT 0, 20 in /home.10/arrimage/www/includes/database.mysql.inc on line 120.
* user warning: Unknown table 'node_field_date_data' query: DROP TABLE node_field_date_data in /home.10/arrimage/www/includes/database.mysql.inc on line 120.

any suggestion ?

Comments

KarenS’s picture

Try going to the field settings screen for the field in question and see if the field is missing anything or if it seems to work.

I've run into a few things in the install file that throw what seem to be errors, but everything works OK afterward. I can't quite get the problem run down.

KarenS’s picture

Another possibility -- I ran into this on another test bed. The content module was doing some updates too, so the error messages might be from that update rather than the date module update. Did you by any chance check whether any other module was selected for update?

KarenS’s picture

I just committed some changes to the date.install that will fix some update problems. However, I'm not convinced these messages came from date.install though, even though the message is about a date field. It looks a bit like there was some corrupt data (a field that no longer exists) which would have nothing to do with this module.

Anyway, if you have the ability to go back to where you were before and try this again, re-load your data and make sure the field in question is OK before the install, then try another install with the updated file (making sure no other updates are selected at the same time).

Either way, do things seem to work OK once you get past the install?

KarenS’s picture

See comments in http://drupal.org/node/72085. As noted there, I think the best course is to go back to where you were before you started (hopefully you can do that). Use the previous version of the date module and go to update.php and make sure your content module updates are all applied. Then make sure the content module fields are all still working right after the updates. Then after that try the date module update.

KarenS’s picture

OK, I did find a problem in the install file. Wait a bit before trying this file. I'll be getting a change committed soon.

KarenS’s picture

Never mind on the last message, my problem was unrelated to this module. Latest commit should be good.

KarenS’s picture

Status: Active » Fixed

No further response on this and there have been changes committed since this message. I don't this applies any more, but reopen if not.

Anonymous’s picture

Status: Fixed » Closed (fixed)