If you want to display data from Gravity Forms and use the entry ID without changing the position in the table, this works without any problems. The content can be sorted and searched.
However, if the entry ID is moved to the first column, for example, it is neither searchable nor sortable.
Furthermore, I cannot search for the complete entry ID ... existing entry IDs are not found if the number is specified in full in the search (both in the global search for the entire table and in the relevant column). Why? Is that a bug?
I've just tested this on our sandbox site, and I can confirm what you're saying regarding the behavior when server-side processing is enabled in the "Data Source" tab. It seems to work fine when disabled.
Unfortunately, it's a known issue with server-side tables generated from Gravity Forms. As you may have noticed from the yellow notice above the tables, sorting and searching may not behave as expected when server-side processing is turned on.
This issue originates from Gravity Forms, and we've been trying to get their help to resolve it. However, despite our best efforts, we haven't heard back from them yet. Until they address it from their end, I'm afraid we won't be able to bypass it.
If you want to display data from Gravity Forms and use the entry ID without changing the position in the table, this works without any problems. The content can be sorted and searched.
However, if the entry ID is moved to the first column, for example, it is neither searchable nor sortable.
Furthermore, I cannot search for the complete entry ID ... existing entry IDs are not found if the number is specified in full in the search (both in the global search for the entire table and in the relevant column).
Why? Is that a bug?
Hi Andreas,
Thanks for reaching out.
I've just tested this on our sandbox site, and I can confirm what you're saying regarding the behavior when server-side processing is enabled in the "Data Source" tab. It seems to work fine when disabled.
Unfortunately, it's a known issue with server-side tables generated from Gravity Forms. As you may have noticed from the yellow notice above the tables, sorting and searching may not behave as expected when server-side processing is turned on.
This issue originates from Gravity Forms, and we've been trying to get their help to resolve it. However, despite our best efforts, we haven't heard back from them yet. Until they address it from their end, I'm afraid we won't be able to bypass it.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables