Our site has this issue as well.
For others with the same problem, we had success performing a find and replace in our theme as follows:
Find:
['#options']['attributes']
Replace:
['#url'].options['attributes']
Yes, the linked issue #3423171 was a duplicate of this problem.
We did a find and replace in our theme and replaced all instances of ['#options']['attributes'] with ['#url'].options['attributes'] which solved our issue.
Thank you!
I'm not sure, I'm not a seasoned Drupal dev. How can I determine which formatter I'm using?
Is the ['#options'] array generated through core or is it generated through the modules that use it? Please advise if this bug is being reported in the wrong place, thanks.
Thanks for finding the duplicate issue.
We did test with 6.2.x-dev (Drupal 10, stable9 custom theme) and it resolved both issues reported. Thank you!
Apologies, should have been more specific. This is on my company's test site, still in development, with a custom theme being built from the stable9 base theme. Let me know if I need to be more specific, I'm not as involved in our site theming.
These errors are present on a separate branch using the custom theme, Drupal 10.0, and Webform 6.2@beta5.
They are not present on the production branch using the custom theme, Drupal 9.5.7, and Webform 6.1.4.
Perhaps not helpful, but how are you accessing the recaptcha response token? I can't figure that part out.
I understand this may not be the appropriate forum for this but I have not seen OP post it elsewhere and I believe I found a solution.
After creating a computed twig element which returns an email address based on a condition, in my case the page url, I modify the email handler to use a "Custom To email address...". I use the token of the computed field as the custom email, but append the token with ":raw". For example: [webform_submission:values:computed_email_recipient:raw]
Yes it does, thank you for your reply.
I somehow assumed that all keys had to be lowercase and totally missed the examples provided with each pattern.
CamelCase aside, is there an out-of-the-box way that Webform can post data with a custom structure (nested objects) while also still including arrays? Or, would this need to be done with some kind of custom handler?