- Merge request !9Issue #2849810: Data processors do not check type before performing type-specific operations β (Open) created by jonathan1055
- πΊπΈUnited States aitala
I'm utterly confused by the issues threads here...
I'm getting an error that looks close to this one, but...?
TypeError: Drupal\typed_data\PlaceholderResolver::scan(): Argument #1 ($text) must be of type string, null given, called in docroot/modules/contrib/rules/src/Plugin/RulesDataProcessor/TokenProcessor.php on line 69 in Drupal\typed_data\PlaceholderResolver->scan() (line 182 of docroot/modules/contrib/typed_data/src/PlaceholderResolver.php).
Any idea what I need to do here?
Thanks,
Eric - π«π·France dcoppel
Hi,
I have same error of @aitala by using token annotation in my email actions rules after update to version 4.
Thanks for help. @aitala @dcoppel I had the same issue as the one you outlined here https://www.drupal.org/project/rules/issues/3469170 π Using token annotation in rules action crash after update to version 4 Closed: duplicate .
In the send email portion of the rule I had left the language field empty as it wasn't required but after upgrading to version 4 it started throwing errors. I would suggest checking if you have any empty fields that could be returning null instead of a string.
For your reference, I have set the language field to @language.current_language_context:language_interface.
- π«π·France dcoppel
@tidunz : thanks for your reply.
You are right ! It seems that adding the language field to @language.current_language_context:language_interface in email configuration works fine now !
Thanks a lot for your help !
Regards - πΊπΈUnited States AaronBauman Philadelphia
Seems like if "language" was working previously with a blank value, and now a value is required, then Rules should provide a default value.
! It seems that adding the language field to @language.current_language_context:language_interface in email configuration works fine now !
Works for me too with this workaround.