Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.When importing a value that is too long for the field a mysql error is raised and importing fails. Perhaps it would be better if the field mapper checked the incoming value against the length of the field and trimmed it to fit?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | feeds-1151438-1.patch | 1.04 KB | jamsilver |
| #1 | feeds-1151438-1-drush-make.patch | 694 bytes | jamsilver |
Comments
Comment #1
jamsilver CreditAttribution: jamsilver commentedPatch attached.
Comment #2
emackn CreditAttribution: emackn commentedI poked this a bit and can't seem to get it working reliably. Also not sure I want to promote incomplete data being pulled into a feed. I feel it might be best to leave this as is for now.
Comment #3
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedI think this should fail an import. You can fix the problem by using the plugin "Truncate" from Feeds Tamper. When the patch from #2379631: field_attach_validate() must be called before programmatic entity saves gets committed, we'll get a better error message for this issue.