"There are no new nodes" message when import file has Mac EOL format [solved]

I'm seeing the same behavior. I even downloaded the template produced by the input form and added one line of content and tried to import. I don't get any errors, just the same "There are no new nodes".

Subscribing.

@dotman - Ever find the solution to your problem?

Poieo: I had the same problem, and as dotman noted, changing the line break settings of the file to "Unix (LF)" seemed to solve my problem. I'm not sure if this always has to be LF or if the line break type has to match that of the server's system.

More info on Wikipedia: Conversion utilities

Also, most GUI-based text-editors will give you some kind of line-break setting option in the "Save as..." dialog. I used Text Wrangler.

I want to import some "pages" als Nodes from a csv-file. In the body of the resulting pages, there must be some commas in the german sentences.
So i think, i need the sign " for text separation.

Please tell me, how i can import a CSV-file like:

title,body,guid
"Welcome","<p>Hello,</p><p>nice to meet you, here on our homepage.</p><p>You want more Info?<br>klick on: <a href='about'>About</a> or <a href='we'>We</a>.</p>",1001
"About","<p>We, <strong>Name1</strong> and <strong>Name2</strong>, want to do something.</p>",1002
"We","<p>Our company 'Ourname Ltd.' will ....</p>",1003

Please help me.

Thanks

[Update]
The solution is:
I must activate the option "Import on submission".
[/Update]

@wusel - I believe that should work, but if you're having trouble you need to create a new issue, as your problem does not relate to the original issue in this thread. Thanks.

Subscribing, having the same on Mac, when I try it on Wordpad (Windows) I got some results..will investigate more..
greetings, Martijn

please look at my update in comment #5

I had the same issue. I opened up the CSV file that was saved in Excel in BBEdit, changed the File Options to "Unix", saved and uploaded-- done.

sub

I had the same "no new nodes" error on import, and changing the line endings to UNIX (I used Notepad++ in Windows) fixed the problem. The import csv was originally created on a Mac.

Should this be a feature request/bug report to "Support Mac EOL Format"? Or at least give a better error message; without this issue page I could have spent hours debugging the import.

Setting this back to active for now, since @wusel closed it based on a separate issue.

@goodeit Thanks for saving me a headache! #11 worked for me as well.

It is like http://drupal.org/node/1285276#note2 for the Migrate module:

The line-ending-char(s) depend on the type of the operating system of the www-server:
If you are using a Linux-Server, please use only LF at the line-end of the CSV-file.
If you are using a Windows-Server, please use CR+LF at the line-end of the CSV-file.
If you are using a Mac-Server, please use CR at the line-end of the CSV-file.

When the CSV-file is in "UTF8 with BOM"-format, then the import of special characters (letters like ß, ö ,ü, ä, Ö, Ä and Ü, non-ASCII-signs) is without problems.

I think: this should be dokumented in the drupal.org-Online-Documentation of Feeds and in the help-page of the feeds-import-dialog on the help-sub-page.

Note: a patch-file also needs the same line-ending-char(s), depending on the type of the operating system of the www-server.

Another solution for fellow mac users

File to "save as" windows format .csv

That fixed the problem for me.

The "save as windows CSV" worked for me. Thanks!

"save as windows CSV" worked for me as well. muito obrigado!

*bangs head against table*
I spent hours to find that the line endings were wrong!

Please look at http://drupal.org/node/622710#csv

Considering this thread, as well as this one... http://drupal.org/node/1464008 - I think that indicates that enough people are not finding the description of the line-feed char requirements to warrant inclusion of it (the description) in other places in the documentation. I, for one, would never think of looking in the "Feeds Glossary" for information on file format requirements.

And adding "(check documentation regarding line-feed characters)" to the "No new nodes" error message would be nice as well.

A few minutes on your part will save others countless hours of searching for a solution to this "issue".

Could we not get a function built into the import that checks the linefeed and converts is as necessary?

for example: (from http://darklaunch.com/2009/05/06/php-normalize-newlines-line-endings-crl...)

function normalize($s) {
    // Normalize line endings using Global
    // Convert all line-endings to UNIX format
    $s = str_replace(CRLF, LF, $s);
    $s = str_replace(CR, LF, $s);
    // Don't allow out-of-control blank lines
    $s = preg_replace("/\n{2,}/", LF . LF, $s);
    return $s;
}

I realise this would probably add a good bit of overhead to the import, but it would avoid people having this issue.

Not sure where this would fit into the import process, though.

I don't know, whether this works for Feeds, but for the module "Migrate" this voids the known line ending issue (e.g. look at "Invalid data value" on http://drupal.org/node/1152158 ):

    ini_set('auto_detect_line_endings', TRUE);

Good luck!

Wusel

Subscribing. Would like to see this fixed. I have end users who are importing users and getting CSV files from 3rd parties. I have no control over how the original source saves the CSV.

I ran into this problem where I was importing nodes that were all unpublished. Tried everything and it wasn't until that I started marking them as published that they would finally import.

I am still having issues with this.. for XML files. I have tried the various methods. How can I, on the command line of the Linux server, verify what the line endings are??

Eric

Hi Setting this to active because I think something like #22 needs to be added.
Intuitive this seems right. I have constantly problems with line items. I just don't know which are correct anymore..
I am sorry if I put this wrong into active again.

Link http://drupal.org/node/1705850 is not working..
greetings, Martijn

New link at #1189682-22: "There are no new nodes" message when import file has Mac EOL format [solved], text has been moved

Hi,
So the setting in #22 should be set in settings.php, thats it?, than there is no lineitems discussion more and will also other types than unix be possible?

Greetings, Martijn

No, that may show problems with other modules, I don't know.

But for the module migrate, we use it only in the specific classes. You can see e.g. at http://drupal.org/node/1285276 ("Import new users and their Profile2 fields from one CSV file") we only use it in the
abstract class Wusel_Basic_Migration extends Migration { ... }

Good luck!

Are there any other instances where the "There are no new nodes" issue can occur? I have stripped down my XML file to 2 items and I am beginning to suspect that its not the EOL issue. I've even stripped out all the EOLs and still no luck.

I'm thinking of starting a new issue.. Should I?

Thanks,
Eric

Hi,
Aitala, I have exactly the same situation using all feeds depending modules like xpath_xml in latest .dev.
Trying all sorts of EOL with nodepad++ TextWrangler on mac. Setting Lineendings to Unix/ Mac, utf8 type...
No feed will import. I use the commerce_feeds importer and it says constantly: "No imported items.".
No debug messages, no errors, just no trigger to import the feed. It is driving me crazy!
Greetings, Martijn

I actually re-edited the .xml file with vi on the server's command line and had no luck either.

E

Please, please do also this: https://drupal.org/node/1464008#comment-5796476
Not to select "Import on submission" took me 3 days of thinking it was about the EOL, utf and all other stuff..

Now at least I have the message "There are no new commerce products."
Which is not true....because it is a new ID-nr, but I am one step further...how to debug this sort of stuff please?

Greetings, Martijn

Box is checked - I have done this import successfully in the past, so I know it should work. The site has been updated since the last successful import, so the issue may lie there which is why I may open a new issue.

E

Hi Aitala,
Yes I think adding a new issue is the best. I got whatever I do:

There are no new commerce products. 

No reporting of errors, no showing what the system sees only that sentence while I did add new Commerce Product with new ID (GUID, etc.... Grrr.

Greetings, Martijn

Posted new issue with as many details as I can think of at: https://drupal.org/node/2096763

Eric

At some level, I fixed my issue ( https://drupal.org/node/2096763 ) but it looks like its some sort of issue with the current versions of D7, Entity, Feeds, Feeds XPath Parser... and maybe other modules.

Basically I had to revert my site back to Dec 2012... not sure where the issue really lies, but it seems to be some sort of module / core interaction...

E

I add a hint

As far as I can tell the ParserCSV.inc library already has this on line 86:
ini_set('auto_detect_line_endings', TRUE);

I'm still having trouble with feed import on a Windows Drupal installation - seems to work fine for me on Linux. Will post any solutions I find that may help.

I developed a module to help with debugging imports: Feeds import preview allows you to see what your source looks like after it has been parsed.

thanks MegaChriz for this module it's helps a lot

I was able to get the import to work by replacing improperly formatted quotations ("). e.g. search an replace “ with ".