Attempting to use a view, getting the following error:

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

And the following warning shows up in the logs:

user warning: Table 'views_data_export_index_XX' doesn't exist

It only occurs with 'Batched Export' = Yes.

Previous discussion of this bug was going on in #1005842: fatal error: non-object, starting at #4

Comments

steven jones’s picture

steven jones commented
Priority: Normal » Critical

Need to fix this.

jamsilver’s picture

jamsilver commented
Status: Active » Closed (duplicate)

Almost certain that this is a duplicate of http://drupal.org/node/1008240.
The problem is that we save the serialized view away in a database field that is too small to contain it and so it gets truncated, so when we try to de-serialize it that fails.

There are patches posted in the other issue which I have now applied to all branches. Once you've updated your code you'll need to run database updates, or just disable, uninstall and re-enable the module.

Set this back to me if the issue still doesn't seem fixed.

jvdurme’s picture

jvdurme commented

Also still receiving this error with latest views (6.x-dev) and latest views data export.

PHP Fatal error: Call to a member function set_display() on a non-object in /var/www/switch/snpeffect/sites/all/modules/contrib/views_data_export/views_data_export.module on line 147, referer: http://snpeffect.switchlab.org/batch?op=start&id=12

jvdurme’s picture

jvdurme commented
Status: Closed (duplicate) » Active

Reopening because this bug cripples the whole idea of scaling to large datasets...

penyaskito’s picture

penyaskito
he/him
Primary language Spanish
Location 🧑🏽‍🌾 Seville 💃 Andalusia, UTC+2 🇪🇺
commented

I had the same problem "PHP Fatal error: Call to a member function set_display() on a non-object in views_data_export/views_data_export.module on line 147, referer: /batch?op=start&id=12"

In my case was that I had imported a view that uses views_data_export but without views_data_export being installed and enabled. Just for the record.

steven jones’s picture

steven jones commented
Status: Active » Closed (duplicate)

Really don't see how this could still be an issue. Please make sure that you've run updates, and if it still doesn't work, please let me know what the DB schema of the views_data_export table looks like,