nicholosophy → created an issue.
Sorry added something to the wrong branch. MR !2 closed and MR !4 created
nicholosophy → changed the visibility of the branch 1.0.x to active.
nicholosophy → created an issue.
nicholosophy → changed the visibility of the branch 1.0.x to active.
nicholosophy → changed the visibility of the branch 1.0.x to hidden.
nicholosophy → created an issue.
nicholosophy → created an issue.
I have no issue with open source Devs generating an income from their work. What is disappointing in this case is that community members have provided patches to allow an upgrade to v6 but they have been not been accepted in order to have that functionality as part of a premium version.
There is value in the other premium features that you list that you could build that into a separate premium sub module whilst allowing this module to at least support the latest version of fullcalendar without a fee.
If the issue is that you don't want to maintain the free version any further or do not have the time to commit to the task, then I ask that you seek a new maintainer to take over the project. I don't have a history of maintaining Drupal modules however I am willing to assist if it allows this module to remain free for the community.
It doesn't help at the moment as I'm using a select field, not checkboxes. Even when I switch to a standard select list I'm not sure it works. I don't know if it would work with the standard query parameter completion that is in webform.
What I've done with a different site is create a webform handler that checks the #default_value has been set and then hides the select field. I've found that if it is hidden by default, #default_value doesn't get set.
Thanks! I've grabbed the patch from the PR (https://patch-diff.githubusercontent.com/raw/colemanw/webform_civicrm/pu...) and that applies cleanly.
nicholosophy → created an issue.
Updated the version. Meant to choose the latest version.
nicholosophy → created an issue.
nicholosophy → created an issue.
nicholosophy → created an issue.
nicholosophy → created an issue. See original summary → .
Just checking that the module is still being supported, because the duplicated issue mentions that the block module is preferred.
Personally, I would rather just use this plugin with a page view, rather than having to create a view, then add that block to a page.
nicholosophy → created an issue.
This patch changes the references to load the `mjs` files, and adds the `type: module` attribute when loading the library.
nicholosophy → created an issue.
nicholosophy → created an issue.
Yeah this appears to be an incorrect report. Thanks for looking into this.
nicholosophy → created an issue.
nicholosophy → created an issue.
nicholosophy → created an issue.