I'm currently building a site, and one of the ideas I have for content is to have a couple of hundred nodes which have text and a file attachment. Rather than create them manually through Drupal, I thought that preparing and importing a CSV file might be faster/easier.
Can someone who has used this module extensively advise me:
1)
Given the size of the issue queue, is this module stable enough to use to import a production site?
2)
I suppose that to handle core or CCK attachments, you just put a link to the attachment in the CSV file, and upload the files separately by ftp? Would the files subsequently be 'tracked' by the Drupal file system as if they had been uploaded normally?
3)
For a non-coder like me, would setting up and testing this module take longer than actually just buckling down to work and creating two hundred nodes manually?
Thanks.
Comments
Comment #1
colanSee #1301678: Release Path and Roadmap for Feeds 7.x-2.0 .
I recommend the fora or IRC for support requests as this queue is becoming unmanageable. It's getting too difficult to handle them all. Let's keep it to feature requests, tasks & bug reports for now.
Comment #2
chianti commentedIf this is the case, you should perhaps put a note on the project page.
Then I wouldn't have wasted my time posting my queries here.
I feel that these questions would not be answered in the general forum, so could you point me towards the IRC channel you referenced above? Again it might be a good idea to put it on the project page.
Or alternatively, you could simply just answer the questions! Q1 and Q2 are just yes/no responses. Q3 is just a one liner - 'I have imported over a hundred nodes and it saved me time', or 'I have imported over a hundred nodes and I met with so many problems that it would have been quicker just to create the nodes manually'.
Comment #3
colan(1) You need to do your own QA to determine if it meets your requirements. If so, it's stable for you. If not, it isn't. For widely known problems, refer to the issue I posted above.
(2) No idea personally. I'd recommend trying it. If it doesn't work, try searching the issue cue. I think this question may have come up before. If not, create a new "Feature request" issue dealing exclusively with that.
(3) Possibly, but that's something that you'll have to determine for yourself, or pay a consultant to figure out. You haven't given enough information here to answer that (How much data do your nodes contain? How fast do you type?), and even if you did, I doubt that many folks would jump at doing the research for free. ;) The real answer is, "It depends". See (1). If others see this question, maybe they'll comment on this while the issue's open.
As a general rule, don't post multiple issues in one. Many folks won't bother replying. Keep things separate to keep people focused. Also, always search the queue first before creating new issues. I'm trying to help the maintainers bring the numbers down here, so sorry if my response seemed curt.
IRC: http://drupal.org/irc
Maintainers: Could we suggest on the project page that folks search the issue queue first, and if their support requests aren't already there, they could communicate in IRC or the fora? This should help keep the issue queue from growing too much.
Comment #4
chianti commentedThanks for your reply.
Comment #5
franzFrom my personal experience, warnings on project description don't help that much...