- Assigned to Grimreaper
- Status changed to Active
almost 2 years ago 9:45am 17 February 2023 - Issue was unassigned.
- Status changed to Closed: cannot reproduce
almost 2 years ago 10:12am 17 February 2023 - 🇫🇷France Grimreaper France 🇫🇷
Hi,
I have tested with:
- a node with Metatag with and without values,
- with and without the Metatag field enhancer enabled on the server website.Also, there seems to be a bug in JSON API Extras, you have to save a resource override twice to have configuration saved and do not forget to clear cache after applying the field enhancer.
Everytime I have been able to import the entity, with or without the meatags depending if the field enhancer was enabled on the server website, but no fatal error.
Like @gayatri chahar had written. This needs clear steps from a frest install to reproduce.
- 🇺🇸United States bwoods
I just ran into this issue after using Entity Share for a couple of months without any issues. It turns out the problem was that I removed a field that's part of an unrelated contrib module from the content type on the Server. Even though that field was not being used, it was creating a record in the field table (previously, since the field was left blank, it wasn't creating any records). JSON:API was picking up this record as part of the node, and because it's a special field, it could not process. To fix this, I had to re-enable the field on the form display screen, edit the node to leave the field blank, and that deleted the record in the field table. By doing this, Entity Share began working again. This seemed rather bizarre, but hopefully this troubleshooting will help someone else!