After latest Updates SearchPanes show "No SearchPanes" hint although they are filled

fwtag

Hi there,

after the latest updates to the current versions of DataTables (2.3.2) and SearchPanes (2.3.3), I struggled a bit with the configuration. But I think I can work it out.

However, one strange behaviour still persists: Each SearchPanes filter shows "No SearchPanes" although there are a lot of data. Ref to the image attached.

The config is quite simple (since I still need to do a lot of config adjustments):

...
import 'datatables.net-dt'
import 'datatables.net-select-dt'
import 'datatables.net-searchpanes-dt'
...
$(function () {
   ...
   let table = $('#orders-datatable').DataTable({
      ...
        layout: {
            topStart: 'searchPanes'
        },
   }
}

allan

Can you give me a link to a page showing the issue so I can attempt to debug it please? It isn't happening in this example so I'm not certain what would cause it.

Allan

fwtag

@allan Sorry, this page is not public available, since it is refactored locally at the moment.
OK, so I need to do some debugging by myself.

allan

There is something nagging at me that I've seen this before, but I can't put my finger on it! I've just had a look at the commit messages for SearchPanes since the last release, and I don't think there is anything there that would impact this, but it might be worth trying the nightly build.

Allan

fwtag

@allan Great that you took care onto this issue again. I shall give it a try but currently, another odd issue with sererside skripting and SearchPanes "pains" me ... I shall open another topic on this. Frank

fwtag

See here: http://datatables.net/forums/discussion/81138/searchpanes-stya-empty-with-serverside-skripting/p1?new=1

kthorngren

I wonder if this is the same issue as noted in your other thread. Do you have columns.searchable set to false for these columns?

Kevin

fwtag

@allan No changes with the nightly build.

But however, maybe I am wrong regarding my statement that it started with the last build. This issue might be there for longer than one release step and I just did not see it.

But however, since there is a "speaking" error message, this might be the point to start from.

This message seems to be the default value for emptyPanes:

      emptyPanes: "No SearchPanes",

But if you take a look to this screenshot you see that the non-default message (in german language) is not shown at all (only the "emptyTable" or "infoEmpty" message is shown ADDITIONALLY, don't know which one, both have the same value):

This message is set here:

         searchPanes: {
            i18n: {
                clearMessage: 'Alle Filter löschen',
                collapse: {
                    0: 'Filter',
                    1: 'Filter (1 ausgewählt)',
                    _: 'Filter (%d)'
                },
                collapseMessage: 'Filter ausblenden',
                emptyPanes: 'Keine Filter verfügbar',
                loadMessage: '<span class="spinner-border spinner-border-sm text-secondary me-2" role="status"></span>Filtere Daten ...',
                showMessage: 'Filter einblenden',

                title: {
                    _: '%d Filter angewendet',
                    0: 'Keine Filter angewendet',
                    1: 'Ein Filter angewendet'

                }
            }
        },

The other localized values are set as expected. Only this one misses and is shown even if there are Data.

Maybe that helps?

kthorngren

Are you loading a language file that contains a searchPanes section?

Possibly language.searchPanes.emptyPanes (from the file) and searchPanes.i18n.emptyPanes are conflicting.

Also you may have missed my previous comment as it looks like we cross posted.

Kevin

fwtag

@kthorngren Thanks for your advise. After switching from searchPanse.i18n to language.searchPanes at least the message is shwon in the right language:

But however, the issue still persists.

kthorngren

I might be wrong but it seems like we have two threads discussing the same issue. See my answer in your other thread.

If that doesn't help then we will need to see a test case replicating the issue so we can help debug. If you can't post a link then maybe you can update this test case I started for you:
http://live.datatables.net/geseteyu/1/edit

It uses the xhr event to simulate adding the searchPanes property to the JSON response. I pasted what you posted in the other thread into the test case and it is working. The search doesn't work but the pane is populated.

Kevin