Closed (fixed)
Project:
Date
Version:
7.x-2.0-alpha5
Component:
Date Field
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Dec 2011 at 15:58 UTC
Updated:
31 Jan 2012 at 13:31 UTC
I have a multistep form (Multistep 7.x-1.x-dev) with multiple date fields (date popup widget, one value per field). These fields are not on the first page. When I submit de first page I get an error:
There are errors in Gewenste opleverdatum deal value #1:
De data zijn ongeldig.(invalid data)
The latest version of the Date module seems to validate date fields that are not in the particular step of the form and throws a validation error. If I move this date field to the first page and submit the form with that field empty the validation error is not thrown for that field.
I'll have to downgrade my version of Date module because alpha5 seems to be incompatible with multistep forms.
Comments
Comment #1
karens commentedNot critical when it only happens when you use another module that is not widely used. I cannot replicate any problem in the latest dev code. I can create a content type with two fields, have the date field as the second step, and everything works fine.
It is possible than in addition to Date, Fieldgroup, and Multistep, you are also using Entity Translation. Which is even more of an edge case. Entity Translation required a ton of workarounds to handle dates correctly so that could be one level of complexity too far. And there are lots of different ways translation handling can be set up (Entity Translation or Content Translation? Are you translating the Date field or not? Etc).
First you need to confirm that things are broken in the latest dev code (alpha5 is outdated now). If so, then you have to figure out the exact steps to reproduce this on a clean site, because I cannot reproduce it.
Comment #2
karens commentedNo response and we are now to rc1. So assuming things are working or the reporter no longer cares.