I'm running into a strange bug when adding a Smart Date recur field onto a Paragraph type. I've created a Paragraph type called "Event Session", and on that Paragraph type I have a single field called "Date" (field_event_date). In the field settings it's set to unlimited cardinality, required, allow recurring date values/12 with a default value of "Next hour" (though I've also set it to None with no effect).
Under manage form display on the Paragraph type I have it set to "Smart Date | Inline range", with these toggled on:
- Always include an empty...
- Hide the end date...
- Provide a checkbox...
- Use an overlay...
- Separator: to
- Use modal for...
- Allowed frequency values: daily, weekly, monthly, annually
I've added this Paragraph type onto a content type called "Event" as a field called "Schedule" (field_schedule), set to unlimited cardinality, and required. The Paragraph form settings under manage form display are the defaults for Paragraphs except I don't have a default so you have to click the "Add" button to add a paragraph to Schedule.
If I go to create an Event node, it will add a paragraph that looks like this:
Even though I haven't yet chosen to repeat (it's set to "never"), it still is showing all the stuff for repeats, and, it has the Advanced details with nothing in it. If I click "Add another item", the second value will look how I expect the first one is supposed to look. (note that I added the recommended module on this one's frontpage for clicking the X to remove a field from a multivalue field, but it was doing this even before I did that)
If, on the first value, I change "never" to "days", "weeks", whatever, nothing changes. Also selecting "After" under "Ends" does nothing, same for "On date". However it will work in the second value. BUT, if I click "X" to delete the first value so that the second value becomes the first, the second value does the same thing as the original first! Hopefully this makes sense. The browser console gives no JavaScript errors.
I've created a short screen recording demonstrating the issue: