You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we got some struggle with cross browser functionality and opt-in confirmation because sometimes $arguments were null inside ConditionAwareValidator.
We could reproduce this with the following setup:
Create a form with some mandatory fields
Create a condition to make one of these mandatory fields optional
Submit the form (e.g. with Chrome)
Confirm the opt-in email with another browser (e.g. with Firefox), maybe private mode will work as well here
After clicking the confirmation link the error message:
Validation failed while trying to call In2code\Powermail\Controller\FormController->createAction()
will be triggered, because $arguments were null and the validator will complain about a mandatory field that is not set because the powermail_cond-Session is missing. To fix this issue we have added the following condition to ConditionAwareValidator:
if ($arguments === null) {
return;
}
What do you think about it?
The text was updated successfully, but these errors were encountered:
We have the same problem. Firefox working, Chrome not.
the odd thing is: after the mail is confirmed, it's unhidden in Backend, but no further Mails are sent, so my receivers long time were not really aware of the problem, they just wondered why they got less emails..
Hi @einpraegsam,
we got some struggle with cross browser functionality and opt-in confirmation because sometimes $arguments were null inside ConditionAwareValidator.
We could reproduce this with the following setup:
After clicking the confirmation link the error message:
Validation failed while trying to call In2code\Powermail\Controller\FormController->createAction()
will be triggered, because $arguments were null and the validator will complain about a mandatory field that is not set because the powermail_cond-Session is missing. To fix this issue we have added the following condition to ConditionAwareValidator:
What do you think about it?
The text was updated successfully, but these errors were encountered: