changed behaviour of fnFilter / search from 1.9 to 1.10

changed behaviour of fnFilter / search from 1.9 to 1.10

XyphusXyphus Posts: 1Questions: 0Answers: 0

Hi,

I noticed than fnFilter worked to search in a specific column in 1.9 even if the column is not searchable.
The same code in 1.10 does not work (either using the legacy fnFilter or column().search().draw()), unless the column is made searchable.
It's a bit annoying when you need a search input in addition to the generic one to search a column that needs a specific type of search. That column should not be searched via the generic input.
I don't know if this can be considered as a bug or not. I'd personally find the 1.9 behaviour more logical.

Replies

  • allanallan Posts: 61,805Questions: 1Answers: 10,119 Site admin

    That is a bug in 1.9. If a column is marked as not searchable, it should be ... not searchable :-).

    I think there does need to be a way to remove a column for the global search without disabling its column searchability. I'm planning on doing a major update to the search for 1.11 and I will look at how this could be implemented for that release.

    Allan

This discussion has been closed.