-
Notifications
You must be signed in to change notification settings - Fork 284
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
Date range filter with ColReorder populates wrong column for AJAX searches #429
Labels
Comments
As an aside, after doing the date selection in the 1st column, you'll notice that the 3rd column's filter field has the focus, not the 1st column like you might expect. I assume these are related behavior/bugs. |
vedmack
added a commit
that referenced
this issue
Jan 9, 2018
vedmack
added a commit
to vedmack/yadcf-showcase
that referenced
this issue
Jan 9, 2018
vedmack
added a commit
to vedmack/yadcf-showcase
that referenced
this issue
Jan 9, 2018
fixed, look at the the updated showcase page (see new js code) and if you want you can see the new server side java code in the showcase source code https://github.com/vedmack/yadcf-showcase |
SebastianRoland
added a commit
to SebastianRoland/yadcf
that referenced
this issue
Feb 14, 2018
* commit 'c549c9295d508af5d4b7eb398796f6f9a0a645a2': Fix a markdown link in readme ✌️ Added support for col reorder in range filters - vedmack#429 bug fix: vedmack#426 bug fix: vedmack#425 enhancement for parsing multiple html elements in cell 0.9.3 beta has began... yadcf 0.9.2 goes final fixed filter_type: 'text' with FixedHeader Add CSS class on DateRange fields # Conflicts: # src/jquery.dataTables.yadcf.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using ColReorder and an AJAX endpoint, the date range filter pushes the search term into the wrong field. I've put together a simple example: http://23.239.11.111/yadcf_test/index.html that is about as stripped as I could get it. The server component does not return "right" data, it's just there to mirror the "draw" field so it doesn't fail.
What's happening: in the AJAX call, the columns[n][search][value] entry is right for the text field searches. But for the date range search, it goes in it's "natural" spot, not in its reordered spot.
You can see from the attached image that even though the date field is "platform2", the date search went into the "engine" search field.
For reference, I've also attached the data.php in case you want to recreate the example locally.
data.php.txt
Note: This appears to be a very similar issue to #267 , but I'm providing an example and the fix listed there doesn't work for me.
The text was updated successfully, but these errors were encountered: