Unable to use pagination when using views_pre_execute function

Hi there,

I recently had to upgrade views from version 3.5 to 3.10 because of the recent security vulnerabilities (See: https://www.drupal.org/node/2424403)

I have several custom modules using the views_pre_execute function to manually override some very slow SQL queries.

In all cases I was not specifying a limit in the function - the SQL generated in the preview would still use whatever was set in the configuration. This was useful for views that have pagination because views needs to reference what is set in the config.

After upgrading to Views 3.10 however, I find that none of my views have limits. I therefore had to go through and set them in each view manually. This is fine in all cases except for those views with pagination, because whatever function is creating the pagination isn't able to reference the limit that I'm setting in the module. I'm having to make do with a extended finite list now :(

So it seems that views_pre_execute no longer offers an either/or scenario when it comes to limits and pagination. I figured it was worth bringing some attention to this slight oversight? Or was I merely taking advantage of a bug in the first place? In either case, if anyone has any ideas on how this might be overcome it would be most appreciated!

Cheers,

Rob.

p.s.

I wish I could be more helpful about when this change happened. I can only say it must have been at some point between versions 3.5 and 3.10...