Date field with To date option

Please try version 6.x-1.x-dev. I'm not getting this problem there. Also, if you marked the To date as required, you should either:
a) give it a default value
b) allow your first state to edit it
so that Drupal doesn't complain about a missing value.

I use Date module version 6.x-2.0-rc6. Workflow field version 1.0 or 6.x-1.x-dev. With default value or not also give same result. My first state already give this field a value. This make me must give this field alway editable. Date Granularity is Year Month Day Hour Minute. Not second. I use Drupal 6.6. in IIS window domain, last version of PHP and MySQL.

Do I miss something? I create a fresh 6.6 site with just workflow_fields, workflow, cck, date. I still get this error.

Here's what I did:

* installed date-6.x-2.0-rc6
* edited a content type to add a date field with widget = Text field with custom input format
* edited the second workflow state (after creation) to make this field visible but not editable
* created a new node of the content type, and gave the date field some value
* made sure the workflow moved to the second state
* edited again, saw the date field displayed but not editable, submitted: no complaint, the date field remained the same

What did I miss in this scenario?

Which all module version did you use? CCK, date, workflow, workflow field?

* edited the second workflow state (after creation) to make this field visible but not editable

I give date field edit at creation and next state "First state". And then the second state "Second state" is viewable but not editable.

cck-6.x-2.1
date-6.x-2.0-rc6
workflow-6.x-1.0-rc3
workflow_fields-6.x-1.x-dev
drupal-6.7

I think only me have this bug. But after search, I found this http://drupal.org/node/289327 and this http://drupal.org/node/298440 . It seem be a date bug and it is resolved.

Why I still get this ???

Can you try the date fields with Content Permission? Do you still get the same problem as they described it?

If I don't use workflow and workflow field module, and I create a role with userA that have view, not editable that date field. UserB with editable and viewable. If a node created by userB with date field -> no error. UserA edit this node -> no error.

Seem to be only when use workflow to set field permission will get this error.

I regconize that I set Content permission for this field is editable for everyone. So it will load when node save even if workflow field set it to only viewable. Now I remove role that not need to edit date field at Content permission module. This resolve the error at this state. But if this role need to edit date field at other state, it will unable.

I still need help at this bug. If I don't use content permission then I will get this warning when save at state without editable permission date with to date field.

1. Do you also get this problem if the field is marked as non-editable *and* non-visible?
2. According to the error you're getting at date_elements.inc:392, the field's To date is marked as required. Is that the case?

1. Yes
2. To date is marked as required or Optional will get the same

* Please make sure you don't have an older copy of CCK, Date or any other module in the modules folder. This is a common cause of hard-to-trace problems.
* When you save the node at the state where date is marked as read-only, does the node actually get saved?

Sorry for not being to help you more. I am still not able to reproduce this bug even though I keep trying. If you want to send me your Drupal installation + database snapshot please let me know.

Here is something similar to what is noted above- it might be the same bug:

The errors are:

* warning: date_offset_get() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 494.
* warning: date_format() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 497.
* warning: date_format() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 498.
* warning: date_offset_get() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 500.
* warning: date_timezone_set() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 501.
* warning: date_timezone_set() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 502.
* warning: date_format() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 503.
* warning: date_format() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 504.
* warning: date_timezone_set() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 512.
* warning: date_timezone_set() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 513.
* warning: date_format() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 514.
* warning: date_format() expects parameter 1 to be DateTime, null given in /home/httpd/dev/drupal_6_sites/all/modules/date/date/date_elements.inc on line 517.

My date field value then disappears. Here are the module versions:

cck-6.x-2.2
date-6.x-2.1
workflow-6.x-1.1
workflow-fields-6.x-1.1
drupal-6.10

If a role has view-only access during a certain step in a workflow, the date field is set to NULL and the above errors are seen.

I will try the dev version.

Thanks,
DaveA

Same result with 6.x.1.x-dev
:(

Thanks,
DaveA

Yes, the date module changed recently and introduced a whole lot of problems. I'll be looking at this soon.

Can you please try to create a new node with the latest date module in place, and then check if workflow_fields gives you the same errors? I encountered problems upgrading my existing CCK nodes containing dates to the latest date.module.

Also, what are the settings on the date field? single/multiple values? disabled/optional/required to date? widget type?

I'm also having similar problem, Used the latest version of all cck, date, workflow/workflow fields but

Do we need to write any function of workflow_fields process just as written for file - _workflow_field_process_file?

I hope not. Can you give me the settings of your date field for me to try and reproduce this behaviour? See comment #16 for what I'm asking.

I've used the single date, optional, widget type default (tried both Select List / Text Field with Date Pop-up calendar).

Created couple of date cck:
'birth_date' cck with 'Select List' required.
'exam_date' cck with 'Select List' optional.

I've taken create student and workflow state as 'Entry Point' and 'Exit Point'.
'Entry Point' ::
- birth_date (visible and editable both)
- exam_date (visible and editable both)

'Exit Point' ::
- birth_date (visible and not editable)
- exam_date (visible and editable both)

When first create .. No issue.
Change the workflow to 'Exit Point' and save .. No issue.
Again go and edit the 'no editing done' and save .. birthdate field goes wrong ... year's first letter goes to zero. Even when do preview at this point of time.. Preview gives wrong result.

Is it sufficient information to reproduce the error?

kratib,

Are you able to reproduce the bug?

Sorry I haven't replied earlier. I was able to replicate a problem using your scenario and I'm currently looking into it.

Seems this is a date module issue: #408770: #access of date_combo fields prevents validation. I am following up on it.