You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#48 Introduced a support for file uploads. Unfortunately it introduces an assumption that all requests to /wp-content/uploads/* should be resolved from the WASM filesystem, and all other non-PHP requests should be resolved from the server where wordpress-wasm is hosted.
Let's relax that constraint and correctly serve the static files from either the server or the WASM filesystem regardless of their path.
The text was updated successfully, but these errors were encountered:
adamziel
changed the title
[Browser] Support uploads to paths different than /wp-content/uploads
Support uploads to paths different than /wp-content/uploads
Oct 22, 2022
eruizdechavez
pushed a commit
to eruizdechavez/wordpress-playground
that referenced
this issue
Sep 20, 2023
FixesWordPress/playground-tools#4
## What?
Updates the VS Code Extension to work with the latest implementation of
`wp-now`.
## Why?
It's broken otherwise.
## How?
<!-- How is your PR addressing the issue at hand? What are the
implementation details? -->
## Testing Instructions
1. Follow the new CONTRIBUTING instructions to run the VS Code Extension
locally.
2. Verify 'Start server' launches a new WordPress Playground.
3. Verify it's possible to switch PHP and WordPress versions.
<!-- Please include step by step instructions on how to test this PR.
-->
<!-- 1. Check out the branch. -->
<!-- 2. Run a command. -->
<!-- 3. etc. -->
#48 Introduced a support for file uploads. Unfortunately it introduces an assumption that all requests to
/wp-content/uploads/*
should be resolved from the WASM filesystem, and all other non-PHP requests should be resolved from the server where wordpress-wasm is hosted.Let's relax that constraint and correctly serve the static files from either the server or the WASM filesystem regardless of their path.
The text was updated successfully, but these errors were encountered: