Cannot display specific number of items in view

Are you simply using "Display a specified number of items" under Pager to limit the number of results?

I had the same issue on updating to the latest version.
This is due to the new hook implementation in the module file.

/**
 * Implements hook_views_post_build().
 */
function views_php_views_post_build($view) {
  // Clear the limit and offset
  $view->build_info['query']->range();
}

I've committed this to 7.x-1.x-dev:

https://www.drupal.org/commitlog/commit/17562/b348878140641e0eadd6486abf...

Let me know if it works for you.

Great :)

This is still broken as far as I can tell... Limits are being ignored and the query isn't adding LIMIT anywhere.... I'm on 7.x-1.0-alpha2+1-dev

To fix it, I commented out the line containing '->range()' and it went back to working... Why are we nuking this in the first place?

Marking as needs work because it still seems to break any view with a limit.

+1. Breaks both normal views and blocks.
It looks like it displays all the entries instead of paging it, but if you page it you get the same entries all over again.

Thanks fizk, it works for me.
You saved my night ^^

@stevetheboater I thought I published an alpha3 release this morning, but it doesn't seem to be showing up. I'm trying to figure out what's going on...

@RedEight @pandroid Do you have the following code in views_php.module:

function views_php_views_post_build($view) {
   // Clear the limit and offset
   if (!empty($view->views_php) && !empty($view->build_info['query']) && is_object($view->build_info['query'])) {
     $view->build_info['query']->range();
   }
 }

It seems Drupal.org has been having issues building releases today. They said it should clear up within the next hour or so.

The infrastructure team has fixed the releases, you should have access to alpha3 now.

Yes, alpha3 seems to have fixed it.

Will you update also the dev version? I use that and I still have the bug. Thanks!

@smurfxx Thanks, I didn't notice that. I've pinged the infrastructure team.

I thank you too @fizk!

Hi, this is not fixed at all.

I have a Services View and when adding a Global PHP field, the view doesn't work anymore.

Even after alpha 3 views php broke the view completely.

Removing

/**
 * Implements hook_views_post_build().
 */
function views_php_views_post_build($view) {
  // Clear the limit and offset
  if (!empty($view->views_php) && !empty($view->build_info['query']) && is_object($view->build_info['query'])) {
    $view->build_info['query']->range();
  }
}

from views_php.module fixes the issue, so that it's definitely the problem.

While debugging I found that the process list on the db showed that the view wasn't filtering the number of specified items, and instead it was processing all of them, so it's the same problem still...

Thanks for the fix though !

Cheers.

@pipep The committed fix seems to work for others. Can you please create a new issue for the issue you're seeing?

I already had used the patch mentioned here from when I came across the problem some time ago. Had the problem again today using latest dev release - this time in a new view of custom entities (rather than nodes) and I had to do as #25 - comment out the clear of range. Can't shed any more light, sorry.

Latest dev 2.x has this bug. It didn't become apparent right away though as many things were working fine still with my views elsewhere.

It really messed up my Views Rules. I even tried switching to Views Bulk Operations: Fetch a list of Ids -- as an alternate solution... and the problem still there.

I can confirm this is an issue for the 7.x-2.x-dev - 11/13/15. Was able to fix easily commenting out function views_php_views_post_build (like post #25). Thanks pipep - saved my day!

I also confirm with the latest release the code comment in #25 is still there. Not sure why the code is there to unlock all the limit query done in first place.

However, removing the line code also didn't solved all problem. When using with pager, it didn't come out as Views PHP already override default range(). Currently I remove all PHP field in Views, and convert back using template override.