I am getting the error, "Column 'pos' cannot be null" when I save my tables. I have tried uninstalling wpDataTables and reinstalling, but the error keeps appearing.
Issues like this are usually caused by setting a non-integer, non-auto-increment, non-primary column to be the ID column for editing.
Please provide me a temporary WP-admin login 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 party. You can write credentials here just check Private Reply so nobody can see them except us.
Thank you for your response. Your information provided me with the solution. I was selecting the wrong column as my "key." I have corrected the query and the table now saves properly. Sometimes the issue is hidden by its simplicity!
You aren't able to add any header that includes "<" because of a security measure wpDataTables and WordPress implement. So, the title of the column is the cause of this due to the fact that "<" is an opening HTML script tag, and it's automatically being flagged as a potential SQL injection threat, so it's causing the issue.
Adding superscript to the column header is something that you'd need to do with custom HTML. This is not something we've done in the past, so we can't share any advice with you.
I am getting the error, "Column 'pos' cannot be null" when I save my tables. I have tried uninstalling wpDataTables and reinstalling, but the error keeps appearing.
Hello Ronny
Issues like this are usually caused by setting a non-integer, non-auto-increment, non-primary column to be the ID column for editing.
Please provide me a temporary WP-admin login 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 party. You can write credentials here just check Private Reply so nobody can see them except us.
Kind Regards,
Aleksandar Vuković
aleksandar.vukovic@tmsproducts.io
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Aleksandar,
Thank you for your response. Your information provided me with the solution. I was selecting the wrong column as my "key." I have corrected the query and the table now saves properly. Sometimes the issue is hidden by its simplicity!
Thank you.
Ronny
You're welcome Ronny
Glad I could help.
If you have any further questions or issues, please feel free to open a new ticket, and we'll gladly help.
Best regards.
Kind Regards,
Aleksandar Vuković
aleksandar.vukovic@tmsproducts.io
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Aleksandar,
I am also getting this error because I use a <sup> tag in the column heading(import via CSV format)
Is it possible to add a superscript in the column heading?
Hello Nikhil
You aren't able to add any header that includes "<" because of a security measure wpDataTables and WordPress implement. So, the title of the column is the cause of this due to the fact that "<" is an opening HTML script tag, and it's automatically being flagged as a potential SQL injection threat, so it's causing the issue.
Adding superscript to the column header is something that you'd need to do with custom HTML. This is not something we've done in the past, so we can't share any advice with you.
Kind Regards,
Aleksandar Vuković
aleksandar.vukovic@tmsproducts.io
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables