- Issue created by @chucksimply
- 🇺🇸United States chucksimply
Could this issue be related to the token’s depth? Even using just
[easy_email:field_report:entity:field_photos]
isn’t recognized as empty, and the process stops. - 🇺🇸United States pianomansam
Could this issue be related to the token’s depth? Even using just
[easy_email:field_report:entity:field_photos]
isn’t recognized as empty, and the process stops.@chucksimply Sorry to hear that you are experiencing issues. When you uninstall token_or, does this token produce a value?
- 🇺🇸United States chucksimply
The token output behaves as expected, whether or not the token_or module is installed.
For example, with this field: [easy_email:field_report:entity:field_photos]
• If the field contains an image, the value displays correctly.
• If the field is empty, no value is produced—there’s nothing returned (no space, extra character, or anything).However, the token_or module still treats it as if it has a value, even when nothing is returned.
- 🇺🇸United States pianomansam
@chucksimply I'm unable to reproduce this. I've tried to make this happen with a multi-value image media field and displaying the image style url of the second entity in the field, then falling back to the first entity in the field. The functionality worked as expected.
[node:field_banner:1:entity:field_media_image:featured_image_desktop:url|node:field_banner:0:entity:field_media_image:featured_image_desktop:url]
Can you reproduce from a clean site install and provide all the necessary steps? Or even better, create a feature branch and write a test reproducing the issue?
- 🇺🇸United States chucksimply
Apologies for my delayed response. Wondering if this has to do with the way the Easy Email module handles its tokens? I'll have to do further tests and circle back. Thanks again for the quick replies.