promt text
After updating with 6.x-2.7 on 6.x-2.x-dev, has faced a problem.
At me is node with type of content Date, and by quantity of values "not limited". Now at addition of one more value, all pregoing are erased. There was this all as soon as I have updated the module. The problem remains in any browser.

original text
После обновления с 6.x-2.7 на 6.x-2.x-dev, столкнулся с проблемой.
У меня есть нода с типом контента Date, и количеством значений "не ограничено". Теперь при добавлении еще одного значения, все предидущие стираются. Произошло это все как только я обновил модуль. Проблема остается в любом браузере.

Comments

alexeyal1’s picture

alexeyal1
Primary language Russian
commented
Version: 6.x-2.x-dev » 6.x-2.8

on 6.x-2.8 the problem on former remains

rbrownell’s picture

rbrownell
he/him
Primary language English
Location Gatineau, Québec, Canada
commented

I am experiencing the same issue with 6x-2.8... But I am not sure if this is a CCK or Date Issue. I have a content multigroup with a single date on each occurance in the multigroup with two additional options associated with each date. Any thoughs?

rbrownell’s picture

rbrownell
he/him
Primary language English
Location Gatineau, Québec, Canada
commented

I have other content multigroups in the same content type and this problem dose not happen with the other multigroup.

rbrownell’s picture

rbrownell
he/him
Primary language English
Location Gatineau, Québec, Canada
commented

Upon further messing around with the multigroup I am having trouble with, the other CCK content associated with each date retains its values, it is only the date field that is loosing its values. So this leads me to think that the problem is with the Date Module.

rbrownell’s picture

rbrownell
he/him
Primary language English
Location Gatineau, Québec, Canada
commented

More information for you... It isn't just in the Content Multigroup this problem is happening but with ALL date fields with repeat options. Though it isn't a huge issue for me, I can just plan a head and add as many fields as I need BEFORE I fill out the date field when creating a new node. It is however less than desireable when making changes (adding dates) to already existing nodes.

grimfandango’s picture

grimfandango commented

I noticed this same behaviour recently, using Multigroup. Reverting Date module to 2.7 and Multigroup works as normal (but opens a security concern).

edg’s picture

edg commented

I'm experiencing this problem with 6.x-2.8. I have a CCK for date fields which by default offers two rows of dates and the option for adding more rows. When the user clicks on the "Add another item" to add another date row the information in the previous two rows disappears.

arlinsandbulte’s picture

arlinsandbulte commented
Status: Active » Postponed (maintainer needs more info)

This looks like a duplicate of #1039192: date fields filled by date_popup get wiped on full/part form regeneration
Could someone please confirm that?
Also, IIRC, it might be a pop-up only issue that does not affect select lists or plain text fields.
Thanks,

rbrownell’s picture

rbrownell
he/him
Primary language English
Location Gatineau, Québec, Canada
commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

@arlinsandbulte I think it maybe is but I am not 100% sure. For me it is so I am going to declare it as such... This is a duplicate of #1039192: date fields filled by date_popup get wiped on full/part form regeneration.

If anyone disagrees they are more than welcome to reactivate this.

Thanks;

-Ryan

edg’s picture

edg commented

Yes, as a workaround I've got it to work by turning off the pop-up calendar and using a custom date text field instead.