From the users point of view the unlimited value option of a field means that the user can add/input multiple separate items of a field bundle. In this case the user ist awaiting multiple dates. While checking repeating date option makes it possible to let ONE of these multiple items repeat daily, weekly, or something similar. In UI logic of dates and calendars, this has nothing to do with a hidden multiple added field item logic.

From the users point of view it is not understandable, why setting up the date field with the option checked to have a repeating date available, forces him to use the field with "unlimited value" (selector not changeable no more) option activated and without the option to use this for additional field entries. And how does that interfere with the option to have multiple repeating dates. As of the user understands it. I don't ask how to achieve this. I try to explain where the UI is logically not good designed.

Even if this is maybe forced by the way how this field should work I am rather not sure if this is a feature request or a bug. From the UX point of view this input logic is wrong. An option to set up a "value which repeats" is not a field with unlimited values, it is ONE value which has an addtitional parameter which can be set to make it repeat frequently.

The picture below also demonstrates very well how illogically this causes a form field failure in drupal node add forms, since these node forms have the same logic like the user, which gets confused by this behavior.

CommentFileSizeAuthor
#2 date_add_repeating.jpg52.11 KBdqd
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dqd’s picture

Issue summary: View changes
dqd’s picture

Issue summary: View changes
FileSize
52.11 KB
dqd’s picture

Category: Bug report » Task

Is there any progress or discussion on this somewhere else, where I can chime in and help? Didn't found anyhting yet. Thanks for any advice.

bluesman2014’s picture

I have the same issue and fully agree with you diqidoq. Please say if you've heard anything on this.

dqd’s picture

From what I know now about it it is def. a feature request. Not a bug. I was too tired these days to see the descriptions at some inputs telling so. But I still stay with the opinion that it feels kind of a work-around. But maybe this is because how the field instances work in Drupal. I would love to have a short explanation on this from a dev here to get an idea why this is the way how it has been achieved. I am sure there is a reason for how it is now.