I can also confirm the issue. I have a feed set up to import CSV data, with an Explode tamper on a specific column.
When I import an empty or valid string it seems to work fine, but if I import a sheet that doesnt include the tampered column (I don't want to update items with an empty value), I get HTTP 500 during import and the same message as the reporter.
I agree this should be a fix put into the module instead of a custom code snippet.
- Status changed to Needs review
over 1 year ago 2:51am 26 April 2023 - 🇳🇿New Zealand ericgsmith
Linking related issue in tamper module. It seems there is a lot of support to improve the handling of null values. Please see the issue Improve handling of empty data. It would be awesome if that issue could get some feedback.
The change in #14 is essentially part of that issue - I would also welcome that as a standalone patch in tamper module.
- 🇩🇪Germany lissy
A Workarround is, to integrate the Tamper "Skip tampers on empty" and put it before the Explode-Tamper
- 🇨🇦Canada Ron Collins
In case this helps someone else, I got this error when I accidentally selected a mapping for a new blank source instead of a new CSV source.