Importing Taxonomy Not Provided As String

Created on 9 June 2018, about 6 years ago
Updated 14 June 2023, about 1 year ago

I have been testing some importing via Feeds with Feed Tamper. I have used this successfully many times using Drupal 7 -- but for the dev-release for Drupal 8 is tossing this error:

Drupal\tamper\Exception\TamperException: Input should be a string. in Drupal\tamper\Plugin\Tamper\Explode->tamper() (line 80 of /modules/tamper/src/Plugin/Tamper/Explode.php).

I am looking at the exports and have tried comma separate, tabbed, and pipes. Nothing in the data should cause this (that I can tell).

πŸ› Bug report
Status

Needs review

Version

2.0

Component

Code

Created by

πŸ‡¨πŸ‡¦Canada Shane Birley

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 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 about 1 year ago
  • πŸ‡³πŸ‡Ώ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

Production build 0.69.0 2024