Does not work with data export + paging

I hit this same issue.

I found that it is related to the "Column aggregation row applies to" setting within Format -> Settings.

If you set "Column aggregation row applies to" to "the page shown" then the error goes away. Switching it back to "the entire result set" causes the error to occur.

Is this related to 🐛 Exposed filters aggregation (regression?) Active and is this problem fixed by the proposed patch in that issue?

I ran into a similar error after update to version 2.1.0 - an existing View with aggregator table had a linked Views Data Export. After update, the Aggregator Plus page did not display and the error message about "route does not exist" appeared. It looks like the database update (after running Drush database update) wipes the path?

The update function did not make any database changes - it only changed the datatypes of three configuration variables used internally to views_aggregator. Specifically, routes and all other configuration variables were left unchanged. Only views that used views_aggregator were changed, and only the displays on those views that used these three configuration variables

I would try to re-save your view, and clear your caches, but I don't see how anything the update did could have affected a route anywhere on your site.

What route in particular is it missing? Is it possible for you to compare an export of the old view and the new view and post that here so I can see what changed?

I am hitting this issue too, the patch of issue 3439536 🐛 Exposed filters aggregation (regression?) Active does not fix it.

As stated in the original PR, the issue appears when using a pager.

Hitting the same issue. It's happening because Drupal\views_aggregator\Plugin\views\style\Table::preRender() creates a duplicate and executes it without saving. Down the line, in Drupal\views_data_export\Plugin\views\display\DataExport::attachTo(), $view->getUrl() is called and fails because the attached view doesn't have an ID yet, because it is new and unsaved.

I'm able to fix this in Views data export → by calling isNew() before trying to generate an url. I believe that's the way to go, so I'm moving this issue to that project.

steven jones → made their first commit to this issue’s fork.

There's actually a method on \Drupal\views\ViewExecutable that tells us if there's a URL, I wonder if that's what we need to check here?

@dieterholvoet are you able to test this MR I'm about to open please?