Interval cannot be set to 1

#2 patch is working fine for me, @thefancywizard, please review this patch and apply.

To clarify, for the sake of recurring dates, one is actually the default value. That's the reason it isn't currently stored.

I understand the perspective that for an editor it may seem strange to see a value explicitly set not displayed the next time the content is edited. From a data management standpoint it also seems strange to me to to have some content that doesn't store a value (because they use the default) and some that store a value (matching the default) that behave the same.

If the UX of the current widget is confusing to some, then I'm open to discussion about changing it, but I'm not sure the change in the current patch is the best way to address it. If anything, I'd be more inclined to set 1 as the default value in the form element, but still not store it.

Thanks for the patch. I found it very confusing to not have the value 1 save. It wasn't intuitive to me that it was the default; I thought it was broken.

Just weighing in here that our users at the Department of Veterans Affairs are also confused by this behavior. Issue # 3469265 🐛 Repeat setting is missing when editing a node Needs review also seems to be a duplicate of this issue.

I would consider merging this in if the behaviour is controlled by widget setting.

The code to implement the new widget setting has been merged into the 4.2.x branch and will be in a new release shortly.

Automatically closed - issue fixed for 2 weeks with no activity.