On line 1607 in wpdatatables/source/class.wpdatatable.php you are passing an array to a 3rd party library. The array's internal pointer however is not guaranteed to be at the first element which the library expects. An example in our case is when $parsedSearch has a value. This causes an exception in PHPSQLCreator since WHERE or anything but the 1st key is not a valid SQL query type. The fix is to add reset($parsedQuery) before $creator->create($parsedQuery);
Thanks and hope to see this in a bug fix release soon.
On line 1607 in wpdatatables/source/class.wpdatatable.php you are passing an array to a 3rd party library. The array's internal pointer however is not guaranteed to be at the first element which the library expects. An example in our case is when $parsedSearch has a value. This causes an exception in PHPSQLCreator since WHERE or anything but the 1st key is not a valid SQL query type. The fix is to add reset($parsedQuery) before $creator->create($parsedQuery);
Thanks and hope to see this in a bug fix release soon.
Hi jacobgalanty,
Thank you for your purchase.
I will forward this to my team to fix that in next update. Thank you very mach for reporting this. We appreciate that.
Kind Regards,
Isidora Markovic
wpDataTables: FAQ | Facebook | Twitter | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Amelia demo sites | Docs
You can try our wpDataTables add-ons before purchase on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables