I have a two content types A and B. A has a multivalue node reference "field_related" defined field to B.
I created a block view that takes the node ID as an argument ( from the URL validating to be of type A) and selected "field_related" as my field unchecking the group multiple values check box. I set my items per page limit to 4 and turned on the pager.
If i have more than 4 values for field_related on a given node of type A all i ever see is the first 4 values that returns from the view. If i up my limit items per page limit to 5 then it shows 5 but never does it show a pager.
From what i can tell i think that since im passing a node argument in the result set from the query is really only 1 and it doesnt think that there are more values to page over.... seems like the paging implementation for views excludes taking into account multi value fields...
Is this as designed? Is there a work around or patch to get this to work? I have more complex examples as well...
thoughts?
Comments
Comment #1
gpk commentedThis could be a duplicate of #375298: Pager misses records when multiple value fields are displayed with other fields, in which case it would be nothing to do with the argument..
Also #553766: Pager doesn't work with multi-field CCK items?, #552804: Records are missing when using pager and items per page.
Comment #2
esmerel commentedNo response to suggested other issues.
Comment #3
gpk commentedLet's at least mark this as a dupe of #375298: Pager misses records when multiple value fields are displayed with other fields.