I see there are several notices in the documentation and on the wpDataTables table creation page when using Gravity Forms integration regarding "sorting and searching" may not work as intended", (though nothing about filtering).
I'm attempting to filter some tables - some columns work, some don't, even though they are the same field type, and have the same column settings (that I can see). I have advanced column filters turned on to provide the functionality I require. When I search for a value that is in the affected columns there are no results shown. If I turn server side filtering off, the problem is resolved. I assume this is the issue I'm facing.
The trouble I am about to face is that I have many thousands of entries I'm going to be importing shortly. The page I'm working with has 4 wpDataTables that are hidden, and these are connected to 4 report builder templates that work with the filters. By using URL variables and server side filtering I can control fairly easily what data is delivered to the tables, and thus that which is in the reports.
Unfortunately if I am not able to use server side filtering I'll be delivering those thousands of entries to the client browser every time, for every table.
When can we expect a fix for the issue of wpDataTables server side filtering with Gravity Forms? I'm not convinced that this is a Gravity Forms issue - because I have a number of other plugins that seem to be able to deal with the affected fields just fine.
Somehow we forgot to add filtering to that notice, thanks for pointing that out. It will be added in the next update.
wpDataTables may not work correctly with server-side processing for Gravity Forms based tables and SQL query based tables with JOINs, CONCATs and some other statements. This is probably happening because wpDataTables server has problems with parsing of the query and building new queries dynamically.
For Gravity Forms based tables, the Server-Side processing feature is based on Gravity’s API which we use to fetch the data and create a table from it. Regardless of the complexity of the fields, their type and order - if the API doesn’t return the values correctly, filtering, searching and sorting will not work properly either.
Our developers are well aware of the issue, and currently we're looking at options that Gravity's API has to offer, and trying to figure out if there's something we can do in our code to fix the issue with filters, sorting and search for Gravity Forms based tables with server-side processing.
I see there are several notices in the documentation and on the wpDataTables table creation page when using Gravity Forms integration regarding "sorting and searching" may not work as intended", (though nothing about filtering).
I'm attempting to filter some tables - some columns work, some don't, even though they are the same field type, and have the same column settings (that I can see). I have advanced column filters turned on to provide the functionality I require. When I search for a value that is in the affected columns there are no results shown. If I turn server side filtering off, the problem is resolved. I assume this is the issue I'm facing.
The trouble I am about to face is that I have many thousands of entries I'm going to be importing shortly. The page I'm working with has 4 wpDataTables that are hidden, and these are connected to 4 report builder templates that work with the filters. By using URL variables and server side filtering I can control fairly easily what data is delivered to the tables, and thus that which is in the reports.
Unfortunately if I am not able to use server side filtering I'll be delivering those thousands of entries to the client browser every time, for every table.
When can we expect a fix for the issue of wpDataTables server side filtering with Gravity Forms? I'm not convinced that this is a Gravity Forms issue - because I have a number of other plugins that seem to be able to deal with the affected fields just fine.
Thanks
Hello Simon
Somehow we forgot to add filtering to that notice, thanks for pointing that out. It will be added in the next update.
wpDataTables may not work correctly with server-side processing for Gravity Forms based tables and SQL query based tables with JOINs, CONCATs and some other statements. This is probably happening because wpDataTables server has problems with parsing of the query and building new queries dynamically.
For Gravity Forms based tables, the Server-Side processing feature is based on Gravity’s API which we use to fetch the data and create a table from it. Regardless of the complexity of the fields, their type and order - if the API doesn’t return the values correctly, filtering, searching and sorting will not work properly either.
Our developers are well aware of the issue, and currently we're looking at options that Gravity's API has to offer, and trying to figure out if there's something we can do in our code to fix the issue with filters, sorting and search for Gravity Forms based tables with server-side processing.
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