Hi Uriahs,

Sorry for the waiting time, i did my best to search through all our available working examples with hooks,

and unfortunately, we don't have any example to show you for something similar to this specific use-case.

-

We do not currently have any built-in options to add a Data Validation like that.

If you wish to add a future development suggestion for that, 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.

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

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 the user entered. 

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.

-

At the moment, we only have those error handling messages, which we are working to improve over time to make them as clear as possible, so if a user tries to input text which is too long ( not allowed by the character limit from the SQL Column), our Plugin throws that message.

Thank you for the feedback, we will do our best to make that message clearer in the future/more user friendly.

Hello,

Thank you for adding the suggestion.

I upvoted it and will do my best to affect its priority as much as possible from my end.

Thanks again.