Adding a URL param makes start = epoch

Should probably check if query contains specialParam not startParam.

Thanks for raising it.

This module use JSON to feed the FullCalendar.js, details on how it works can see the official documentation below.

https://fullcalendar.io/docs/v5/events-json-feed

When FullCalendar.js will visit the URL whenever it needs new event data, for example switch between weeks. So that it won't load all events into the client side (browser), only those required for the current week, for example. If the 'start' URL parameter wasn't specified by the user, the FullCalendar.js will generate one according to the current view. It could be the first day for the week or the month.

That all saying, the 'start' parameter shouldn't be missing. It could be misleading by the URL parameter specified by a user. In this case, it is a wrong input fed by the user.

After a quick look at the patch #3, I think it try to deal with a situation where the 'start' parameter is missing. As explaining above, the automated generated parameter by FullCalendar.js should always exist.

Please feel free to correct me, if I was wrong.

Thank you for this patch! I ran into the same issue with the missing start and end parameters in v1.1.x.

I use a views exposed filter and remove the start and end date inputs in the template. When a user chooses a filter value, the start and end parameters are not in the url. Starting with v1.1.x, this reverts the date back to 1969.

/calendar -> /calendar-feed?start=2025-02-23T00%3A00%3A00-05%3A00&end=2025-04-06T00%3A00%3A00-04%3A00

/calendar?s=&t=1234&c=All&o=All -> /calendar-feed?s=&t=7928&c=All&o=All&start=1969-11-30T00%3A00%3A00-05%3A00&end=1970-01-11T00%3A00%3A00-05%3A00

There are two things here.
1. The Http request sent to data source endpoint by the FullCalendar.js, in your case, the endpoint is a Drupal view created by you. If the endpoint doesn’t accept or recognize the start parameter with the request, nothing this module can do, in other words, no patch to this module can help you.

2. The HTTP request for a web page where the calendar block is embedded. In this case, the “start” parameter is to specify the initial date of the calendar, which is an optional parameter. If it is not specified by the request parameter, the current date is the initial date as default. Which means no need to check if the “start” parameter exists, as it is optional.

I close it as nothing to do with this module. Again, this module does not create or provide any Drupal view for you.

If you believe that something needs to do with this module, please provide some steps to reproduce the issue.

It would be helpful if you could provide a PHPUnit test as well.

Sorry for misunderstanding this issue.

This issue should be fixed with the new version coming shortly.

Fixed with 1.1.2