Hello

"When you use paging and you want to drag a row from one page to another then you need to show some rows of the previous/next page."
Totally right, I didn't think about that...

But since this new fonctionality, rownumbers don't respect pager anymore.

I'm using Views Custom Field module.

You can see my post about Rownumber using pager.

If you could take a look please. Thanks^^

Comments

junro’s picture

junro commented

Link is working here: Rownumber using pager

sevi’s picture

sevi commented

I suppose this is caused by the fact that DraggableViews always sets current_page = 0 but uses offset to skip all nodes until a certain page.
What's exactly the problem at the moment? Which Rownumbers do you see?

greetings,
sevi

junro’s picture

junro commented

How many rows should be displayed of the previous page : 3
How many rows should be displayed of the next page : 3

nodes per page: 100

Page 1:

1
2
3
...
99
100
101
102
103

It's OK.

Page 2: (wrong rows display)

1
2
3
4
5
6
....
99
100
101
102
103
104
105
106

Where 1, 2, 3 are the 3 last nodes of Page 1.
Where 104,105,106 are the 3 first nodes of Page 3.

The good rows display of Page 2 should be:

98
99
100
101
102
103
...
200
201
202
203

Where 98,99,100 should be the 3 last nodes of Page 1.
Where 201,202,203 should be the 3 first nodes of Page 3.

junro’s picture

junro commented

oups I don't know why I put this...

I prefer to put it again here for no mystake.

The good rows display of Page 2 should be:

98
99
100
101
102
103
...
200
201
202
203

Where 98,99,100 should be the 3 last nodes of Page 1.
Where 201,202,203 should be the 3 first nodes of Page 3.

sevi’s picture

sevi commented
Status: Active » Fixed

Well, just what I said.
I created an issue: #419970: Let offset affect row number

Cheers.

junro’s picture

junro commented

Patch works great! Thanks :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.