I've been trying to work this system all day, and I get nothing except this error.
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /.../batch?id=119&op=do StatusText: Service unavailable (with message) ResponseText: Recoverable fatal error: Argument 1 passed to FeedsProcessor::process() must be an instance of FeedsSource, none given, called in C:\...\sites\all\modules\node_export\modules\node_export_feeds\FeedsNodeExportProcessor.inc on line 33 and defined in FeedsProcessor->process() (line 101 of C:\...\sites\all\modules\feeds\plugins\FeedsProcessor.inc).
I've been trying to export from a D6 site to a D7, to no avail, tried all the formats, even remaking the csv to have the same column order as the D7 version. Now I've seen through testing I can't even export and import a single page from the D7 site to itself without getting the error (although earlier today, exactly this worked fine).
Trying to work this module has taken so long I wish I'd just written a PHP script to put values into the DB myself, complete waste of nearly a whole day. This has been the most frustrating and cumbersome Drupal module I've ever tried to use - how many dependencies? node_import for D6 was way better than this and feeds for people who just want to import content from one site to another. Sorry if I sound bitter.
Comments
Comment #1
danielb commentedlol, well it is still in development, and the Feeds importer you are using is a very recently added feature which I'm not 100% happy with because the Feed's interface makes it difficult for the average user to assign which column goes into which field without understanding the data completely. There are indications in the Feed issue queue that this will improve.
Exporting from D6 to D7 is quite a challenge because of the massive changes in nodes between the two versions. You're better off upgrading the D6 site to D7, then performing the export. But indeed the integration with the Feeds module was intended to provide a way to do this somewhat manually.
I haven't experienced those errors, and I will try to reproduce them.
One...? The UUID module...
Comment #2
finngruwier commentedI've got exactly the same error...
Comment #3
mjcarter commentedThanks for your well-humoured reply @danielb, must say I was in rather a shocking mood at the time I wrote that, I do appreciate your hard work!
I guess when I was talking about dependencies I meant in regard to the job I was trying to accomplish, which also required me to install feeds and ITS dependencies. It certainly seems like the weakness here in more than just that department is with feeds rather than node_export.
In retrospect I would have indeed been better off trying to upgrade my site to D7, but I managed to get the job done using the csv import and then some php/sql insert/update statements to fill out aliases, field data etc, not recommended!
Comment #4
spleshkaSubscribe. I have the same error. If I fix it I'll provide a patch.
Comment #5
tregeagle commentedHi Daniel, Thanks for all your work on this handy module.
I'm unfortunately getting the same problem on a fresh install of Drupal 7.10 using the following modules:
UUID 7.x-1.0-alpha2
Node export 7.x-3.x-dev
Feeds 7.x-2.0-alpha4
I'll try some more troubleshooting this evening and let you know how it goes.
Also gets a mention here:
#1314618: Bug feeds import from node export ?
Comment #6
tregeagle commentedSigh, I think I must be doing this wrong:
I tried using features to import the content types but am still getting this error along with:
I will try some of the pointers you gave here:
#1304942: Node export was unable to recognize the format of the supplied code. No nodes imported.
... when I have some more time.
Comment #7
skinny-misto commentedA quick fix to this that worked for me was:
Open
sites/all/modules/node_export/modules/node_export_feeds/FeedsNodeExportProcessor.incThen have a look at line 33 and change it from:
to
(which passes in the missing parameters that throws that error)
Comment #8
danielb commentedI have committed that change skinny-misto, thanks. That line appears to correlate directly to the error mentioned, so it is very likely your change solves the bug.
Comment #9
twistor commentedI had the same fix. Still not working, but that's a start.
Comment #10
danielb commentedResetting the status as the person who changed it didn't explain why they changed it.
Comment #11
twistor commentedThe reason I changed it is that it fixes the same error as mentioned in the issue summary.
The signature looks like
FeedsProcessor::process(FeedsSource $source, FeedsParserResult $parser_result)FeedsProcessor::process() cannot be called without arguments.
Comment #12
danielb commentedI feel like I'm getting half the story here, but alright.
Comment #13
twistor commentedI have a bit of Feeds experience. I'd be happy to answer any questions you had.