π§βπ» Make WordPress request handling opt-in & configurable #416
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.
For the actual release of v5 we have decided to make the WordPress request handler opt-in. By default, it will be enabled in Sage 10 once that is updated.
Example:
With this, WordPress now uses its own
wordpress
middleware group (which is a copy of defaultweb
) and should allow more fine-grained control.Removing a default middleware from the WordPress group might look something like: