- Issue created by @JonathanWZ
- Status changed to Needs review
over 1 year ago 11:13am 9 October 2023 - last update
over 1 year ago 105 pass, 5 fail - πΊπΈUnited States DamienMcKenna NH, USA
This is a new bug, I haven't come across it before.
I guess the internal API needs to be tweaked to allow the values to be passed into the field as an actual array, instead of a serialized array.
Does this help?
The last submitted patch, 2: metatag-n3392610-2.patch, failed testing. View results β
- Status changed to Needs work
over 1 year ago 7:10am 12 October 2023 Hello @DamienMcKenna
thank for your response :)
Your patch not work but I've indicated a wrong version. It's not "2.0.x-dev" but "2.0.0" sorry for this error.I'll try to propose a patch soon ;)
Hello @DamienMcKenna
I found a solution by forcing the "field_content_metatag" field to JSON data in "JSON:API Resource overrides"
Then when I call it, I have to remove the "value" key.{ "data": { "type": "node--content", "id": "uuid", "attributes": { "title": "Node title", "field_content_metatag": { "title": "customTitle", "og_title": "customOgTitle" } } } }
and it's work