Closed (outdated)
Project:
Feeds
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Apr 2011 at 09:54 UTC
Updated:
9 Feb 2026 at 15:22 UTC
Jump to comment: Most recent
I had an issue with a whitespace terminating a column name in CSV parser
While parseHeader method is trimming the column name,
getSourceElement method is not.
In this case no mapping is done on the column value.
I would propose to trim both as described in the patch
| Comment | File | Size | Author |
|---|---|---|---|
| FeedsCSVParser.inc_.patch | 682 bytes | marco.giaco |
Comments
Comment #1
paolomainardi commentedSubscribe
Comment #2
johnvThis is still true.
Comment #3
lyricnz commentedI don't see any harm in this, even if it is only needed for "malformed" data.
Comment #4
twistor commentedAHHHHHH
The fact that the CSV parser lowercases keys has been the bane of my existence. Adding yet another transformation will make me bonkers. Either we do this to everything, very likely not possible, or none. Or, someone comes up with a fancier way to retrieve the key from an item somehow using the parser.
Very tempted to mark this as won't fix.
Comment #5
bluegeek9 commentedDrupal 7 reached end of life and the D7 version of Feeds is no longer being developed. To keep the issue queue focused on supported versions, we’re closing older D7 issues.
If you still have questions about using Feeds on Drupal 7, feel free to ask. While we won’t fix D7 bugs anymore, we’re happy to offer guidance to help you move forward. You can do so by opening (or reopening) a D7 issue, or by reaching out in the #feeds channel on Drupal Slack.
If this issue is still relevant for Drupal 10+, please open a follow-up issue or merge request with proposed changes. Contributions are always welcome!