Hi guys,

My sincerest apology, there was an error on this ticket from my end - I wrote a reply, but it somehow did not get sent properly.

This will not happen again, thank you very much for your patience and understanding.

Our developers isolated this bug with our WP Post builder integration and we have the first version of the fix available. 

This fix works on our test websites, so it should work for you as well. 

Here are the steps to apply the fix. 

Extract the JS file from the zipped folder we send here as an attachment and use FTP or your WP Hosting server's File Manager to overwrite the file of our Plugin in this path :

..\wp-content\plugins\wpdatatablesintegrations/pro/query-builder/assets/wp_posts_table_config.js 

 We recommend purging the Site's cache at the end, then refresh the page and check, the issue should be fixed.

 Let us know if you are still encountering the issue after applying this JS fix. 

2. Or if you wish to directly edit the code of our JS file (instead of overwriting it via FTP), find this piece of code in the same file, around line 262 :​

cf_column_counter = Object.keys(wpdatatable_config.queryParameters.customFieldColumns).length;

Replace it with this :

cf_column_counter = Object.keys(wpdatatable_config.queryParameters.customFieldColumns ?? {}).length;​

Our developers should add this fix in our next update, but the QA Team is still conducting tests to make sure there are no negative effects before it gets added to the Plugin's core, so please keep a lookout on our wpDataTables changeLog.

It will be stated there during updates which bug fixes have been implemented at each update. 

Thank you for all your patience and understanding once again.