I'm running Drupal 5.12 with the latest versions of CCK, Contemplate and Date. I've got a home-made content type (called 'match') that's stopped working properly (although I'm not sure when). The problem appears to be a field of type date. It no longer shows up when I create nodes of type 'match', ie. all the other fields show up and content can be added and the node saved. It no longer shows up when I edit existing nodes of type 'match', ie. the field is no longer there. When the nodes are displayed (using Contemplate) the field is not displayed.

When I display the content type fields (at .../admin/content/types/match/fields), the field is listed with the others. It has a label and a name, but the type column is empty.

There are very few error messages, except for the following.

1) When I display the fields for my content type (at .../admin/content/types/match/display)

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

2) When I try and configure the problem field (at .../admin/content/types/match/fields/field_date), I see no problems, but get the following when I hit save:

An illegal choice has been detected. Please contact the site administrator.

I'm not sure how I got into this mess. I haven't made any configuration changes on this site for quite a while. I've simply been keeping drupal and modules up-to-date and adding content.

Comments

dshaw’s picture

dshaw commented

I've managed to sort out my problem, but I don't know what caused it.

I found that the 'global_settings' column in the 'node_field' table was unset (ie. 'a:0:{}' or similar) for my date field. Similarly there were these sort of issues for the 'widget_settings' and 'display_settings' fields on the 'node_field_instance' table. Copying in values from other similar fields (using SQL on the DB itself) and then clearing the cache, resolved all my issues.

I certainly haven't been hacking around in the DB prior to this. Or making changes to the content type through the GUI. I wonder if an upgrade to the Date module (perhaps from 1.x to 2.x) might have been the cause??

karens’s picture

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

The D5 version is no longer being supported. Sorry.