[Website] Fix phpMyAdmin page not found in Personal WP - #4154
Merged
Conversation
brandonpayton
requested review from
a team,
bgrgicak and
Copilot
and removed request for
Copilot
July 22, 2026 22:02
Member
Author
|
This tests well in both Playground web app and Personal WP. Let's go ahead and merge it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation for the change, related issues
In Personal WP, choosing Site Tools → Database → Open phpMyAdmin opens a new tab, but that tab shows Page Not Found.
phpMyAdmin is installed at
/tools/phpmyadmin, outside the WordPress document root. This location is intentional because it keeps phpMyAdmin out of site exports. The browser opens/phpmyadmin, so the PHP request handler needs a path alias that says: “serve/phpmyadminrequests from/tools/phpmyadmin.”The regular Playground website registered this alias, but Personal WP has a separate boot path and did not register it. The request therefore fell through to WordPress, which returned its normal 404 page.
The public URL and filesystem path were also repeated across the website, Personal WP, and CLI. Keeping separate copies made it possible for one application to miss part of the routing setup.
Implementation details
@wp-playground/tools.The test uses a small probe instead of downloading the full phpMyAdmin archive. This keeps the regression test focused on the broken URL-to-filesystem mapping.
There are no intentional breaking changes.
Testing Instructions (or ideally a Blueprint)
Automated checks run:
npm exec nx -- run-many --targets=typecheck,lint --projects=playground-tools,playground-personal-wp,playground-website,playground-cli --parallel=4 --output-style=staticnpm exec nx -- run playground-personal-wp:e2e:playwright -- --reporter=list --workers=1 --retries=0— 9 tests passed with no retries.Manual review:
npx nx dev playground-personal-wp.wp_poststable is listed.