You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an xposts endpoint to the REST API of sites that have the O2 plugin installed.
We are bringing xpost support to the Gutenberg editor in the WordPress mobile apps (see here for WPAndroid and here for WPiOS) but will not be able to support self-hosted sites that are not connected to WP.com via Jetpack.
This is because the endpoint we use is WP.com specific. If the O2 plugin can expose a REST API endpoint on sites where it is installed, we could add xpost support for all self-hosted sites that use the O2 plugin.
A possible workaround would be to use /?get-xpost-data (e.g. mysite.com/?get-xpost-data), which is an cookie-authenticated endpoint that returns xpost suggestions. While using this might be an alternative to constructing a new endpoint, it's not practical on mobile which uses a authentication bearer based token (instead of a cookie) to authenticate.
The text was updated successfully, but these errors were encountered:
Add an xposts endpoint to the REST API of sites that have the O2 plugin installed.
We are bringing xpost support to the Gutenberg editor in the WordPress mobile apps (see here for WPAndroid and here for WPiOS) but will not be able to support self-hosted sites that are not connected to WP.com via Jetpack.
This is because the endpoint we use is WP.com specific. If the O2 plugin can expose a REST API endpoint on sites where it is installed, we could add xpost support for all self-hosted sites that use the O2 plugin.
A possible workaround would be to use
/?get-xpost-data
(e.g.mysite.com/?get-xpost-data
), which is an cookie-authenticated endpoint that returns xpost suggestions. While using this might be an alternative to constructing a new endpoint, it's not practical on mobile which uses a authentication bearer based token (instead of a cookie) to authenticate.The text was updated successfully, but these errors were encountered: