[Web] Fix bugs with running personal WP dev server#3391
Merged
brandonpayton merged 3 commits intotrunkfrom Mar 13, 2026
Merged
Conversation
brandonpayton
added
[Type] Bug
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the offline asset caching ignore list so the my.wordpress.net dev server (port 5401) isn’t treated as cacheable/offline content, preventing asset load failures during local development.
Changes:
- Added
127.0.0.1:5401andlocalhost:5401to theshouldCacheUrlignore list.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
brandonpayton
changed the title
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
There are some places in Playground that do not properly acknowledge the personal-wp dev server origin of
http://127.0.0.1:5401:In addition, the local CORS proxy was not working for @zaerl and I, and @zaerl noticed that the CORS proxy output was being corrupted by an inline warning due to
curl_close()being deprecated in PHP 8.5+.Implementation details
http://127.0.0.1:5401to the relevant allow and exclude lists.display_errorsto zero in cors-proxy.phpcurl_close()when the PHP version is below 8.5Testing Instructions (or ideally a Blueprint)
npx nx dev playground-personal-wpon a clean browser env and confirm it loads the Your WordPress welcome page.