thanks for putting this module together, I really hope I can get it to work.

Right now, I am getting a 500 error whenever I try to download any node in any format.

All the node export modules are enabled and I am logged in as user 1.

Any ideas?

Thanks

Comments

toddgeist’s picture

toddgeist commented
Title: Download file result in 500 error code » Download file result in 500 error code and Duplication of Node

I just noticed that Download File also duplicates the node that I am attempting to export.

?

toddgeist’s picture

toddgeist commented

Looking at this some more. Both Download File and Push result in the same thing; a new window gets opened with the the same url in both cases.

node/5352/node_export/serialize?q=admin/content/node_export_push

Why is this? Why is Download file bringing up the same link as Push.

Both are resulting in an error 500

Todd

toddgeist’s picture

toddgeist commented

So even trying to use feeds interface I get the same error. There does not seem to be anyway to get this to work :-(

danielb’s picture

danielb commented

Sorry I'm having trouble following you.

I just noticed that Download File also duplicates the node that I am attempting to export.

I have no clue what 'duplicates the node' means in this context.

And then out of the blue you're talking about node_export_push ?

??

Might wanna disable any node_export_* modules that you don't specifically need.

danielb’s picture

danielb commented

You know I don't think I've ever turned on node_export_push, so it might have some side effects that I don't know about. I didn't even remember that module existed because it is not listed in the same group on the module page.

Can't test it at the moment, my dev site is sick.

danielb’s picture

danielb commented
Category: support » bug

I can confirm that enabling the node_export_push module causes file downloads to fail with the error:

Fatal error: Function name must be a string in /sites/all/modules/node_export/node_export.module on line 517

danielb’s picture

danielb commented

Now I understand what you were saying, this is utterly "wtf!"

danielb’s picture

danielb commented

Looks like two things are going on
- Node export push port to 7 doesn't work
- Node export push in both versions does not contain a setting to enable/disable it.

This module should probably be removed and code integrated into the main module as a 'delivery' method. At least for Drupal 7.

danielb’s picture

danielb commented

I will make the changes for Drupal 7, but for people experiencing this problem in Drupal 6 my advice is to simply disable node_export_push if it isn't required.

danielb’s picture

danielb commented

On second thoughts, after having developed improvements to the functionality just now, I am removing this functionality entirely.

I can justify that publicly by stating that it doesn't align with the goal of 'node export', and suits the http://drupal.org/project/deploy module better.

But there is also a much more important reason that I'm not prepared to discuss until some time in the future.

Perhaps we can revisit this one day, but for the moment, it would be irresponsible for me to support this functionality.

danielb’s picture

danielb commented
Status: Active » Closed (fixed)

Please avoid reopening this issue, and commenting on this topic for a few months.