Search

Is this with Editor? Or filtering? There are a few threads on each, such as here and here, Colin

OMG! I wrote a huge response when I saw the SearchBuilder Extension (Q)! I think this may solve some of the issues I had on many of my pages. I will look into this. Thank you!

See if this thread helps. Kevin

Try the nightly version of FixedColumns which makes this kind of thing much easier. You'll need to use the nightly CSS as well. Allan

The select box appears in header form, between "Show X rows" and "Search" => I didn't find how to do that at all See if this example of adding custom toolbar elements helps. When requesting results to the server, the value always appears in query string => Using a function as ajax.data seems to do the job => That is the way recommended way, see this example. The select box is always having a value, it has a default value and it uses it for the first request Thats up to you, Datatables won't control the custom select input. When selecting another value, the table immediately refresh and show new results => Using ajax.reload() should be ok => That'll work. Another alternative is to use draw() if you are using server side processing (serverSide: true). Kevin

This is great, thank you!

You are going to need to elaborate on your question for me. Are you looking to replicate the code you have there with our Editor PHP libraries, or something else? If you are, then: $editor->where(function ($q) use ($request) { if ($request->first_name) { $q-where('first_name', '%'.$request->first_name.'%', 'LIKE'); } ... }) Would do it. See the documentation here. Allan

Great kthorngren! This is the solution I was looking for Thank you. Thank you also Colin for your answer. I wish you all a good continuation. Riccardo. Do you know how to close this discussion ?

of selected rows after filtering. Kevin

Hi @poeziafree , DD-2030 is simply the internal bug number that we use to track the issue. You don't need to worry about that - it's just so that I can find the original post in the future. The error with SearchBuilder was cause due to the order in which you had your script tags. You can see the order that works by comparing the test cases above. The updated example I provided shows SearchBuilder is working fine, it is the SearchHighlight plugin that is causing the error. You could remove that and it would remove the error. Either way, SearchBuilder will still work. Thanks, Sandy