Please note after much experimentation when using a VBO 'Modify Entity Values' with 'Select all items on all pages' checked (and using a pager) it will only actually modify the current page's entities even though you have 'select all items on all pages' checked. It will not change the entities on any of the other pages.
Just so you know if you have 'display all items' and hence do not have a pager the 'Select all items on all pages' selects all the items on that page and will modify the entities without issue, so it's definitely a pager problem.
At the moment I have over 9000 rows in a view so I really need this to work to make entity changes across all the rows with a pager. As you can imagine the greater the view grows the worse the performance if I have to display all (as opposed to page).
Comments
Comment #1
MaxMendez CreditAttribution: MaxMendez commentedI have same problem
Comment #2
spessex CreditAttribution: spessex commentedHas anyone noticed this post yet? Is there a patch available only it appears to be a major bug?
Comment #3
bojanz CreditAttribution: bojanz commentedProblem is, I can't reproduce what you're describing.
Looks like a corner case, judging by the lack of comments in this issue.
Is it always limited to page 1? What happens if you try another view on the same entity type? What if you try a different entity type (users instead of nodes, etc).
Can you attach a view export?
Comment #4
bojanz CreditAttribution: bojanz commentedComment #5
bojanz CreditAttribution: bojanz commentedNo further information provided.
Comment #6
veronicaSeveryn CreditAttribution: veronicaSeveryn commentedI think I know how to reproduce it. At least I have encountered this issue while using Views LitePager module.
When the pager is set to use LitePager and a bulk operation is performed on ALL the rows (when the limit per page is set to, let's say, 20), the action will be performed on only currently visible rows, which is 20 count. Others will remain untouched.
Is there a way to make Bulk Operations works with Views LitaPager module (since LitePager is not using COUNT queries, not sure if that's the reason of the bug).
Comment #7
bojanz CreditAttribution: bojanz commentedA few months ago we fixed one of these bugs with:
http://cgit.drupalcode.org/views_bulk_operations/commit/?id=a7db93c
I'm not familiar with LitaPager so I don't know if additional changes are needed. If yes, please open a new issue (with a patch, if possible).
Comment #8
icecreammocca CreditAttribution: icecreammocca commentedin new versions code has change
but problem not solved for me, can help me? anybody?