Duplicates of node with multiple date values

I have the same issue. When a node's Date Range field has multiple date values, the node appears on the calendar once for each of those dates. For an event that has 8 values in the date range field, the event appears 8 times.

The view is configured as recommended in https://www.drupal.org/project/fullcalendar_view/issues/3206496 → . The date range setting of "Show all values in the same row" is unchecked.

I have looked at the related issues. I cannot find a configuration that displays an event only one time.

Try Fullcalendar Block module.

Does this mean that Fullcalendar View should not be used for displaying nodes with multiple date values? If so, could you update the project description because it is in the list of features.

5.x (8.x-4.0 and above) version
Upgrade Fullcalendar.js to V4.
Automatically load third party library from CDN if local host library is missing.
Introduce a new plugin type of 'Fullcalendar View Processor' which allow other modules to alter all properties of the Fullcalendar without hacking the JS from this module.
Support rrule.js for recurring event
Support Multiple Calendars in One View
Support for entities with multiple dates
Support Ajax filter.

🐛 End date value is not respected on Daterange field if using the same date field with _1 appendix on views, shows an hour default interval instead Closed: won't fix

More details, see related issues.

@Mingsong, thank you for adding related issues. I have reviewed all of these related issues and they do not address the original problem. If there is a single node that has multiple date values in the same daterange field, then that event appears multiple times on the calendar. I included the screenshots above 💬 Duplicates of node with multiple date values Closed: outdated . See additional screenshot of the node edit form.

As far as I can tell, there is no way to use Fullcalendar View for displaying event nodes IF these nodes use a daterange field and that daterange field allows multiple values.

See #3048219: Support for entities with multiple dates → about the feature to support multiple dates.

The source code to implement it.
https://git.drupalcode.org/project/fullcalendar_view/-/commit/bc20e378c7...

My apologies to @mindsong for all the posts and thank you for speedy replies!

Update for others who are troubleshooting this module:
If you have entities with multiple date values AND you add any filter to limit the calendar by date ("greater than or equal to now", or some other filter) in order to limit the number of results and to improve the load, then the entities with multiple date values will not display properly on the calendar. Instead, a new row is displayed on the calendar for each of the entity dates.

So, if you have a lot of entities (causing a slow load) and have entities with multiple dates, then you may also run into this problem.

I can expand a little on the troubles Potassiumchloride is experiencing.

Having Fullcalendar View display a (day) calendar based on a daterange field with multiple values works like a charm. Until you add filters.

Some filters work well
i.e node type == appointment, published== yes.
You get single entries in the calendar, and they're wonderfully draggable and editable.

Others filters carry penalties
date_range_field == not empty will result in those undraggable, duplicate entries we see in #2 💬 Duplicates of node with multiple date values Closed: outdated .

field_car_term == 3 will make entries based on nodes with a changed date different from today invisible. I have not finished investigating this strange error. Can only say it apparently does not matter if the Default date source of the view is Current date, Date of first view result or Fixed value.

Changing or adding view filters programmatically → offers no escape. The troubles caused by filtering persists.

So the best advice for now is: Are you getting no or duplicate entries? Try removing the filters one by one until there are no errors.

I tried a combination of enabling/disabling displaying all values in the same row per #1, removing filters per #9 and #10, splitting up the date range field by adding a separate daterange field instance to use as the end date (and the original field for the start date). It stopped showing duplicate date entries during the last test. I started undoing what I’d done but the duplicates were still gone. Adding the filter for date not empty brought back the duplicates. Removing it got rid of the duplicate. This has me suspecting some kind of caching issue if you don’t see results right away after removing all problematic filters?