phpMyAdmin configuration storage errors and the missing database tables
When you load phpMyAdmin and see a warning that the configuration storage is incomplete, it usually means the application cannot find the specific tables required to persist user preferences, bookmarks, or history. The error output you provided confirms this: features like relation, table_info, bookmarktable, and history are all marked as "not OK."
This state occurs because phpMyAdmin relies on a separate MySQL/MariaDB database to store its own metadata. By default, this is the phpmyadmin database. Your configuration file (config.inc.php) defines the names of these tables in variables like $cfg['Servers'][$i]['bookmarktable'], but the actual SQL tables do not exist yet. Consequently, phpMyAdmin disables these features to prevent errors when trying to insert or retrieve data from non-existent resources.
The root cause is a mismatch between your configuration definitions and the physical database schema. You have correctly set $cfg['Servers'][$i]['pmadb'] to wordpress_db, but you likely haven't created the necessary tables within that database yet. When you define $cfg['Servers'][$i]['bookmarktable'] = 'pma_bookmark', phpMyAdmin expects a table named pma_bookmark inside the wordpress_db database. If this table is missing, the feature is disabled.
To resolve this without manually creating tables via SQL commands or phpMyAdmin's setup wizard (which often fails if the configuration storage itself is broken), you can execute a script to generate the required schema. Create a file named create_tables.sql and populate it with the standard definitions for all the disabled features:
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_bookmark` (
`db_name` varchar(64) NOT NULL default '',
`user` varchar(32) NOT NULL default '',
`username` varchar(64) NOT NULL default '',
`label` varchar(64) character set utf8 COLLATE utf8_bin default NULL,
`query` text NOT NULL,
`format` tinyint(2) unsigned NOT NULL default '1',
PRIMARY KEY (`db_name`,`user`,`username`,`label`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_relation` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`column_name` varchar(64) NOT NULL default '',
`db_username` varchar(64) character set utf8 COLLATE utf8_bin default NULL,
`db_password` varchar(64) character set utf8 COLLATE utf8_bin default NULL,
PRIMARY KEY (`db_name`,`table_name`,`column_name`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_table_info` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`data` text character set utf8 COLLATE utf8_bin,
PRIMARY KEY (`db_name`,`table_name`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_table_coords` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`pdfpage` varchar(32) character set utf8 COLLATE utf8_bin default NULL,
PRIMARY KEY (`db_name`,`table_name`,`pdfpage`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_pdf_pages` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`pdfpage` varchar(32) character set utf8 COLLATE utf8_bin default NULL,
PRIMARY KEY (`db_name`,`table_name`,`pdfpage`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_column_info` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`column_name` varchar(64) character set utf8 COLLATE utf8_bin default NULL,
`comment` varchar(1000) CHARACTER SET utf8 COLLATE utf8_bin default NULL,
PRIMARY KEY (`db_name`,`table_name`,`column_name`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_history` (
`timevalue` bigint(21) UNSIGNED NOT NULL default '0',
`username` varchar(64) NOT NULL default '',
`db_select` varchar(64) character set utf8 COLLATE utf8_bin default NULL,
`query` text NOT NULL,
PRIMARY KEY (`timevalue`,`username`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_tracking` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`version` varchar(32) character set utf8 COLLATE utf8_bin default NULL,
`username` varchar(64) NOT NULL default '',
PRIMARY KEY (`db_name`,`table_name`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_tracking_versions` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`version` varchar(32) character set utf8 COLLATE utf8_bin default NULL,
PRIMARY KEY (`db_name`,`table_name`,`version`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_tracking_columns` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`column_name` varchar(64) character set utf8 COLLATE utf8_bin default NULL,
PRIMARY KEY (`db_name`,`table_name`,`column_name`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_tracking_options` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`username` varchar(64) NOT NULL default '',
PRIMARY KEY (`db_name`,`table_name`,`username`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_designer_coords` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`x` smallint(5) UNSIGNED NOT NULL default '0',
`y` smallint(5) UNSIGNED NOT NULL default '0',
PRIMARY KEY (`db_name`,`table_name`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_userconfig` (
`username` varchar(64) NOT NULL default '',
`timevalue` bigint(21) UNSIGNED NOT NULL default '0',
`data` text NOT NULL,
PRIMARY KEY (`timevalue`,`username`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_table_uiprefs` (
`db_name` varchar(64) NOT NULL default '',
`table_name` varchar(64) NOT NULL default '',
`username` varchar(64) NOT NULL default '',
`prefs` text,
PRIMARY KEY (`db_name`,`table_name`,`username`)
);
CREATE TABLE IF NOT EXISTS `wordpress_db`.`pma_recent` (
`username` varchar(64) NOT NULL default '',
`timevalue` bigint(21) UNSIGNED NOT NULL default '0',
`data` text,
PRIMARY KEY (`timevalue`,`username`)
);
Execute this SQL against your wordpress_db database. This will create the missing tables and restore full functionality to features like the relation viewer, PDF export, and history tracking.
One critical detail in your current configuration is the $cfg['Servers'][$i]['controluser'] setting set to 'dave1'. phpMyAdmin uses this user to connect to the configuration storage database directly via a socket connection to manage permissions securely. The corresponding password is stored in $cfg['Servers'][$i]['controlpass']. Ensure that the MySQL user dave1 exists and has privileges on the wordpress_db database, specifically CREATE, INSERT, UPDATE, DELETE, DROP, INDEX, ALTER, TRIGGER, REFERENCES, and `