- Issue created by @khorrocks@pcrm.org
- 🇺🇸United States DamienMcKenna NH, USA
Moving this to the Schema.org Metatag issue queue as we need to fix it there. We also need to expand the test coverage to handle this scenario.
After upgrading to Metatag 2.0.0 and Schema.org Metatag 3.0.1, the recipeIngredient and recipeInstructions properties are output as strings instead of arrays. Both are configured with tokens of fields with multiple values. Also, the ingredient and direction values in the strings are separated by commas, when I have the custom separator set to '||'.
After investigation, it appears that the change made in https://www.drupal.org/project/metatag/issues/3367071 🐛 Custom separator also used for string concatenation Fixed to use commas instead of the custom separator during token replacement, has broken this functionality.
The simple solution would be to revert back to using the custom separator during token replacement. I tested this locally and it did solve the issue with the recipeIngredient and recipeInstructions properties. However, this change was made for a reason and I'm not sure how best to handle the two use cases.
Active
3.0
Code
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Moving this to the Schema.org Metatag issue queue as we need to fix it there. We also need to expand the test coverage to handle this scenario.