Track support for randomized storage and DB_PATH #513

Track support for randomized SQLite storage and DB_PATH in projects that configure, locate, or copy the database. Existing database paths and older plugin versions should remain supported.

Integration updates

Projects to update for compatibility.

• Randomized SQLite storage — Add randomized SQLite database storage #502
• DB_PATH support — Support DB_PATH as the primary database path constant #512
• WordPress Playground — Support randomized SQLite database storage wordpress-playground#4344
  Covers database path discovery, panels/downloads, and saved Personal WP sites.
• WordPress Playground — Define DB_PATH for explicit SQLite database paths wordpress-playground#4374
  Defines DB_PATH for explicit SQLite database paths.
• WordPress.com Playground importer — wpcomsh: Support randomized SQLite database paths in Playground imports Automattic/jetpack#53023
  Supports legacy and randomized SQLite database paths in Playground imports.
• WP-CLI wp sqlite — Add support for the new SQLite storage Automattic/wp-cli-sqlite-command#36
  Adds storage discovery for import, export, and table listing.
• WP-CLI wp db — Support DB_PATH for SQLite database commands wp-cli/db-command#351
  Update path discovery to prefer DB_PATH over FQDB.
• WP-CLI tests — Simplify SQLite installation caching wp-cli/wp-cli-tests#367
  Cache and restore SQLite databases with the installation files, including randomized storage.
• Reprint — Prefer DB_PATH for SQLite size estimates reprint#863
  Prefer DB_PATH over FQDB when estimating the database size.
• WordPress Studio
  Update fixed paths used by native phpMyAdmin and journal-mode handling; check import/export and update bundled dependencies.
• wp-env — wp-env: Apply SQLite path settings before Playground installation gutenberg#84109
  Applies DB_PATH and legacy path settings before Playground installation, fixing an existing configuration issue.
• Contributor Toolkit — Fix Adminer database selection for randomized SQLite storage contributor-toolkit#619
  Discover the actual database path in Adminer instead of using the fixed .ht.sqlite path.
• Playground WordPress plugin — Fix Playground snapshot imports with randomized SQLite storage playground-tools#416
  Check that database exports include the hidden randomized directory and its path metadata.
• Playground Step Library — Use active SQLite paths in database tools akirk/playground-step-library#34
  Discover the actual database path in the Adminer and phpLiteAdmin steps.
• Markdown Database Integration — Support randomized SQLite storage and DB_PATH Automattic/markdown-database-integration#443
  Support randomized paths in SQLite detection and prefer DB_PATH over FQDB in mirror mode.
• Openstation — Prefer DB_PATH for phpMyAdmin SQLite connections openstation#963
  Prefer DB_PATH over FQDB in phpMyAdmin.

Third-party follow-up

Projects to notify about compatibility updates.

• All-in-One WP Migration — https://wordpress.org/support/topic/sqlite-database-integration-3-1-compatibility/
  Prefer DB_PATH over FQDB for database-file exclusions; check randomized-storage metadata during restore.
• Pronamic Client
  Prefer DB_PATH over FQDB in Adminer.
• InstaWP CLI
  Discover the actual database path for database push and clone detection.
• Static Playground
  Accept randomized database paths when validating Playground ZIP exports.