Skip to content

Remote.html: Preload the SQLite database plugin, but only execute it if there's no custom db.php inside wp-content - #1424

Merged
adamziel merged 1 commit into
trunkfrom
preload-sqlite-in-remote-html
May 20, 2024
Merged

Remote.html: Preload the SQLite database plugin, but only execute it if there's no custom db.php inside wp-content#1424
adamziel merged 1 commit into
trunkfrom
preload-sqlite-in-remote-html

Conversation

@adamziel

@adamziel adamziel commented May 17, 2024

Copy link
Copy Markdown
Collaborator

What is this PR doing?

This PR always preloads the SQLite plugin in remote.html, even if the provided WordPress already ships one. The preloaded plugin will only be used if no wp-content/db.php drop-in plugin is found in the filesystem. This change sets the stage for:

Related to Boot Protocol

Problem solved

We want the official WordPress release .zip to just work in Playground. Currently it doesn't because remote.html expects a pre-processed build with the SQLite plugin already baked-in. This PR, in conjunction with #1425 and #1426, remove that requirement.

Testing Instructions

Confirm the CI checks pass.

…if there's no custom db.php inside wp-content
@adamziel adamziel added this to the Boot Protocol milestone May 17, 2024
@adamziel adamziel removed this from the Boot Protocol milestone May 17, 2024
@adamziel adamziel mentioned this pull request May 17, 2024
1 task
adamziel added a commit that referenced this pull request May 18, 2024
Replaces a series of custom steps meant to unzip and configure WordPress with passinf the build zip as a preferredVersion.

To test, go to the WordPress PR previewer locally and try previewing one of the recent PRs. Confirm the installed WordPress versions is indeed not the latest stable.

Do not merge until these PRs are merged:

* #1423 
* #1424 
* #1425 
* #1426 
* #1427
@adamziel
adamziel merged commit aa1e061 into trunk May 20, 2024
@adamziel
adamziel deleted the preload-sqlite-in-remote-html branch May 20, 2024 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment