Hi Karl,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

If i understood, you would need something like a 'data validation' of an edited entry before it gets saved/stored in the table?

This is not possible with our current built-in features,

if you wish to see a built-in solution in the future,

Please feel free to search on our suggestions page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there,  and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

-

When it comes to a custom workaround, we don't have any example to show you for something similar to this specific use-case.

We can only provide at least some advice that our developers sent us, and we hope this might help get  you started:

In this file of our plugin:

wp-content/plugins/wpdatatables/controllers/wdt_ajax_actions.php 

around line 252, where the method for saving wdtSaveTableFrontend is, you can find these hooks:

Actions:

wpdatatables_before_frontend_edit_row

wpdatatables_after_frontent_edit_row

Filters:

wpdatatables_filter_frontend_formdata

wpdatatables_filter_formdata_before_save

wpdatatables_query_before_save_frontend

With those, a developer can manipulate the data which a user entered in the table. 

This is as much as our developers can advise since using combinations and solutions which are not included in the built-in functions of the plugin require additional engagement, 

and are not included in the provided support.

I hope that helps.

It probably can be done with some custom work, but our developers are very busy at the moment, working on some priority tasks and fixing bugs and issues with our plugins, so they won't be having the time for custom work in the near future.