WP-DBManager 4.0.0

WP-DBManager 4.0.0 is a total rewrite of the plugin with Claude Code to make it more modern and testable. There will be breaking changes. Please do test it https://github.com/lesterchan/wp-dbmanager/archive/refs/heads/master.zip

WP-DBManager 4.0.0 requires WordPress 6.8 and PHP 8.2. A site on an older stack is simply not offered the update, so if WP-DBManager has stopped appearing in your updates list, that is why.

Written against 3.0.0, the version currently on WordPress.org. It is 4.0.0 rather than 3.0.1 because 3.0.0 had already shipped; nothing was skipped.

Settings migrate on the first load after updating. dbmanager_options becomes wp_dbmanager_options, and a second row, wp_dbmanager_version, records which version last ran. The old row is deleted once copied. Point any code calling get_option( ‘dbmanager_options’ ) at the new name.

All thirteen classes are renamed from DBManager_* to WP_DBManager_*.

The three scheduled jobs have new hook names. dbmanager_cron_backup, dbmanager_cron_optimize and dbmanager_cron_repair are now wp_dbmanager_cron_backup, wp_dbmanager_cron_optimize and wp_dbmanager_cron_repair; the recurrences behind them — dbmanager_backup, dbmanager_optimize, dbmanager_repair — are now wp_dbmanager_backup, wp_dbmanager_optimize and wp_dbmanager_repair. The plugin clears the old events and rebuilds the schedule from your Settings settings on first load; check the three “Next … date” lines afterwards. Point any wp_schedule_event() call or WP-CLI cron entry of your own at the new names.

wp_dbmanager_before_escapeshellcmd is unchanged.

New wp_dbmanager_capability filter. The screens still require install_plugins, as they have since 2.80.7 — they restore, empty and drop tables, so the gate is deliberately as high as installing code. To delegate the Database menu:

add_filter( 'wp_dbmanager_capability', function ( $capability, $context ) {
 return 'manage_database';
}, 10, 2 );

The page I need help with: [log in to see the link]