Extensions issueshttps://lab.civicrm.org/groups/extensions/-/issues2023-12-08T15:20:13Zhttps://lab.civicrm.org/extensions/form-processor/-/issues/66ChainSelect option unavailable in FormBuilder for Country/State fields provid...2023-12-08T15:20:13ZUpperholmeChainSelect option unavailable in FormBuilder for Country/State fields provided via Form ProcessorPossibly linked to #65.
I want to use a Form Processor in a FormBuilder submission form, all on the same site. I see that I can choose my Form Processor from the drop-down list of entities when creating the FormBuilder form. Outstanding...Possibly linked to #65.
I want to use a Form Processor in a FormBuilder submission form, all on the same site. I see that I can choose my Form Processor from the drop-down list of entities when creating the FormBuilder form. Outstanding.
When adding Country and State/Province fields in a FormBuilder form, I would select the 'ChainSelect' option in the field widget settings such that the values offered by the State/Province field are driven by the selected country in the Country field.
But when using the fields made available by the Form Processor, this 'ChainSelect' option is not available. This leads to a very poor user experience when trying to select a state or province.https://lab.civicrm.org/extensions/form-processor/-/issues/65State/province field behaviour2023-12-08T15:19:12ZUpperholmeState/province field behaviourUsing a form processor to collect address information. I have a Country field and State/province field. These field types clearly work in that they reference the countries and the States/provinces in the Civi database. Really useful.
Bu...Using a form processor to collect address information. I have a Country field and State/province field. These field types clearly work in that they reference the countries and the States/provinces in the Civi database. Really useful.
But the State/province field does not present only relevant options based on the value selected by the user for the Country field, instead it presents a very long list of all available states/provinces.
Is there a way to enable this?https://lab.civicrm.org/extensions/form-processor/-/issues/64when does the 'Save' button actually save changes to the form processor?2023-12-08T14:51:28ZUpperholmewhen does the 'Save' button actually save changes to the form processor?Thanks for a great extension.
When I create a new form processor and begin by giving it a name, I see that an on-screen red alert message appears to tell me the form processor is not saved.
When I click on the 'Save' button to save the f...Thanks for a great extension.
When I create a new form processor and begin by giving it a name, I see that an on-screen red alert message appears to tell me the form processor is not saved.
When I click on the 'Save' button to save the form processor the alert text remains. Has the form processor been saved? No idea. I click on the 'Save' button a second time, and the alert message disappears.
This happens every time I want to save changes to the form processor.
This feels broken.
Expected behaviour: when I click the 'Save' button I would expect the red "Form processor is not saved" message to go away, or even better, to be replaced with a green alert to confirm that the form processor has been saved.https://lab.civicrm.org/extensions/stripe/-/issues/461Update your billing options not available on recurring receipts2023-12-07T08:35:25ZStoobUpdate your billing options not available on recurring receiptsStripe version 6.9.4, Civi 5.63.3, with Stripe configured as the default processor, we have having two possibly related issues.
1. When setting up a recurring plan the 'update your billing' details links are not available in the _email ...Stripe version 6.9.4, Civi 5.63.3, with Stripe configured as the default processor, we have having two possibly related issues.
1. When setting up a recurring plan the 'update your billing' details links are not available in the _email receipt_ (see below)
2. The email receipt is being sent inconsistently, at first it was, now it isn't at all
Is there a setting somewhere in the Stripe Extension we are missing? Is this a bug?
Or it is a feature request and not part of Stripe integration at the moment? If so, _how do_ folks update their credit card numbers or amounts on an existing plan?
Thanks!
![st](/uploads/971a271489a5fbfdeac9e35c885c949d/st.jpg)
![nos](/uploads/47e2459855d8982acfd3cbc5d9d78993/nos.jpg)https://lab.civicrm.org/extensions/certifications/-/issues/16Errors when adding certificate2023-12-06T21:40:33Zmikebeck-fuzionErrors when adding certificateI have come across a few errors when attempting to add certificates:
- When I click on the 'Add Certificate' button, it doesn't do anything, but the following error is logged in the console:
`An invalid form control with name='' is not ...I have come across a few errors when attempting to add certificates:
- When I click on the 'Add Certificate' button, it doesn't do anything, but the following error is logged in the console:
`An invalid form control with name='' is not focusable. <input class="form-control ng-pristine ng-untouched ng-scope ng-isolate-scope ng-empty ng-invalid ng-invalid-required" ng-required="$ctrl.defn.required" id="date-1" ng-if="!$ctrl.isMultiple()" crm-ui-select="{data: select2Options, placeholder: $ctrl.defn.input_attrs.placeholder}" ng-model="getSetSelect" ng-model-options="{getterSetter: true}" tabindex="-1" title required="required" style="display: none;">`
- When I try to add a new certificate via the menu (/certification/edit), the form submits but I don't see the certificate anywhere (could be user error; maybe I'm not looking in the right place?)
- The Certification Type field provided yes/no options by default, so I removed it via /admin/afform#/edit/afformEditCertification. Now when I add Certification Type back in, it doesn't get added to the form and is no longer selectable as a value to add to the form.
**This is using Drupal 10, CiviCRM 5.67.beta1, PHP 7.4.33**https://lab.civicrm.org/extensions/caldera-civicrm/caldera-forms/-/issues/11How to support Caldera Forms going forward2023-12-06T21:09:23ZkcristianoHow to support Caldera Forms going forwardAt the Manchester Sprint we were able to work to get a new build of Caldera Forms working that supports php 8.x (8.0-8.1 for certain).
@jaapjansma has committed to organizing a call in the new year about the progress.
Some considerat...At the Manchester Sprint we were able to work to get a new build of Caldera Forms working that supports php 8.x (8.0-8.1 for certain).
@jaapjansma has committed to organizing a call in the new year about the progress.
Some considerations to review:
- Should we look to release to the WP Repository? We'd need to have ownership transferred to "Us" which means we must define who we are and who will support the plugin
- Caldera had many add-on plugins. I have already found php 8.x issues in the payment processors, I suspect we will find issues in other add-ons as they were not created to be php 8.x compatible. What is our stance on these?
- There are at least two know WP --> CiviCRM integrations, will these be maintained?
- How do we get sufficient testing considering that there are many implementations that utilize bespoke code and old code to ensure we have a stable plugin base and are not potentially breaking production sites
Please add to this issue. I'd like us to review all potential risks and benefits of continuing to support Caldera Forms.
Thanks to @simon.hermann and @kainuk for all their work to get us to this point.https://lab.civicrm.org/extensions/themetest/-/issues/16Sort Snippets display, with recommended at top, then supported, then deprecated.2024-03-11T13:32:25ZnicolSort Snippets display, with recommended at top, then supported, then deprecated.At the moment a recommended pattern can appear bottom, and a deprecated at top.At the moment a recommended pattern can appear bottom, and a deprecated at top.https://lab.civicrm.org/extensions/searchactiondesigner/-/issues/10Checkbox fields always active - independent of backend setting2023-12-06T12:22:23ZTobias Voigttobias.voigt@civiservice.deCheckbox fields always active - independent of backend settingWhen using a checkbox field, users can choose to set this active by default. Yet this setting seems to have no effect since the checkbox is always aktivated (checked) by default - regardless of the backend setting.When using a checkbox field, users can choose to set this active by default. Yet this setting seems to have no effect since the checkbox is always aktivated (checked) by default - regardless of the backend setting.https://lab.civicrm.org/extensions/searchactiondesigner/-/issues/9Conditions can't be deleted2023-12-06T11:59:33ZTobias Voigttobias.voigt@civiservice.deConditions can't be deleted**Current behaviour:**
When deleting a previously set condition (by updating the condition, deleting any previously made configuration and saving the condition), the condition type stays active (without a set parameter).
**Expected ben...**Current behaviour:**
When deleting a previously set condition (by updating the condition, deleting any previously made configuration and saving the condition), the condition type stays active (without a set parameter).
**Expected benhaviour:**
When deleting a previously set condition (by updating the condition, deleting any previously made configuration and saving the condition), the condition is actually deleted. The condition's configuration screen looks as if no condition was ever set up.https://lab.civicrm.org/extensions/caldera-civicrm/caldera-forms/-/issues/10PHP8 issue? Error when submitting empty number fields used by calculation fie...2023-12-05T23:01:30ZAndreasandreas.howiller@civiservice.dePHP8 issue? Error when submitting empty number fields used by calculation field for divisionIf you create a calculation field for number fields as follows, the Caldera form freezes when submitting in PHP 8.0 and PHP 8.1 if the number fields are left empty. On PHP 7.4. the form is submitted without errors. On all three PHP versi...If you create a calculation field for number fields as follows, the Caldera form freezes when submitting in PHP 8.0 and PHP 8.1 if the number fields are left empty. On PHP 7.4. the form is submitted without errors. On all three PHP versions the form is submitted when the number fields are filled.
![2023-12-05_23-34](/uploads/2b38f30b788d806b210d7b8d130d8a12/2023-12-05_23-34.png)
Error in browser console:
![2023-12-05_23-17](/uploads/6ee22e97cc764280e13676d60bf30312/2023-12-05_23-17.png)https://lab.civicrm.org/extensions/fromemailpermission/-/issues/2Warning: Constant MAX_ITEMS already defined in include_once()2023-12-13T12:02:51ZCésarWarning: Constant MAX_ITEMS already defined in include_once()```
Warning: Constant MAX_ITEMS already defined in include_once() (line 8 of sites/domain.com/files/civicrm/ext/fromemailpermission/fromemailpermission.php).
Warning: Constant MAX_ITEMS already defined in include_once() (line 8 of sites/...```
Warning: Constant MAX_ITEMS already defined in include_once() (line 8 of sites/domain.com/files/civicrm/ext/fromemailpermission/fromemailpermission.php).
Warning: Constant MAX_ITEMS already defined in include_once() (line 8 of sites/domain.com/files/civicrm/ext/fromemailpermission/fromemailpermission.php).
```
Source: https://lab.civicrm.org/extensions/fromemailpermission/-/blob/1.1.3/fromemailpermission.php?ref_type=tags#L8
cc: @sluc23https://lab.civicrm.org/extensions/formprotection/-/issues/23Flood control on editing civicrm contacts2023-12-05T02:05:08Ztoby-fzFlood control on editing civicrm contactsWe were recently using this module for card testing prevention and therefore, had this extension's configuration set very tight. One side effect of this was that when we were editing CiviCRM contacts, the flood control kicked in. This wa...We were recently using this module for card testing prevention and therefore, had this extension's configuration set very tight. One side effect of this was that when we were editing CiviCRM contacts, the flood control kicked in. This was not a hard fix, we simply set the flood control to apply to just the forms we wanted rather than all forms but I'm curious which of the options in the form type list was causing this?
Steps to recreate:
Set the flood control to apply on all forms
Set the rest of the options to the following
![image](/uploads/ca48075a76db5ba03317d7b1914319a8/image.png)
add a handful of test contacts to a test group ( I think the following error triggered on the 4th)
Please correct the following errors in the form fields below:
There was a timeout while processing your request. Please wait a few seconds and try again.
Adding contacts to a group was not the only scenario where this happened, But the one where I have the best concrete example.https://lab.civicrm.org/extensions/archivemailing/-/issues/8Feature Request: Option to also delete unscheduled mailings2023-12-04T11:29:07Zeff-alexymikFeature Request: Option to also delete unscheduled mailingsIt would be nice if there was a checkbox option that would also delete any Mailings older than x days that haven't been scheduled.
During some maintenance I deleted 700 such mailings and consequently was able to delete 1m+ related rows...It would be nice if there was a checkbox option that would also delete any Mailings older than x days that haven't been scheduled.
During some maintenance I deleted 700 such mailings and consequently was able to delete 1m+ related rows from `civicrm_mailing_recipients`.https://lab.civicrm.org/extensions/civirules/-/issues/210Deprecate conditions/actions?2024-03-24T23:20:19ZJonGoldDeprecate conditions/actions?We have conditions/actions that we've replaced with better versions, but maintained the old one for compatibility with existing rules.
However, some of these old conditions/actions are dangerous (e.g. [see discussion on PR #26580](https...We have conditions/actions that we've replaced with better versions, but maintained the old one for compatibility with existing rules.
However, some of these old conditions/actions are dangerous (e.g. [see discussion on PR #26580](https://github.com/civicrm/civicrm-core/pull/26580)). We should have a way of deprecating conditions/actions.
Proposal:
* Use `is_active` if it's not otherwise used - otherwise create `is_deprecated` column.
* Modify the upgrader to allow passing in the new value.
* A system check for rules with deprecated conditions/actions.
* Deprecated rules can't be selected on new rules.
* (Strongly prefer) we don't allow users to save rules with deprecated conditions/actions.
* In time, we remove the deprecated items.
I can write the code for this if there's buy-in from other stakeholders. I envision a `deprecated()` method on deprecated conditions/actions that returns help text for replacing the condition/action. In many cases, it can probably be automated.JonGoldJonGoldhttps://lab.civicrm.org/extensions/authnet/-/issues/33Upgrade Error: Could not delete payment processor type2024-02-26T18:54:33ZrbaughUpgrade Error: Could not delete payment processor typeWhen upgrading a staging site from 2.5.2 to 2.5.3, I was presented with a message about not being able to delete a payment processor. Looking at the logs, it seems it was trying to delete the Authnet payment processor which is the only p...When upgrading a staging site from 2.5.2 to 2.5.3, I was presented with a message about not being able to delete a payment processor. Looking at the logs, it seems it was trying to delete the Authnet payment processor which is the only processor set up on the site.
```
Dec 01 07:24:43 [error] (com.donordepot.authnetecheck) Unable to delete managed entity "Authorize.Net (Credit Card)": Could not delete payment processor type
Array
(
[exception] => CRM_Core_Exception: "Could not delete payment processor type"
#0 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/ManagedEntities.php(369): civicrm_api3("payment_processor_type", "delete", (Array:2))
#1 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/ManagedEntities.php(149): CRM_Core_ManagedEntities->removeStaleEntity((Array:8))
#2 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/ManagedEntities.php(113): CRM_Core_ManagedEntities->reconcileEntities((Array:93))
#3 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(417): CRM_Core_ManagedEntities->reconcile()
#4 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Extension/Manager.php(231): CRM_Core_Invoke::rebuildMenuAndCaches(TRUE)
#5 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Extension/Downloader.php(152): CRM_Extension_Manager->replace("/tmp/tmp-xMrj2b//authnet-2.5.3")
#6 /home/www/staging/wp-content/plugins/civicrm/civicrm/api/v3/Extension.php(239): CRM_Extension_Downloader->download("com.donordepot.authnetecheck", "https://lab.civicrm.org/extensions/authnet/-/archive/2.5.3/authnet-2.5.3.zip")
#7 /home/www/staging/wp-content/plugins/civicrm/civicrm/Civi/API/Provider/MagicFunctionProvider.php(89): civicrm_api3_extension_download((Array:4))
#8 /home/www/staging/wp-content/plugins/civicrm/civicrm/Civi/API/Kernel.php(158): Civi\API\Provider\MagicFunctionProvider->invoke((Array:8))
#9 /home/www/staging/wp-content/plugins/civicrm/civicrm/Civi/API/Kernel.php(81): Civi\API\Kernel->runRequest((Array:8))
#10 /home/www/staging/wp-content/plugins/civicrm/civicrm/api/api.php(22): Civi\API\Kernel->runSafe("Extension", "download", (Array:2))
#11 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Admin/Form/Extensions.php(202): civicrm_api("Extension", "download", (Array:2))
#12 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/Form.php(624): CRM_Admin_Form_Extensions->postProcess()
#13 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/StateMachine.php(144): CRM_Core_Form->mainProcess()
#14 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/QuickForm/Action/Next.php(43): CRM_Core_StateMachine->perform(Object(CRM_Admin_Form_Extensions), "next", "Next")
#15 /home/www/staging/wp-content/plugins/civicrm/civicrm/packages/HTML/QuickForm/Controller.php(203): CRM_Core_QuickForm_Action_Next->perform(Object(CRM_Admin_Form_Extensions), "next")
#16 /home/www/staging/wp-content/plugins/civicrm/civicrm/packages/HTML/QuickForm/Page.php(103): HTML_QuickForm_Controller->handle(Object(CRM_Admin_Form_Extensions), "next")
#17 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/Controller.php(355): HTML_QuickForm_Page->handle("next")
#18 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/Page/Basic.php(364): CRM_Core_Controller->run()
#19 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/Page/Basic.php(170): CRM_Core_Page_Basic->edit(2, NULL)
#20 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Admin/Page/Extensions.php(105): CRM_Core_Page_Basic->run()
#21 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(319): CRM_Admin_Page_Extensions->run((Array:3), NULL)
#22 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(69): CRM_Core_Invoke::runItem((Array:19))
#23 /home/www/staging/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(36): CRM_Core_Invoke::_invoke((Array:3))
#24 /home/www/staging/wp-content/plugins/civicrm/civicrm.php(1199): CRM_Core_Invoke::invoke((Array:3))
#25 /home/www/staging/wp-includes/class-wp-hook.php(308): CiviCRM_For_WordPress->invoke("")
#26 /home/www/staging/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters("", (Array:1))
#27 /home/www/staging/wp-includes/plugin.php(517): WP_Hook->do_action((Array:1))
#28 /home/www/staging/wp-admin/admin.php(259): do_action("toplevel_page_CiviCRM")
#29 {main}
)
```https://lab.civicrm.org/extensions/checksumexport/-/issues/3PHP 8 compatibility2023-12-07T07:50:34ZmasettoPHP 8 compatibilityI report that this extension is not compatible with PHP 8:
> PHP Fatal error: Array and string offset access syntax with curly braces is no longer supported in .../ext/checksumexport/checksumexport.civix.php on line 246I report that this extension is not compatible with PHP 8:
> PHP Fatal error: Array and string offset access syntax with curly braces is no longer supported in .../ext/checksumexport/checksumexport.civix.php on line 246https://lab.civicrm.org/extensions/civimobileapi/-/issues/89Drupal 9/10 is not supported2024-03-26T18:37:56ZDetlev SieberDrupal 9/10 is not supportedDrupal 9 is using different paths, that are not supported by civimobile as is:
![grafik.png](/uploads/2e60832a6091334f3e383e62d3ee2473/grafik.png)
There is a workaround described here:
https://civihosting.com/blog/civimobile-and-drupa...Drupal 9 is using different paths, that are not supported by civimobile as is:
![grafik.png](/uploads/2e60832a6091334f3e383e62d3ee2473/grafik.png)
There is a workaround described here:
https://civihosting.com/blog/civimobile-and-drupal-9/
... but that "solution" is very hacky and will be destroyed with every "composer require".
Would it be possible to implement a sustaining solution into CiviMobile, in order to make it work "out of the box" for Drupal 10?
(this is a duplicate / wrapper for #66, #81 and #70 ).
By the way, #66 and #70 should not be marked closed, imo.https://lab.civicrm.org/extensions/action-provider/-/issues/47Discussion - ValidateChecksum action should return FALSE instead of throwing ...2023-11-29T21:32:09Zjustinfreeman (Agileware)Discussion - ValidateChecksum action should return FALSE instead of throwing an exception, so that other actions can handle the missing Contact IDCurrently the ValidateChecksum action throws an exception, which causes processing to stop. Whereas if it returned FALSE then other actions could check if the Contact ID was empty and do something else.
```
public function validatePara...Currently the ValidateChecksum action throws an exception, which causes processing to stop. Whereas if it returned FALSE then other actions could check if the Contact ID was empty and do something else.
```
public function validateParameters(ParameterBagInterface $parameters) {
$contactId = $parameters->getParameter('cid');
$checksum = $parameters->getParameter('cs');
$valid = \CRM_Contact_BAO_Contact_Utils::validChecksum($contactId, $checksum);
if (!$valid) {
throw new InvalidParameterException(E::ts('Invalid checksum, can not access contact data.'));
}
return TRUE;
}
```https://lab.civicrm.org/extensions/gocardless/-/issues/139GoCardless API deprecating Redirect Flows... in favour of Billing Request [Fl...2024-02-19T16:53:04ZRichGoCardless API deprecating Redirect Flows... in favour of Billing Request [Flows]
According to this page: https://developer.gocardless.com/api-reference/#core-endpoints-redirect-flows
> Deprecated: Redirect Flows are legacy APIs and cannot be used by new integrators. The Billing Request flow API should be used for y...
According to this page: https://developer.gocardless.com/api-reference/#core-endpoints-redirect-flows
> Deprecated: Redirect Flows are legacy APIs and cannot be used by new integrators. The Billing Request flow API should be used for your payment flows.
[Chat topic](https://chat.civicrm.org/civicrm/pl/toqn5s56x3nt9nn1fcyerd919e)v2.0.0https://lab.civicrm.org/extensions/civirules/-/issues/209Field Value comparison with condition Empty not working on date field2023-11-23T15:54:30Zeth4everField Value comparison with condition Empty not working on date fieldUse case: I would like to execute an action (Set Chassé step to '01-01') when a thank you letter is sent (Thankyou_date field is filled).
I utilize this rule:
- Trigger: Contribution is changed
- Condition: Contribution is Completed
- F...Use case: I would like to execute an action (Set Chassé step to '01-01') when a thank you letter is sent (Thankyou_date field is filled).
I utilize this rule:
- Trigger: Contribution is changed
- Condition: Contribution is Completed
- Field value comparison (original value): Is Empty
- Field value comparison (new value): Is Not Empty
This rule doesn't fire.
The issue appears to be that the Field Value Comparison condition "Is Empty" does not function properly on a date field. It functions correctly on a Text field (Source), but not on a date field (Receipt.date of Thankyou_date).
The condition "Is Not Empty" on a date field does function properly.
Anyone with the same issue? Any suggestions how to fix it?