Skip to content
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

global ordering:false not working why? #107

Closed
saahmadi opened this issue Sep 14, 2019 · 2 comments
Closed

global ordering:false not working why? #107

saahmadi opened this issue Sep 14, 2019 · 2 comments
Labels
Milestone

Comments

@saahmadi
Copy link

global ordering:false not working why?

@smsotirov
Copy link

I have the same issue. basically, whet this is set, the request does nto contains any rder. So there is not order[0].column... and order[0].dir and order[0].name params in the request. While the validation in DataTablesInput is @notempty for the field "order". I don't have a fix to this issue. I'm thinking to create my implemetation of the whole project because of this issue.

darrachequesne added a commit that referenced this issue Mar 3, 2024
The "order" attribute can be empty in two cases:

- when setting "ordering: false"

Reference: https://datatables.net/reference/option/ordering
Related: #107

- with DataTabbles 2.0

> Columns can now have three ordering states - asc, desc or data index order (specified by an empty string). The columns.orderSequence option has been updated to make use of this, so the third ordering on a column will now take it back to the index order, rather than returning to the first direction.

Reference: https://cdn.datatables.net/2.0.0/
Related: #156
@darrachequesne
Copy link
Owner

This should be fixed by a214d5b, included in version 6.0.2.

@darrachequesne darrachequesne added this to the 6.0.2 milestone Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants