Mea culpa
The release of Acorn v4 introduced a Laravel wrapper for WordPress responses. It would capture the WordPress response and convert it into a standard interoperable http message so that users could add third-party middleware to it and treat it as a response object that you’d find in frameworks like Laravel or Symfony.
Things didn’t go as planned.
We’ve dropped this wrapper as part of the standard Acorn v4 installation and put it behind an experimental flag.
We would still like to include it in an upcoming release of Acorn. If you want to test or contribute, you can reenable it by adding the following to your .env.
ACORN_ENABLE_EXPERIMENTAL_WORDPRESS_REQUEST_HANDLER=true
Sorry for any headaches this may have caused anyone over the last week.
Kind Regards,
QWp6t
What’s Changed
add experimental flag for WordPress request handler by @QWp6t in 🚩 add experimental flag for WordPress request handler by QWp6t · Pull Request #348 · roots/acorn · GitHub
Fix is_file()deprecation warning by @joshf in https://github.com/roots/acorn/pull/340- Let WP handle requests that should trigger a canonical redirect by @tombro in https://github.com/roots/acorn/pull/346
- Fix missing migration providers by @ben in https://github.com/roots/acorn/pull/347
Deprecations in CI action by @dr5hn in https://github.com/roots/acorn/pull/341
Remove Fruitcake CORS service provider by @dsturm in https://github.com/roots/acorn/pull/343
New Contributors
- @dr5hn made their first contribution in https://github.com/roots/acorn/pull/341
Full Changelog: https://github.com/roots/acorn/compare/v4.0.1...v4.0.2