Date Recur 3.x and Fullcalendar View 5.x

I see two ways to get recurring dates into the view. You can add the recurring date field and configure it in the fullcalendar display settings. However, this doesn't appear to be working.

You can also add a relationship to recurring items. I set up the display to use these start and end values, and had to hack FullcalendarViewPreprocess.php to get it to read the values.

The display plugin is looking for fields on a content entity, and doesn't see the recurring date value on the related item. I've attached a patch that overrides the content entity field check, to help find a solution.

Hello @mortona2k,

I have checked your patch and its having static fields names that will not work in all cases when we have different machine name of date field, so i have created a simplified patch that will work in all cases when we use occurrences relationship and occurrences fields for full calendar view start and end dates.

Anyone who is looking for same solution please test and verify.

Thanks
Dev

Please find the updated patch, there was a notice throws so fixed it now.

Smart Date module - https://www.drupal.org/project/smart_date - and Smart Date Recurring already work with FullCalendar View module in that you can create easily create nodes with multiple dates and then these will be displayed correctly on a FullCalendar View as calendar items (see screenshot).

That's not to say everything is working -> we're having an issue at the moment with tokens (when trying to get at one specific value in a series) -> e.g. in the popup dialog box.

https://www.drupal.org/project/fullcalendar_view/issues/3253685

I added a processor plugin for Recurring Dates fields. To use it, select the recurring date field for start, end, rrule, and duration.

Hiding the old patch - use the issue fork which implements the processor plugin.

Thank you. The forked module works for me and seems the Recurring Dates Field is the only module that currently works with recurring dates and FullCalendar View that the editor doesn't have to write rrules if they also install the Modular Widgets module.

I tested the MR, and it works fine.

For my use case, I have a multiple-value instance of date_recur.
The MR does not support that.
I do not know how to handle MR's, so please find a humble patch for the MR.

@KarinG (comment #5),
In order to add seasonal recurring dates into the Office Hours module,
I am comparing/testing both smart_date and date_recur.
I found that smart_date has a separate table for the RRULE, and generates the occurrences in the field_date, whereas date_recur just saves the RRULE in the field_data. The date_recur + preprocessor seems a more efficient way to me.

Setting to Needs work, in order to incorporate above patch (and perhaps the @todo in that patch).

I could not get the patch in #10 to apply either on its own or after applying the MR.

Try Fullcalendar Block module.

Did Fullcalendar Block suport views?
patch #10 is not compatible with current version 5.1.14

Fullcalendar Block supports all kind of data source including a output from a Drupal view.

The MR does apply to FV 5+

While the other module might be a solution for some it is not the solution that I was looking for. I wanted to see if there was the ability to natively connect Fullcalendar_view with date_recur without a third module.

Createing a DateRecur view processor seems to work.

Updating name, since It seems to address 'FullCalendar' module, instead of 'Fullcalendar View'.