We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
By other words: Guttenberg uses for internal REST API requests "siteurl" domain instead of "home" domain
The text was updated successfully, but these errors were encountered:
Hi there! thanks for opening the issue.
I believe this was already discussed before and that it's the right approach. REST API folks would know more. cc @spacedmonkey @TimothyBJacobs
Sorry, something went wrong.
Yeah, Gutenberg is using the WordPress APIs for these things so it is the correct behavior according to core.
A core trac ticket was created as well but closed because that is the intended behavior and a filter exists to change it.
Thanks @TimothyBJacobs
@youknowriad There is more about this issue #1761 Actually Gutenberg is using incorrect url, core return correct one if you test it ;/
No branches or pull requests
reason is that Guttenberg's internal request leads to
http://another-frontend-domain.com/index.php?rest_route=%2Fwp%2Fv2%2Fpages%2F2&_locale=user
expected is internal request to
http://some-wp-domain.com/index.php?rest_route=%2Fwp%2Fv2%2Fpages%2F2&_locale=user
By other words: Guttenberg uses for internal REST API requests "siteurl" domain instead of "home" domain
The text was updated successfully, but these errors were encountered: