Shabnam Tornado Database Maintenance is a database inspection and maintenance toolkit for WordPress administrators and developers. It combines preview-first cleanup, integrity checks, verified logical backups, reference discovery, and an optional controlled Post ID reindex workflow.<\/p>\n\n
The plugin reads the active WordPress table names from Post ID reindexing is an advanced, destructive operation. It is disabled by default, is not required for ordinary cleanup, and should be tested on a staging copy before use on a production site.<\/p>\n\n The optional reindex workflow creates a dense Tornado uses a collision-resistant two-phase mapping:<\/p>\n\n The Posts table is the source of truth for the mapping. Adapters synchronize references; they do not independently choose or renumber the Posts primary-key sequence.<\/p>\n\n Reindex execution requires matching Discovery, Mapping, and Backup fingerprints. It also requires supported transactional tables, successful Preflight checks, administrator capabilities, a REST nonce, a session-bound one-time authorization token, and an explicit confirmation phrase. Blocking failures before commit cause the operation to stop or roll back.<\/p>\n\n Tornado includes dedicated reference handling for known relationships and a conservative adaptive detector for conventional plugin tables.<\/p>\n\n The adaptive detector can evaluate:<\/p>\n\n Detection is evidence-based. The plugin checks column type, naming, mapping intersection, row resolution, table scope, and compatible WordPress post types. Ambiguous, encrypted, compressed, binary, proprietary, remotely stored, or free-text references are not guessed. They remain blocking until an administrator selects an explicit policy or a dedicated adapter is provided.<\/p>\n\n Tornado includes dedicated or structured handling for selected WordPress, WooCommerce, Elementor, Gutenberg, and Rank Math relationships. It also exposes an adapter registration hook for site-specific integrations.<\/p>\n\n Compatibility does not mean that every extension or external system can be detected automatically. IDs copied to a CRM, ERP, payment gateway, search service, mobile application, custom API, arbitrary HTML, shortcode, URL, or remote database may remain outside WordPress and must be reviewed separately.<\/p>\n\n Cleanup operations provide a Preview before deletion and operate in bounded batches. Supported cleanup categories include:<\/p>\n\n The optional revision archive stores selected snapshots in Tornado's own table instead of keeping ordinary WordPress revision rows indefinitely. Elementor and WooCommerce content can be included according to the configured archive policy. This archive does not replace Elementor's complete editor history or an external backup.<\/p>\n\n Tornado creates local logical SQL backups and verifies the resulting file with SHA-256. By default, backup files are stored below the directory returned by A backup is accepted for reindex only when the required snapshot and protected-storage checks pass. Mixed storage engines or an insufficiently protected custom backup location can produce warnings or prevent the backup from being accepted for reindex.<\/p>\n\n Full database restore is intentionally available through WP-CLI rather than a browser request, reducing the risk of HTTP timeout or connection loss during import.<\/p>\n\n Tornado does not send site data to an external service and does not include usage tracking or telemetry. Administration requests are made to the site's own WordPress REST API.<\/p>\n\n The plugin stores operational data locally, including settings, discoveries, mappings, backup records, jobs, logs, revision archives, and short-lived authorization data. SQL backup files may contain the complete database and must be treated as sensitive data.<\/p>\n\n Uninstall removes scheduled events and plugin capabilities. Operational tables and backup files are removed only when the corresponding uninstall options are enabled by an administrator.<\/p>\n\n Tornado registers commands under Destructive WP-CLI commands require their documented confirmation arguments. Use No No. Post ID reindexing is disabled by default and requires a separate, explicit workflow with Discovery, Mapping, Backup, Preflight, authorization, and typed confirmation.<\/p><\/dd>\n No. Cleanup, revision retention, orphan checks, backup, integrity reporting, and Yes. Core table names are read from Reindexing changes existing IDs and synchronizes registered references. It evaluates schema and data evidence before registering a relationship. Clear conventional references can be included in Preflight and the two-phase mapping. Ambiguous data remains blocked instead of being rewritten by guesswork.<\/p><\/dd>\n Version 1.0.0 includes a dedicated Rank Math adapter for supported internal-link, internal-meta, and analytics object relationships. The adapter is conditional and only acts on tables and columns that exist in the current installation.<\/p><\/dd>\n It includes structured Elementor reference handling, media repair tools, selected builder-registry support, and post-operation CSS or cache rebuilding. Elementor and third-party widget data can vary, so unresolved proprietary paths remain blocking.<\/p><\/dd>\n No. Remote services, custom applications, external databases, exported files, and copied IDs outside the current WordPress database must be audited separately.<\/p><\/dd>\n No. Backups are created locally. The default location is a protected, randomized Tornado directory below the WordPress uploads base directory returned by The plugin can inspect the active site's tables, but network-wide Multisite reindexing is intentionally not supported. Do not use the reindex workflow as a network-wide operation.<\/p><\/dd>\n Reindex remains blocked. Review the table and column, choose an explicit supported policy, register a site-specific adapter, or leave the operation unexecuted.<\/p><\/dd>\n Scheduled hooks and Tornado capabilities are removed. By default, operational tables and backup files are retained to avoid accidental data loss. They are deleted only when the relevant uninstall settings were enabled before uninstalling.<\/p><\/dd>\n\n<\/dl>\n\n\n WordPress.org pre-review fixes: standardized backup storage resolution, hardened protected backup paths and serialized-data handling, and clarified third-party Elementor option writes.<\/p><\/li>\n Published under the $wpdb<\/code>. It does not assume the default wp_<\/code> prefix, so installations using custom prefixes such as shcd_<\/code> are supported.<\/p>\n\nMain features<\/h4>\n\n
\n
INFORMATION_SCHEMA<\/code>, including tables, columns, indexes, engines, and foreign keys.<\/li>\nAUTO_INCREMENT<\/code> normalization without renumbering existing rows.<\/li>\nControlled Post ID reindexing<\/h4>\n\n
1..N<\/code> sequence for rows in the active $wpdb->posts<\/code> table. This includes posts, pages, custom post types, revisions, and Media Library attachments that still exist when the mapping is created.<\/p>\n\n\n
AUTO_INCREMENT<\/code> value.<\/li>\n<\/ol>\n\nAdaptive plugin-reference detection<\/h4>\n\n
\n
post_id<\/code>, page_id<\/code>, product_id<\/code>, or attachment_id<\/code>.<\/li>\nobject_id<\/code> with object_type<\/code>, or element_id<\/code> with element_type<\/code>.<\/li>\nPlugin and builder compatibility<\/h4>\n\n
Cleanup and revision management<\/h4>\n\n
\n
Backups and recovery<\/h4>\n\n
wp_upload_dir()<\/code> in a Tornado-owned directory with a persisted random storage token, restrictive file permissions, and Apache\/IIS deny files. A site administrator may explicitly provide SHCD_TORNADO_DBM_BACKUP_DIR<\/code> for a custom storage location. A backup records the Posts ID fingerprint, schema fingerprint, consistency status, and storage classification.<\/p>\n\nImportant limitations<\/h4>\n\n
\n
Privacy<\/h3>\n\n
Requirements<\/h3>\n\n
\n
INFORMATION_SCHEMA<\/code> metadata.<\/li>\nWP-CLI<\/h3>\n\n
wp shcd-tornado-dbm<\/code> when WP-CLI is available. Examples include:<\/p>\n\n\n
wp shcd-tornado-dbm discover<\/code><\/li>\nwp shcd-tornado-dbm mapping build<\/code><\/li>\nwp shcd-tornado-dbm dry-run <mapping-uuid><\/code><\/li>\nwp shcd-tornado-dbm backup create<\/code><\/li>\nwp shcd-tornado-dbm integrity check<\/code><\/li>\nwp shcd-tornado-dbm cleanup preview<\/code><\/li>\nwp shcd-tornado-dbm cleanup execute --yes<\/code><\/li>\nwp shcd-tornado-dbm tables scan-unused<\/code><\/li>\nwp shcd-tornado-dbm reindex prepare<\/code><\/li>\nwp shcd-tornado-dbm reindex preflight <mapping-uuid> <backup-uuid><\/code><\/li>\n<\/ul>\n\nwp help shcd-tornado-dbm<\/code> for the commands available in the installed version.<\/p>\n\n\n\n
shcd-database-maintenance<\/code> directory to \/wp-content\/plugins\/<\/code>, or install the ZIP through Plugins > Add New > Upload Plugin.<\/li>\nwp-config.php<\/code> edit is required for normal operation. An optional emergency constant can disable destructive operations; review the plugin settings and inline administrator guidance before enabling destructive operations.<\/p>\n\n\n\n
Does Tornado automatically renumber my WordPress posts?<\/h3><\/dt>\n
Do I need reindexing to clean the database?<\/h3><\/dt>\n
AUTO_INCREMENT<\/code> normalization can be used without changing existing Post IDs.<\/p><\/dd>\nDoes it support a custom database prefix?<\/h3><\/dt>\n
$wpdb<\/code>, and plugin tables are resolved from the active $wpdb->prefix<\/code>. The plugin does not hard-code wp_posts<\/code>.<\/p><\/dd>\nWhat is the difference between Post ID reindexing and AUTO_INCREMENT normalization?<\/h3><\/dt>\n
AUTO_INCREMENT<\/code> normalization changes only the next generated value when the database allows it; it does not renumber existing rows or remove interior gaps.<\/p><\/dd>\nHow does adaptive detection handle an unknown plugin table?<\/h3><\/dt>\n
Does the plugin support Rank Math?<\/h3><\/dt>\n
Does the plugin support Elementor?<\/h3><\/dt>\n
Can Tornado detect IDs stored outside WordPress?<\/h3><\/dt>\n
Are backups sent to another server?<\/h3><\/dt>\n
wp_upload_dir()<\/code>. Administrators remain responsible for server permissions, off-site backups, encryption, retention, and restore testing.<\/p><\/dd>\nIs Multisite supported?<\/h3><\/dt>\n
What happens when Preflight finds an unresolved reference?<\/h3><\/dt>\n
What happens when I uninstall the plugin?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n
shcd-database-maintenance<\/code> repository slug and matching text domain.<\/p><\/li>\n$wpdb<\/code>.<\/li>\n