When using comment driven to drive changes in _any_ field in a content type which has a date field, the form fails with the message:

There are errors in:
The dates are invalid.

Comment driven functions as expected in node types where there are no date fields.

Using 6.x-1.x dev (and latest non-dev attempted) of driven and comment_driven, and latest stable (6.x-2.4) of date.

Anything else I can provide to help troubleshooting?

Comments

arhak’s picture

arhak commented

mm... I haven't seen that one
I'll have to spare some time for a driven dates review
there are several configurations to test
we have also #792198: unmodified dates get shifted (having time zone)

obrienmd’s picture

obrienmd commented

Anything I can do to help debug?

arhak’s picture

arhak commented

what I need is diversified feedback
I can't make decisions based on a particular broken configuration without knowing if the rest of them will hold

I need to know which date's configurations are working as expected
which ones get shifted (it seems to be related with time zone handling, but there are three kind)
and which would be the steps to reproduce this particular error

obrienmd’s picture

obrienmd commented

Setting up dev environments to test this further today, more info coming for you arhak!

obrienmd’s picture

obrienmd commented
Status: Active » Closed (fixed)

Actually, can't consistently reproduce this one, I will close this task unless I am able to provide more data in the future, sorry.

PAdrian’s picture

PAdrian commented
Status: Closed (fixed) » Active

i can reproduce this error message by doing this:
add new content type
in this content type add a date field with from date and to date option
add some other fields
set whatever driven fields you want except the date one
add new content of this type and then comment on it.
voila

demoshane’s picture

demoshane commented

Have to same issue so can confirm this. Latest date.