Thanks for the great work on this module, it is very useful with large node sets.

I had CSV export working great, but for some reason I'm now getting this error:

Fatal error: Call to a member function set_display() on a non-object in /modules/views_data_export/plugins/views_data_export_plugin_display_export.inc on line 189

CommentFileSizeAuthor
#6 fix.1005842.patch1.87 KBjamsilver

Comments

mkennedy2d’s picture

I fixed the problem. My view had another display using views_datasource and once I removed it, the export started working again without any errors.

steven jones’s picture

Oh interesting...

steven jones’s picture

Assigned: Unassigned » jamsilver

James, this bug is coming from your code that does that tricky loading thing that I really don't understand. Are we good to remove it?

mkennedy2d’s picture

I'm seeing this bug again, but several things have changed. I'm now using views-6.x-3.x-dev with views_data_export-6.x-3.0-beta3.

An error occurred. /batch?id=55&op=do Fatal error: Call to a member function set_display() on a non-object in (mysite)/modules/views_data_export/views_data_export.module on line 130

Can't seem to fix it this time. Any suggestions?

johnv’s picture

I have the same error with configuration as in #4.
It only occurs with 'Batched Export' = Yes.
I use 'reverse node reference' in the view. If I clone the display, and remove al 'reverse node references', the error still exists.

jamsilver’s picture

Status: Active » Fixed
StatusFileSize
new1.87 KB

Yeah, that code has been left around for a while and is completely unnecessary. I not sure why it's causing erros here, but the following patch - which I have just applied to the 6.x-2.x and 6.x-3.x branches in cvs - removes this block of code and should therefore fix this issue!

mkennedy2d’s picture

I tried the latest 6.x-3.x with your patch, but the same error from #4 is still occurring . . . wish I had better news.

mkennedy2d’s picture

Version: 6.x-2.0-beta3 » 6.x-3.x-dev

However, I do see a new error:
user warning: Table 'site_478.views_data_export_index_2' doesn't exist

I'm going to disable, uninstall, remove any data_export tables manually, and try again.

mkennedy2d’s picture

I started fresh, reinstalled the module, and can confirm that the table "views_data_export_index_2" is not created when enabled. Should it exist?

jamsilver’s picture

When views_data_export is installed the only tables that should exist are views_data_export and views_data_export_object_cache, the latter of which is just our slightly modified version of ctools_object_cache (modified to remove the per user/session dependency).

Other tables are created as and when a views_data_export display is executed, and are removed after execution has completed. In your case your export had an error during processing and so it's index table was not cleaned up. It can be safely removed.

Now that you've started afresh, is everything working properly?

mkennedy2d’s picture

Thanks, but after starting fresh, I still receive the error in #4.

mkennedy2d’s picture

It's definitely within the batched export, the one segment export works fine.

ezeedub’s picture

Just to confirm, same error here as in #8. (views 3.x-dev and views data export 3.x-dev)

Every time I run the batch, the missing table (views_data_export_index_n) is incremented by one.

cjdavis’s picture

Version: 6.x-3.x-dev » 6.x-2.0-beta3
Status: Fixed » Active

Also seeing the same issues as 4, 5, and 8 - same errors as well.

steven jones’s picture

We'll keep this issue closed I think, and re-test and raise issues in other threads if needed.

steven jones’s picture

Version: 6.x-2.0-beta3 » 6.x-3.x-dev
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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

mikedotexe’s picture

I've got the same issue as #8 and #13 where it says
(views_data_export_index_n) is incremented by one.
Dang, I have this working on my Dev site. Does it mean it's not cleaning up after itself or something?
I'm hoping to have this fixed by next week. Shoot.

views_data_export_plugin_display_export.inc on line 228