Displaying duplicate rows when we are in last page and change rows per page value
Displaying duplicate rows when we are in last page and change rows per page value
perceptive_dev
Posts: 1Questions: 0Answers: 0
Hi,
We are using data tables plugin 1.9.3. We have found an issue is,
1) When we are in last page and change current rows per page, the plugin is displaying the rows exists in last but one page and highlighting last but one page number and still has last page. For example if we have 138 rows and rows per page value is 10 then plugin is displaying the rows 128-138 in last but one page and still we have last page upon changing rows per page value.And then if we click on last or next page it is displaying rows from 130 to 138, the remaining rows.Actually it should display rows from 121-130 in last but one page or 131-138 in last page.
2) And when we do second click on last but one page the rows are displaying correctly (121-130) and even second click on last page.
Is this known issue? actually I have updated the code locally to calculate "iDisplayStart" value in _fnFeatureHtmlLength ( oSettings ) function to fix the issue.
Madhu.
We are using data tables plugin 1.9.3. We have found an issue is,
1) When we are in last page and change current rows per page, the plugin is displaying the rows exists in last but one page and highlighting last but one page number and still has last page. For example if we have 138 rows and rows per page value is 10 then plugin is displaying the rows 128-138 in last but one page and still we have last page upon changing rows per page value.And then if we click on last or next page it is displaying rows from 130 to 138, the remaining rows.Actually it should display rows from 121-130 in last but one page or 131-138 in last page.
2) And when we do second click on last but one page the rows are displaying correctly (121-130) and even second click on last page.
Is this known issue? actually I have updated the code locally to calculate "iDisplayStart" value in _fnFeatureHtmlLength ( oSettings ) function to fix the issue.
Madhu.
This discussion has been closed.