CSV Export not respecting Pager

pschopf - March 31, 2008 - 16:27
Project:Views Bonus Pack
Version:5.x-1.x-dev
Component:Views Export
Category:feature request
Priority:normal
Assigned:Unassigned
Status:postponed (maintainer needs more info)
Description

When I use the CSV export on a view with many rows, I only get the first page of results in the .csv file, regardless of which page I am looking at. For now, I am disabling pager, but this will be horrendous when the table gets very large.

Is there some argument handling text that need to be added to the view? or is this a bug?

#1

dman - December 24, 2008 - 00:43
Category:bug report» feature request
Status:active» postponed

I haven't encountered any use cases where I'd want paging in my CSV files. Sounds a bit tedious to me - complete dumps are much more useful.
But I guess it could be added in with a medium amount of work. If someone really thinks it's worthwhile.
Seeing this is an old request with no follow-up, I'll flag it down as postponed - a maintainer can "won't fix" if they prefer...

#2

neclimdul - January 7, 2009 - 07:41
Version:5.x-1.2-alpha1» 5.x-1.x-dev
Status:postponed» postponed (maintainer needs more info)

I'd need more information but its likely that attached feeds do not respect the pager. Are you using the attached feed method or the page style?

#3

emdalton - June 19, 2009 - 18:03

One circumstance in which one might want to use the pager is when the csv export is timing out and downloading incomplete data. For example, I can only export about 700 rows of my view before it quits. If I could set my pager to 500 rows per page and export each page separately, I could ensure that I capture all rows and then merge them later.

#4

peamik123 - June 29, 2009 - 19:20

I agree with emdalton. We also could do with paging support enabled in order to download just the page being displayed, but also retaining the capability to download the full set via another feed definition if possible. We too have the situation where there could be a lot of data to download, so reducing it by paging would be a distinct advantage.

I did wonder if there was some kind of argument definition required on the feed in order to get the paging processing going, because it only ever downloads the first page for me as well (this is what psychopf reported above). But I can't find any evidence of any way to use arguments to specify the required page. Has anyone else noticed anything significant in this respect?

Neclimdul - what further information do you require in order to recreate this problem? It seems to be very well defined to me.

 
 

Drupal is a registered trademark of Dries Buytaert.