I have a table that is configured to be editable from the front-end. It used to be set up to only allow users to edit their own data and to use advanced filters, although I have since disabled both settings as a troubleshooting measure.

Currently, both before and after disabling the aforementioned settings, the table only shows about five rows of data on initial load. If I configure on the admin page to automatically refresh every few seconds, it will correctly display all the rows; otherwise, I have to enable advanced filtering and clear the filters in order to get all the rows to display. It seems to be behaving as if it's being pre-filtered - even from the admin page - but I can't find any other setting that might be interfering with this.

The other big issue is that the 'code' field is configured as the id/primary key (and formerly was the primary key in the database until I changed it trying to troubleshoot the table issues) and only rows with a numeric code (e.g., '10', '200', etc.) are editing/updating correctly. Non-numeric coded rows (e.g., 'B', 'H', 'BMH', etc.) are creating a new row instead of simply updating the selected field. I can select the value, I can type the new value in, but then it takes that value and creates a new row instead. Previously, since the Code field was the primary key, I assumed that was what was causing the "error creating new rows" message. However, I still seem to be getting that even though I have now removed primary keys from that table in my database. So after the error is generated on creating a new row, I can no longer edit any additional rows since the database now has a row with three null fields that are not supposed to be null which is generating errors on attempting to write any further data to the database.

I just don't know what is causing WPDataTables to create a new row instead of correctly editing the field or simply generating an error and not writing to the database at all if there is another problem. I'm still getting the error even though I no longer have a primary key, presumably because it's still generating a row with invalid null fields. It's a pain having to delete that row manually in SQL through PHPMyAdmin every single time and pretty much not having the option to edit those rows at all.

I am not seeing anything in the Firefox Developer Tools that indicates what is causing that new row to be created or what the error actually is, and I can't think of anything else to try to troubleshoot. I need help please. I really need my users to be able to edit this particular table.

 ,