Hi, Mark.

That seems strange.  If you have set up the userid column correctly, then all the new rows the currently logged user has,  should auto-populate their user ID, which should then allow them to edit those rows.

Can we take a look at the setup, then we can do some troubleshooting?

If you could send me the URL of that private page,

and Administrator access to the back-end.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

And point me to both table ID's,    the initial table for Admins/Editors,

and the second table.

If the private page needs a password, please share that as well.

Thank you.

Hi, Mark.

Our developers have advised us.

We have discovered a bug for this behaviour.

The issue here is that you have named your "user ID" column 'WP-ID', which makes a problem with our current plugin's configuration.

The solution will be to go in your database and change the WP-ID and save the tables again in order to change the settings.

Or you can change this piece of code in our plugin's PHP file , in this path :

../wp-content/plugins/wpdatatables/source/class.wdttools.php

around line 2033 find this :

$res = $wpdb->query($wpdb->prepare( "SELECT {$idColumnName} FROM {$mySqlTableName} WHERE {$idColumnName} = %d AND {$userIDColumnName} = %s", $idValCheck, get_current_user_id() ));

replace it with :

$res = $wpdb->query($wpdb->prepare( "SELECT `{$idColumnName}` FROM {$mySqlTableName} WHERE `{$idColumnName}` = %d AND `{$userIDColumnName}` = %d", $idValCheck, get_current_user_id() ));

this will still be tested by our QA Team, before our developers implement a fix in the plugin,

but you can try and let us know if that works on your site.

Thank you.

Hi, Mark.

We got advised by the devs , as mentioned, they will work to add this fix in one of the future updates.

In regards to naming conventions for Columns and tables in MySQL, please check this Guide :https://medium.com/@centizennationwide/mysql-naming-conventions-e3a6f6219efe.

I hope that helps.

Hi, Mark.

Just an additional advise, in regards to setting up the "user_id" column with our Plugin for the "users can see and edit only their own data" feature,

please check the example on our Documentation Page.

For the time being, it is best to do it like that, but when our devs implement this fix, then users will be able to name the user ID column anything they need.

We can't say exactly when it will be added, but

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.

I hope that helps.

Thank you.