I both installed this module and "Conditional Fields" module to control time fields. I hope a time field will be displayed in the form when controlling components was triggered. Howerver, after creating the form, the time field always show me that "the field is required". Does it mean this module is not compatible with "Conditional Fields" module? How should I fix it?

Comments

panthar’s picture

panthar commented

Interested in a fix here also. I could probably fix it myself and post it up, anyone have any suggestions? I came across a patch for conditional fields with date, I thought this may work, but does not seem to have any effect.

Additionally, when you add a time inside a group, there is a display error that puts array() next to each time field. Not sure whats up there either.

YK85’s picture

YK85 commented

Hi, I was wondering if there has been any progress in this issue? Thank you

j.pose’s picture

j.pose commented
jphelan’s picture

jphelan commented

Same issue. Any fix?

jphelan’s picture

jphelan commented
Priority: Normal » Major
Everett Zufelt’s picture

Everett Zufelt commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
Category: bug » feature
Priority: Major » Normal

I'm happy to review and commit a patch for this if anyone is interested in writing it.

I would strongly prefer that the patch be written against the 7.x-1.x branch and then backported.

jphelan’s picture

jphelan commented

Do we know if 7 has the same issue? I have not tested it on 7.

peterpoe’s picture

peterpoe commented
Title: Not compatible with "Conditional Fields" module » Compatibility with CCK Time
Project: CCK Time » Conditional Fields
Version: 7.x-1.x-dev » 7.x-3.x-dev
Component: Code » Compatibility w/ other modules

This issue belongs to Conditional Fields: it's up to the module the handling of required fields.

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented
Issue summary: View changes
Status: Active » Closed (outdated)

Thanks for the report and all the efforts in here. But due to inactivity in this issue for some years and because of the upcoming EOL of Drupal 7, I will close this issue on the way cleaning up the issue queue.

Feel free to re-open as "Needs review" if you found a solution or have a patch to be reported to help others.