Needs work
Project:
Feeds
Version:
8.x-3.0-alpha6
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Nov 2019 at 05:14 UTC
Updated:
11 May 2022 at 09:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
dariogcode commentedBasically the patch check if the "violation" is made by a field, and if the field is in mapping targets.
Tested againts 8.x-3.0-alpha6
Comment #3
dariogcode commentedComment #4
megachriz@dariogcode
Thanks for the idea. In some cases this could be useful. In other cases though this can cause less user friendly SQL errors, like the one in the automated test. So with your patch, if someone forgets to map to node title, this will result into a SQL error.
I know I implemented this in the D7 version but I think D8 is more strict in this regard. A possible solution to overcome the most likely SQL errors, would be to only skip configured fields. So if the error is on a base field of an entity, we let the validation fail even if not mapped to that base field.
I think ideally Feeds should warn you if you didn't map to all required fields on the mapping page, but that would be food for an other issue.
Coding standards
Your patch contains some coding standard issues, see https://www.drupal.org/pift-ci-job/1460628.
Comment #5
mehul.shah commentedSubscribing to this issue. It should only validate the base entity fields and configured fields.
Comment #6
socialnicheguru commentedThis worked to deal with this issue:
https://www.drupal.org/project/feeds/issues/3062232#comment-14408592
Comment #7
megachrizClosed #3209176: Deleting a taxonomy term not associated with a feed type prevents nodes from updating as a duplicate.