CSV unrecognized

This looks to be a bug. The number of columns in each row doesn't match. Not sure why, since I deliberately designed it to adjust these, but apparently that isn't what it's doing.

Hi there,

I'm getting the same issue, i.e. download the csv of node_export from one site and import into another. The format is the same.

I see in the export CSV creation most field enclosures are single quotes but for body it's double quotes? I think initially my spreadsheet tool (Numbers) is getting confused by this and I'm seeing single quotes in fields, like content type.

That all said though, tracing the error that appears in the code, the issue appears to be due to import function misunderstanding the format required for the operation?

I checked and originally I didn't have CSV enabled on the import site, but this is now on and the problem persists.

Any ideas?

With regards to exporting all content from a type, you can install CMF (http://drupal.org/project/cmf) which provides the ability to set how nodes appear on the filter output, then use update options to export. Or I suppose you could have a play with Views and VBO.

Thanks,
luke

I see in the export CSV creation most field enclosures are single quotes but for body it's double quotes? I think initially my spreadsheet tool (Numbers) is getting confused by this and I'm seeing single quotes in fields, like content type.

The single quotes around things are not part of the CSV format, per se, but were intended to represent that the data was a string to begin with. They SHOULD appear with single quotes when viewing in a spreadsheet. I suspect this actually has little real value and just confuses people, so maybe that needs to go.

- It would be a problem when trying to distinguish the values TRUE/FALSE/NULL with strings that literally say 'TRUE' etc... during the import. Perhaps for these - this needs to remain.

If a value has double quotes, that is part of the CSV format, and it means that the value contains the value delimiter (,), or the record delimiter (CR LF), and the double quotes are used for escaping purposes.

I've changed how CSV code is composed, and committed it. It seems to work so far, but more testing is needed.

Hi danielb,

Thanks for the prompt actioning of this, I've had a little play. I didn't want to update to latest dev and instead just chucked in the changes you made for the CSV module only.

It's exporting very nicely now, I've tested it with node_import and the columns etc all match up and the data is being parsed properly within spreadsheets software and automatically in node_import. So not extra tidying is required which is great!

One issue I have is that the taxonomies are exported separately as individual terms, ie not within their vocabularies. Plus they are tids and not term names, is this intentional for node_export:import or just not been looked at yet? If the latter then I might have a look at this in order to get it working for node_import.

Thanks,
luke

Good to hear.

I am unsure about the taxonomy stuff but it is probably consistent with the data in every other format, so perhaps a new issue for that would be better.

this is still happening with CSV files in 6.x-3.2.

According to #7 it was resolved.
If you are experiencing a problem you should start a new issue with a more verbose description and steps to reproduce including which modules from this project you have and what settings you have enabled.

created new issue #1455690: cannot import CSV file or code