Closed (fixed)
Project:
Provus
Version:
2.1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
26 Jun 2023 at 15:42 UTC
Updated:
13 Jul 2023 at 14:42 UTC
Jump to comment: Most recent, Most recent file
Problem/Motivation
We have previously been using the fullcalendar_view module to display events in a calendar format. We were using the 6.x dev version because it uses Fullcalendar version 5 which is much more accessible than the version 4 of Fullcalendar. However, it seems that the maintainers of fullcalendar_view have opted not to maintain this 6.x version for drupal 10: https://www.drupal.org/project/fullcalendar_view/issues/3350850. They suggest to move to using a new module fullcalendar_block.
Proposed resolution
Evaluate the differences with fullcalendar_block and fullcalendar_view and decide what direction to take to support events calendar in Drupal 10 version of Provus.
Remaining tasks
* Install fullcalendar_block and setup with recurring, static, multiday events
* Evaluate whether it satisfies our needs
* Decide on plan forward
* Integrate
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | Screen Shot 2023-06-27 at 10.59.32 AM.png | 56.42 KB | johnlutz |
| #3 | Screen Shot 2023-06-27 at 10.58.51 AM.png | 31.04 KB | johnlutz |
| #3 | Screen Shot 2023-06-27 at 10.52.37 AM.png | 55.4 KB | johnlutz |
| #3 | Screen Shot 2023-06-27 at 10.52.21 AM.png | 55.76 KB | johnlutz |
Issue fork provus-3370235
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
johnlutzComment #3
johnlutzI have installed fullcalendar_block and tested this integration with fullcalendar out. I think it will work for our purposes. 1 benefit is that it uses a cdn for all of the libraries it requires out of the box so our maintenance can be lighter. It is a pretty different setup. It requires you to setup your own events feed. And the biggest problem in my mind is that it wouldn't be a client facing form to have content editors add this calendar to a page. It requires that you know this url and then it presents lots of fullcalendar display options in the block. I would imagine we have this block automatically configured on a page out of the box.
Since I needed to touch the views for the events and the recurring option wasn't working correctly with the rule right out of the box, I tried a different way to store the dates for events as well with this ticket and I suggest we move to that. We are currently using date_recur to store the dates and date_recur_modular to give us a better user experience adding recurring dates. The module I tried would replace both of these with one module: Smart Date. Smart date has a lot more installs and to me has a better user experience when editing static, recurring, and multiple dates. It also makes our views easier to implement because it doesn't require a relationship to the occurrences of the date. It just handles it out of the box. Here are some screenshots:
Comment #4
johnlutzComment #5
dsquaredb commentedI think moving to Smart Date would be a good move.
A preconfigured calendar block using the full_calendar block seems like a reasonable solution.
These changes would seem to put Provus in a better position for the future.
Comment #6
aastrong commentedI have to agree, i think moving to Smart Date would make more sense in the long run.
Comment #7
_renify_ commentedfull_calendar block https://www.drupal.org/project/fullcalendar_block solves performance issue of having large number of contents.
This can be implemented through
Comment #8
johnlutzComment #9
johnlutzComment #11
johnlutzComment #13
johnlutzQA Reviewed and successful
Comment #15
johnlutzComment #16
johnlutz