-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bootstrap-Table column reorder mismatch when paging #79
Comments
it seems this project is abandoned. nobody answering for years. :/ |
Hello Team, any update or any solution for this issue ?? please let us know if you have any solutions @andre-mr @carolinatree |
i didn't have this exact issue, i was commenting because of another related one and noticed the lack of support from developers here. but for many issues i faced using this library, i ended managing tricks to deal with them, like extra js/jquery code, external buttons, functions fired just to fix layout issues, direct access to table elements, etc. |
I could not find a solution because of time constraints so I went with another library. |
@carolinatree thanks for a time can you let us know which library are you using for this issue ? |
@AlpeshKatariya we went with DataTables DataTables-1.11.4. |
https://live.bootstrap-table.com/code/carolinatree/10576
I'm developing a dashboard list that uses this bootstrap table with the reorder columns extension coupled with dragtable.js.
The table is successfully loaded with the requested column order which is personalized per person. All the paging works and it looks good. But when I use my filter to let them choose to move columns or hide/show them, when moving to the next page, the column order is different than the header columns which moved successfully when they were filtered.
Dashboard loads correct order of columns using object list from the db. User clicks filter and moves a column. The page they are on appears correct. User clicks to the next page or show all rows and the data rows (not the header) revert back to the original order.
The header and data are mismatched.
The text was updated successfully, but these errors were encountered: