0

I have a search feature based on views (Drupal 10, latest version of Views) with several exposed filters. By default, it displays all results, and users need to use the filters to narrow down their search.There are approximately 5,000 result records.

I added the 'Views Data Export' module to enable users to download search results as a CSV export if desired. However, it isn't functioning as expected.

I successfully created the export view and attached it to the search view. However, I can't configure the pager to "Display all items" to include all records in the export. Setting the pager to "Display all items" results in an error. If I set the pager in the export view to 'Items to display: Full | Paged, 1500 items,' it works fine for fewer than 1500 items. But for more than 1500 items, it produces an error.

When I enable batched export, it generates a link stating 'Export complete. Download the file here.' However, clicking 'here' results in an error [csv.htm file (you can't download this site)].

Does anyone know how to resolve this? Ideally, the export would include only the records currently displayed on the screen after applying the filters.

6
  • You have to tell us what these errors are or we can’t answer the question.
    – mona lisa
    Commented Jul 4 at 2:06
  • This could be a bug rather than a question we can answer: drupal.org/project/views_data_export/issues/3175420
    – mona lisa
    Commented Jul 4 at 2:09
  • The specific errors I'm encountering are: 1.When attempting to configure the pager in the export view to "Display all items," it results in an error.'Error message Oops, something went wrong. Check your browser's developer console for more details.' 2. Setting the pager to 'Items to display: Full | Paged, 1500 items' works for fewer than 1500 items but produces an error for more than 1500 items. 3. Clicking the download link after enabling batched export results in an error message stating '[csv.htm file (you can't download this site)]'.
    – YTDY
    Commented Jul 4 at 2:43
  • That information belongs in the Question. And when it says “Check your browser's developer console for more details”, you have to do that.
    – mona lisa
    Commented Jul 4 at 10:04
  • I have looked at the browser's developer console and don't see the error.
    – YTDY
    Commented Jul 5 at 0:17

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.