Unrecognized field: A request for item wc_post_id_XXX contains unrecognized fiel
-
HI,
when i make some changes in the product in woocommerce and update the same product I’m getting this message in the logs for every product and variation created in facebook
{“warnings”:[{“message”:”Unrecognized field: A request for item wc_post_id_XXX contains unrecognized field additional_variant_attributes”}
This causes an empty dropdown box in the facebook product page with n possibility from choosing a different variation!
i already delete de plugin, delete the integration, delete de catalog in facebook, try to make all from the beggining but i still getting this messages.
Thansk in advance for your time
-
Hi @voxoff,
Thanks for reaching out about Facebook for WooCommerce! I’ll be happy to help.
As a starting point, could you please confirm which version of the plugin you’re running? If you haven’t yet updated to the current version (2.1.4), could you please go ahead and run the update and let us know if this is resolved in this version?
Thanks,
Jennifer
Hi , yes a have the last verion of the plug in.
Can you explain me how the plugin manages the csv feed, i see that the feed is generated every 15m but a dont see it being uploaded to facebook catalog.
when i make changes in the products they are updated directly and then i have this messages in the log.
`11-11-2020 @ 17:47:04 – Response
Response
code: 200
message: OK
headers: Array
(
[expires] => Sat, 01 Jan 2000 00:00:00 GMT
[content-type] => application/json
[facebook-api-version] => v7.0
[x-fb-request-id] => xxxx
[strict-transport-security] => max-age=15552000; preload
[x-fb-trace-id] => xxxxx
[content-encoding] => gzip
[x-fb-rev] => 1002959944
[cache-control] => private, no-cache, no-store, must-revalidate
[vary] => Accept-Encoding
[pragma] => no-cache
[x-business-use-case-usage] => {“xxxxxx”:[{“type”:”ads_management”,”call_count”:1,”total_cputime”:1,”total_time”:1,”estimated_time_to_regain_access”:0}]}
[access-control-allow-origin] => *
[x-fb-debug] => xxxx
[date] => Wed, 11 Nov 2020 17:47:05 GMT
[alt-svc] => h3-29=”:443″; ma=3600,h3-27=”:443″; ma=3600
[content-length] => 271
)
body: {“handles”:[“xxx”],”validation_status”:[{“warnings”:[{“message”:”Unrecognized field: A request for item wc_post_id_1227 contains unrecognized field additional_variant_attributes”},{“message”:”Unrecognized field: A request for item wc_post_id_1228 contains unrecognized field additional_variant_attributes”},{“message”:”Unrecognized field: A request for item wc_post_id_1229 contains unrecognized field additional_variant_attributes”}]}]}The solution for me is manually upload the csv to the catalog feed in catalog manager data feed and then sync the catalog in the plugin option again!
Thanks for your help!
Hi @voxoff,
Thanks for sending that additional information. The feed file method of syncing products to Facebook has been replaced in V2 with the API method. While the feed file can still be used as a backup, the API should be the primary method for syncing.
I also checked with my team on this message that you’re seeing:
{“warnings”:[{“message”:”Unrecognized field: A request for item wc_post_id_XXX contains unrecognized field additional_variant_attributes”}and it looks like a couple of other users have reported a similar error as well. Our engineering team is taking a closer look into this. As soon as they’ve had a chance to do so, I’ll let you know what I hear back.
Thanks,Jennifer
Hi @voxoff,
It looks like the “additional_variant_attributes” field that this error is referencing is now “additional_variant_attribute” (without the s), following some changes that Facebook has recently made on their end. Their team is now aware of this issue and is planning to roll out a fix for it in the next day or so. I would recommend trying a sync again tomorrow (and again over the next several days) to see if the problem is resolved.
After you’ve been able to try this out a few more times, could you please let me know if you see any changes?
Thanks,
Jennifer
Hi Jennifer, ok i will monitor this issue and i will get back to you!
Thanks
Hi @voxoff,
Sounds good! Please do let us know what you find and if there is anything else that we can help with in the meantime. 🙂
Thanks,
Jennifer
Hi @jenskyverge i can confirm that the error message of this post is now gone! but…
Why your engineers are using the slug of the attribute instead of the name? this causes that in the front end you will se the slug and not the name, let me explain…
this is the log:
[variants] => Array
[0] => Array
[product_field] => custom_data:dimensions
[label] => Dimensions (cm)
[options] => Array
(
[0] => 30 x 40
[1] => 70 x 100
[2] => 50 x 70and because they are passing the slug (dimensions) instead of the name (Dimensions (cm)) in the [product_field] => custom_data:dimensions this happens https://snipboard.io/D1kJSo.jpg
and in the facebook page of the product you will se this: https://snipboard.io/cTIWE4.jpg
I managed to manually change this on the csv: https://snipboard.io/bJqxBM.jpg
and manually uploaded and it works https://snipboard.io/2mc9Rs.jpg
you can see the change in the facebook product page https://snipboard.io/iRxG9X.jpgBut now every time you update a product it will change because you solve the problem updating this field.
Please talk to the engineers because this is certainly something really easy to change and have a huge impact in the UX/UI of the user…
Hope i make myself clear…
Thanks!
Hi @voxoff,
So glad to hear that the error message is no longer appearing!
I will certainly run this by our engineering team. In the meantime, we did just release a new version that included an update to the field name and format for additional_variant_attribute – could you please try updating to this version (2.2.0) and let me know if you are still seeing the same thing there?
Thanks,
Jennifer
@jenskyverge is because i update to the version (2.2.0) that the error message is no longer appearing! 🙂
Thanks for your help! please try to pass this trough!!!
Hi @voxoff,
Great, I’m glad to hear that the original issue is fixed now! Regarding the second issue that you mentioned, I will certainly run this by our engineering team. If there is anything else that we can help with in the meantime, please don’t hesitate to reach out.
Thanks,
Jennifer
Hey @voxoff,
Marcus here, stepping in from the support engineering team to take a look at this with you.
It sounds like you want to have the full label value for the custom attribute data. The reason we use the slug is that the plugin builds an array first before it reformats it into what you see in the logs. During this time, there is a “custom data” array with these values and they are paired up with the slug as the key and the attribute as the value. Changing this to use the label would end up with the label as the key, which cannot be relied on to be valid. Example:
Array ( [title] => Variant Label Test [description] => Variant Label Test [image_link] => https://placeholdit.imgix.net/~text?txtsize=33&name=Variant%20Label%20Test&w=530&h=530 [additional_image_link] => Array ( ) [link] => https://example.com/product/variant-label-test/?attribute_dimensions-cm=30x40 [brand] => My Great Blog [retailer_id] => wc_post_id_150 [price] => 10 USD [availability] => in stock [visibility] => published [sale_price_effective_date] => 1970-01-29T00:00+00:00/1970-01-30T23:59+00:00 [sale_price] => 10 USD [custom_data] => Array ( [Dimensions (cm)] => 30x40 ) )In this case, it might work, but we can’t be sure what content is in the label at any time. It could include apostrophes or quotes that would break this.
I tried to find a filter for you in the plugin so that you could do this since your labels do not include these. I’m afraid I was unable to find a filter in the plugin where this could be possible.
I’ll make sure to share this with the product and engineering teams to see if this is something that we can add in a future release. Please make sure to keep an eye on the plugin’s changelog to see if this gets added!
Are there any other questions I can answer for you? Please don’t hesitate to let me know.
Thanks,
MarcusHi @voxoff
We haven’t heard back from you in quite some time. We’ll mark this as solved, however, if you’re still having trouble after following the above recommendations please open a new thread.
The topic ‘Unrecognized field: A request for item wc_post_id_XXX contains unrecognized fiel’ is closed to new replies.