I have run the phpcs and the correction manually.
Hi @Frontmobe, I found a checkbox in the project configuration that marks the project as supported. And after that, the composer install advice appears on the project home page. So I assume that solves the problem.
Hi @dnt, I just merged the fix for Issue #3449578, and tried it for myself on a small form with a preview page. Can you check if it al also works for your webform. (The fix is in the development version)
This is probably the same bug as #3449578. The fix is different. The fix for #3449578 tries to prevent calling the `Retrieval of Defaults` to often. This fix prevents the overwriting of already submitted values.
Fixed in 1.0.15
Fixed: However for current installation the filter must be added manually or the cmrf_reports module must be reinstalled.
Hi @Dieter, thanks. I did not notice this. The reason that it works in my use case is that I do not have a paymentstatus element in my form. The effect is that empty($webform_submission->getElementData($element_key)) is always true. The form processor uses the 'mollie_payment_status' field that passed to it in the same way as the mollie_payment_id field.
Hi Dieter,
I have added some documentation in the code about the checkconditions. As follows.
Sometimes a form processor is used to implement two payment options, for example a Sepa payment or an online mollie Payment. This can be implemented by making the mollie payment handler conditional. The forms processor must here only be disabled when the mollie payment checks are valid.
When no conditions on the mollie handler the conditions check is always true .
Hi @DieterHolvoet, it is definitely the wrong variable, so I will accept your MR. I am not sure if works after the merge. I had some success with by coupling the cmrf_processor to the webform update event:
and using the payment status in the condition.
That makes this module obsolete.
I have just created the new Drupal 10 release. Maybe that helps with downloading.
Hi @Frontmobe, thanks for testing. I have just created a new release with the Drupal 10 changes.
Hi @apaderno, thanks, I will check if I can use it the next time. For the related issue, I used your merge request.
I have a bit trouble with creating MR. I picked a different name for Gitlab, maybe that is the problem. But the change is now merged in the 2.0.x branch.
Fixed in 2.0.x en 2.1.x
This bug is fixed in the current 7.x-3.x branch.
Fixed in 2.0.4
I just this a user test. It is possible to send a text format field that is configured to have rich text to CiviCRM. You also to use a rich text filed in CiviCRM.
I just tried this patch, and it works in my situation.
Fixed in 2.0.3
Tester confirmed this works.
And done.
Hi Christina, thanks for your fix, I have commited it in https://git.drupalcode.org/project/cmrf_core/-/commit/fa430ad379a9bba81d....
Fixed in 2.0.3
The problem only shows up in an edge case, and the workaround is described in the issue.
Adding workaround