Register OAuth Rewrite Path #130
Merged
Conversation
This file contains 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
|
The tests fail because WordPress redirects to The responsible code is here in core: https://github.com/WordPress/wordpress-develop/blob/a4123728068e09200d7dfe2d5a88f803c1adf2aa/src/wp-includes/canonical.php#L695-L697 So rest routes get special treatment, I think this is what we need to convert this to. |
|
I found another solution, so I think this is ready. |
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.
When a post exists on the WordPress site that includes the word "authorize", WordPress redirects there instead of letting EMA handle the path.
This adds the necessary rewrite routing for this. In the course I fixed two more bugs:
'^'prevandnextas intended and also only for our own REST requests.Fixes #129.