When trying to get Views Data Export to play nice with Dynamic Fields as well as some custom field handlers that reacted to different exposed input, I found that the batch process did not pass the exposed filters along with every batch request. Attached is a patch to fix this.

CommentFileSizeAuthor
#6 views_data_export-exposed-input-patch-removed-1871560-5-D7.patch2.65 KBnbouhid
views_data_export_exposed_input.patch2.5 KBAnonymous (not verified)

Comments

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Needs review

Changing status.

albert volkman’s picture

albert volkman commented
Status: Needs review » Reviewed & tested by the community

This fixed my problem! Thank you!

#1322816: views data export - exposed filters appears to possibly be a duplicate.

steven jones’s picture

steven jones commented
Status: Reviewed & tested by the community » Fixed

Thanks! Pushed into 7.x-3.x and 6.x-2.x

Status: Fixed » Closed (fixed)

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

nbouhid’s picture

nbouhid commented
Version: 7.x-3.x-dev » 7.x-3.0-beta7
Issue summary: View changes

This is giving me problems with an exposed filter of a node field (text list).
It throws the following error:

An illegal choice has been detected. Please contact the site administrator.

The funny thing is that when I removed this patch, it started working perfectly.

if($exposed_input) {
  $view->set_exposed_input($exposed_input);
}

Here is some extra information:

  • My page and export has the same exposed filters.
  • I'm using the 7.x-3.0-beta7 version.
  • I've checked the "Parent Sort" option and "Remember last selection" for the filter .

PS:
Is this line being used somewhere?

$batch['exposed_filters'] = $this->view->get_exposed_input();
nbouhid’s picture

nbouhid commented
StatusFileSize
new views_data_export-exposed-input-patch-removed-1871560-5-D7.patch2.65 KB