Issue with Views pagination

It works here. So it could be something particular to your installation, or maybe something special in this view that brakes the joins that this module builds.

Try debugging the queries executed (using the devel module) and see how the SQL statement from the main query of this view changes from one page to another.

You can first see how the query looks in the Views UI, and that should give you the pattern to look into the list of queries provided by devel module.

I had this as well, and figured it out, in my case, i was using the backreference to heavily, and when the "count" query was run by views to get the number of rows returned, it adds "distinct" and since all the rows were for one node (with multiple backreferences), it only returned 1. This was the query:

SELECT COUNT( *  )
  FROM (
    SELECT DISTINCT node.nid AS nid
    FROM node node
    LEFT JOIN (
      content_field_group_ref node_data_field_group_ref
      INNER JOIN node node_node_data_field_group_ref ON node_data_field_group_ref.vid = node_node_data_field_group_ref.vid
    ) ON node.nid = node_data_field_group_ref.field_group_ref_nid
    WHERE (
      node_node_data_field_group_ref.type
      IN (
        'contact'
      )
    )
    AND (
      node.nid =1489
    )
  ) count_alias

So, I had to re-think the view, sort of reverse the relationship/criteria, and the query now looks like:

SELECT COUNT( *  )
  FROM (
    SELECT DISTINCT node.nid AS nid
    FROM node node
    LEFT JOIN content_field_group_ref node_data_field_group_ref ON node.vid = node_data_field_group_ref.vid
    LEFT JOIN node node_node_data_field_group_ref ON node_data_field_group_ref.field_group_ref_nid = node_node_data_field_group_ref.nid
    WHERE (
      node.type
      IN (
        'contact'
      )
    )
    AND (
      node_node_data_field_group_ref.nid =1489
    )
  ) count_alias

And correctly gives the right number of rows - 22

Now there is in fact no backreference usage at all, just using the "group" relationship (which i was backreferencing before) in the argument. This is probably much more efficient as well ;-)

HTH

It looks like this is fixed.

I don't believe the solution offered is a fix.

If you use a reverse node reference to display nodes referring to a given node, then you must use the relationship field on the row style configuration to return the referencing nodes. If not, you just end up with multiple copies of the referenced node. The pager count SQL is not taking in to account this relationship and the DISTINCT is always returning 1 - the node referenced, rather than the number of referencing nodes.