wp_wpdatatables’ doesn’t exist

Hi rippledj,

Sorry for inconvenience,

That is very strange. Can you try to deactivate/activate plugin again , then check again is it created in database. If not, please check server log is there some errors.

If there is no errors and this table is not created in database after activating the plugin, then please contact us over our support platform where you will open new Private Pre-purchase ticket for wpDataTables where you will provide us temporary wp-login credentials 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.

Thank you for understanding.

Best regards.

Getting the same issue on install
Table ‘db.wp_wpdatatables’ doesn’t exist

PHP 7.4
Mysql8 – Managed database on digitalocean
WP 5.8.1

System Error below, I suspect it is related to this issue
https://stackoverflow.com/questions/62418099/unable-to-create-or-change-a-table-without-a-primary-key-laravel-digitalocean

WordPress database error Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting. for query CREATE TABLE wp_wpdatatables (
						id INT( 11 ) NOT NULL AUTO_INCREMENT,
						title varchar(255) NOT NULL,
                        show_title tinyint(1) NOT NULL default '1',
						table_type varchar(55) NOT NULL,
						content text NOT NULL,
						filtering tinyint(1) NOT NULL default '1',
						filtering_form tinyint(1) NOT NULL default '0',
						sorting tinyint(1) NOT NULL default '1',
						tools tinyint(1) NOT NULL default '1',
						server_side tinyint(1) NOT NULL default '0',
						editable tinyint(1) NOT NULL default '0',
						inline_editing tinyint(1) NOT NULL default '0',
						popover_tools tinyint(1) NOT NULL default '0',
						editor_roles varchar(255) NOT NULL default '',
						mysql_table_name varchar(255) NOT NULL default '',
                        edit_only_own_rows tinyint(1) NOT NULL default 0,
                        userid_column_id int( 11 ) NOT NULL default 0,
						display_length int(3) NOT NULL default '10',
                        auto_refresh int(3) NOT NULL default 0,
						fixed_columns tinyint(1) NOT NULL default '-1',
						fixed_layout tinyint(1) NOT NULL default '0',
						responsive tinyint(1) NOT NULL default '0',
						scrollable tinyint(1) NOT NULL default '0',
						word_wrap tinyint(1) NOT NULL default '0',
						hide_before_load tinyint(1) NOT NULL default '0',
                        var1 VARCHAR( 255 ) NOT NULL default '',
                        var2 VARCHAR( 255 ) NOT NULL default '',
                        var3 VARCHAR( 255 ) NOT NULL default '',
                        tabletools_config VARCHAR( 255 ) NOT NULL default '',
						advanced_settings TEXT NOT NULL default '',
						UNIQUE KE

Exact same issue here, exact same environment (managed DigitalOcean database).

Hello!

Can you guys please reach out to DigitalOcean, and ask them to turn off sql_require_primary_key?

DigitalOcean recently enforced primary keys on all newly created tables in their managed databases, and since we’re using UNIQUE, this option needs to be disabled in order to work.

Our developers will surely take a look at this, and find a solid fix for future updates. Also, if DigitalOcean doesn’t want to disable this, please feel free to open a ticket on our official support platform, and our support managers will gladly help.

Kind regards!