#18883: Wordpress - Add automatic fallback for non-pretty permalinks#2080
Open
#18883: Wordpress - Add automatic fallback for non-pretty permalinks#2080
Conversation
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.
Mirror of n8n-io/n8n#20933
Original author: prakharg200
Summary
The WordPress node now automatically handles both pretty and non-pretty permalink configurations. When a request to
/wp-json/returns a 404 error, the node automatically retries using the/?rest_route=format, which works universally across all WordPress permalink settings.Before: WordPress node only worked with pretty permalinks enabled (requires mod_rewrite/nginx configuration)
After: WordPress node works with any permalink configuration automatically - no user configuration needed
Testing
With pretty permalinks: Configure WordPress credentials with pretty permalinks enabled → Request succeeds using
/wp-json/wp/v2/...With plain permalinks: Configure WordPress credentials with plain permalinks → Initial
/wp-json/request fails with 404 → Automatically retries with/?rest_route=/wp/v2/...→ Request succeedsEdge cases: Trailing slashes normalized correctly, non-404 errors don't retry, proper error messages when both formats fail
Related Linear tickets, Github issues, and Community forum posts
Fixes #18883
Review / Merge checklist
release/backport(if the PR is an urgent fix that needs to be backported)