Date module compatibilty

I don't understand what's the problem.

I haven't had problems with date fields in collections. Have you set the field collection to use the embedded widget? If not, the field collection's fields will not appear on the add content or edit content form.

Having a problem as well with a date select field in my embedded field collection (mind you, it's a field collection nested in another field collection).
When i create a node, and select a date, and save my node, the date field doesn't get saved, at all..

I seem to have the same problem.

date fields in the field collection arn't saved.

Idan

Setting this as active to get some focus on this again. I'm not sure what more info you need, please let me know so this is can get looked at ;)

I've used date module myself in field-collection, everything working fine. So if there is still a problem somewhere, we need to nail it down on module versions or any other preconditions.

Actually, there really is some strange behavior of date fields inside field collection. However, i don't know if it is Date's module issue or Field Collection modules. The problem is described here, any ideas?

Subscribing.

I had an issue where a date field (within a collection) failed to appear in the node add form.

I solved it by setting Custom permissions.

I found that the 3 'own value' permssions for authenticated user were insufficient.

I also had to set 'Edit anyone's value' and 'View anyone's value' which I found counter-intuitive.

This is still an issue.

I'm using date-7.x-2.6+26-dev and field_collection-7.x-1.0-beta5+8-dev.
The date field is set to 'date popup', one value allowed.
The field_collection is set to unlimited values.

When I add a few field_collections and hit save, the data disappears.

I can also confirm this issue. I posted some info with a possible fix in #1580032: Date values are not being saved when field is used in a nested field collection

I believe the patch I posted in #1580032: Date values are not being saved when field is used in a nested field collection should solve this. Can anybody confirm? I think this can be closed as a duplicate.