Steps to reproduce:
(1) On a Drupal 7 installation
(2) Navigate to the content listing page
(3) Select some node(s) to export
(4) Use the "export nodes" action from the drop down list
(5) Click the download file button\
(6) Result: The file is empty.

CommentFileSizeAuthor
#5 blank_file_issue.diff4.12 KBdanielb

Comments

danielb’s picture

Hmm you're right.... but I remember fixing this at some stage.. hmm...

danielb’s picture

#1100024: Notice: Undefined variable: nids in node_export_gui() + Undefined variable: code_string in node_export_gui()

I need to figure out if the work I did in that issue has been lost somehow, or if this is a separate bug.

danielb’s picture

ok using latest dev I can't even get to the node export pages using this technique... :/

It's driving me crazy... choosing 'node export' from operations and submitting the form gives me a 404....?

danielb’s picture

ohhhhhhhh

lol I made a function that inadvertently was a hook :/

danielb’s picture

StatusFileSize
new4.12 KB

Alright I've updated that and committed. I'm just going to leave a diff here in case I need to remember what I did.

danielb’s picture

Status: Active » Fixed
danielb’s picture

ps, this code will have to change completely again to fix #1174990: Allow Node export to work with Batch API

dddave’s picture

Status: Fixed » Active

This issue is also present in 6-3x.dev.

danielb’s picture

Version: 7.x-3.x-dev » 6.x-3.x-dev
socialnicheguru’s picture

I get this error now.

implode() [function.implode]: Invalid arguments passed in /node_export/node_export.pages.inc on line 331.

Edit:
download to file works when I use the tab on a node.
It doesn't if I use VBO. An empty file is downloaded.

danielb’s picture

I've ported some of the changes over to 6.x, hopefully that solves the empty files issue.

Make sure you don't use VBO with the 'batch' option enabled, it won't work.

socialnicheguru’s picture

Are you going to have a new release?

There is a new release and the download seems to work.

danielb’s picture

Status: Active » Fixed

The changes will be in the development snapshot and will appear in the next release.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.