- Issue created by @dinazaur
- @dinazaur opened merge request.
- Status changed to Needs review
about 1 year ago 3:47pm 7 November 2023 - πΊπ¦Ukraine dinazaur
So I just merged 5.x into 6.x resolved merge conflicts and added support for v6 which includes: modification of few libraries and replacing few deprecated options with new ones. Also added the ability to use once instead of jquery.once.
- πΊπΈUnited States MattDanger
+1 for this patch. We have been using it on a large D10 project for the past few months with success. It helped us meet our accessibility initiatives.
- πΊπΈUnited States jackfoust
@mattdanger are you using this patch on the latest 5.x version of the module, or have you switched to 6.x that has the upgrade to v5 of the library installed - https://www.drupal.org/project/fullcalendar_view/issues/3085884 β ?
- πΊπΈUnited States erutan
I tried to install this patch via composer on the 6x branch, which led to some requirements conflicts. I just downloaded the code manually from the issue fork and dropped it in a local test instance, but I get ajax errors when editing a view for it and the calendar doesn't render on 10.3.1.
I'd love to try this out, mark it RTBC if it works and get a new version of this module out - is this still working for you dinazaur & MattDanger?
- π¦πΊAustralia mingsong π¦πΊ
I am planing to develop a premium version of this module, which will support the FullCalendar 6.
Details see π± Premium Version Active
- πΊπΈUnited States erutan
The extra features in the paid version aren't of interest to me (no recurring events or rrules needs), since someone already wrote code for Fullcalendar 6 to work that seems appropriate to just put into a new branch if it's functional and then the bonus features can be added on top of that.
We're using the calendar as a simple visual tracker, it'd just be nice to have the latest version for UI / accessibility improvements. :)
- Status changed to Closed: won't fix
4 months ago 11:15pm 7 August 2024 - π¦πΊAustralia mingsong π¦πΊ
It is good hear that a patch is enough to help someone already.
I close this issue since this feature won't be considered as the free version of this module.