SQLite Database Integration 3.1 compatibility

  • Jan Jakeš

    (@janjakes)


    1 day, 11 hours ago

    Hi AI1WM,

    We want to let you know that SQLite Database Integration 3.1 introduces DB_PATH and randomized database storage. Two compatibility points appear relevant to All-in-One WP Migration:

    • Database-file exclusion: In version 7.111, Ai1wm_Export_Enumerate_Content::execute() excludes FQDB. Please prefer DB_PATH, falling back to FQDB for older versions. When both constants are defined differently, WordPress uses DB_PATH, so the current exclusion targets the wrong file.
    • Storage metadata during restore: Managed databases now live under wp-content/database/.ht.<random>/.ht.sqlite, with wp-content/database/db-path.php recording their location. Please check that restoring files does not overwrite the destination’s path metadata while excluding the corresponding SQLite database. This restore concern still needs an end-to-end check.

    Existing database paths and older SQLite integration versions should remain supported.

    Tracking issue: https://github.com/WordPress/sqlite-database-integration/issues/513.

    Thanks for looking into this.

Viewing 1 replies (of 1 total)
  • Plugin Author Yani

    (@yaniiliev)

    1 day, 8 hours ago

    Hi Jan,

    Thanks for the detailed heads-up, and for tracking this in issue #513

    I’ve passed this to our product team to investigate against current All-in-One WP Migration. We’ll follow up here once we have a fix or a clearer plan. If there’s anything else we should watch for on the Playground / Studio side, feel free to add it on this thread.

    Thanks again for reaching out.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.

  • 1 reply
  • 2 participants
  • Last reply from: Yani
  • Last activity: 1 day, 8 hours ago
  • Status: not a support question