- Issue created by @NicholasS
- Merge request !18Only set intialDate from query string if its a valid date and is actually set by query param → (Open) created by NicholasS
- 🇺🇸United States NicholasS
After this change if no start date in query param it does not default back to Dec 1969 - 🇦🇺Australia mingsong 🇦🇺
without a valid date parameter
First of all, any issue caused by an invalid parameter is not a bug.
Secondly, the Initial date parameter is optional, which mean if the client don't want to change the default initial date, which is the current day, no need to have the parameter in the URL. If the client does want to change the default initial date, then a valid date must be provided. If an unexpected initial date presented, please check the URL that you are visiting.
After all, this module doesn't provide any Drupal view. The view mentioned in the description of this issue is an example attached to the tutorial article.
- 🇺🇸United States fallenturtle
I have the same situation as @nicholass. It doesn't make sense from a UI perspective to have an exposed start date field for a calendar display like this since we are relying on FullCalendar to provide the calendar navigation.
Is the best solution to add the exposed start date filter to the filters on the Page display and then hide it with CSS? I suppose the alternative would be to add a hook or something that will add &start= to the end of the URL parameters when ever the filter is applied.
- 🇦🇺Australia mingsong 🇦🇺
I think there is a misunderstanding here.
The “start” parameter sent to the data source endpoint by the FullCalendar.js is the beginning of the date range of the dataset required by the FullCalendar.js. For example,when switching weeks or months, the FullCalendar.js will send out a HTTP request to the data source endpoint with the start date of that week, in your case, it is a request to the Drupal view built by you, not this module. This module has nothing to do with any Drupal view.
The “start” parameter in the URL to where the calendar block is placed is actually the “initial date” when the calendar should display at the beginning. Which is optional custom parameter.
Again, this module does not include any Drupal view, that is saying no patch to this module can help you to solve the problem with the view created by you.
- 🇦🇺Australia mingsong 🇦🇺
If you are using a Drupal view to provide the data to the calendar, I think you might want to try other module,
For example, https://www.drupal.org/project/fullcalendar →
Which is straightforward and simpler.