Jump to:
| Project: | Node import |
| Version: | 6.x-1.0-rc4 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
| Issue tags: | carriage return, line break, linebreak, mac, paragraph break, return |
Issue Summary
I tried to an import Ubercart product into Drupal 6.12, and things were going reasonably fine. It basically works with the known issue of not getting taxonomy terms in and a few other little things.
Things went strange when I tried to import several record in one go, and that seems to have to do with the fact that I am on OSX, where a new line is encoded as linefeed only. Interestingly the first line containing the field-names is separated correctly, but any linefeed after that is ignored (so all records/data after the first record are entered into the last field of the first record - which creates an error).
When I saved my CSV-file with a text-editor that can create Windows line-breaks (linefeed+carriage return) things worked as expected and the records were recognized/separated correctly.
I tried using another record separator (;) and entered it manually into my file, but that didn't help.
I also tried writing "Linefeed" into the "other-separator" field on the data-structure-definition pane, and that didn't work either.
Would be nice to have that fixed for non-Windowsers... :)
Best
Rainer
Comments
#1
I have the same issue. Hopefully this can be addressed in the next release candidate (whenever that happens).
#2
I'll throw in my 2 cents for this request. I spent a couple of hours this morning tinker with an import file before I finally found this post ( I am on OS X). Opening my csv in a text editor and saving with Windows line endings fixed my issue.
It's not a huge deal but it's a bummer for such a seemingly insignificant setting to bomb out the import process.
All-in-all a wonderful module though. I was able to import 3900 nodes in a single import! Hooooray!
#3
Yes, this is still a problem. These comments got me to the workaround: If you are using Word for Mac to save as a csv, save as "text only with linebreaks (MS-DOS)". In excel, I successfully used "CSV (Windows)".
#4
Fixed in -dev. Will be added to -rc5.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.
#6
Is it possible to make the fix available as a patch?