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
XML-RPC itself can be easily considered as an outdated method of communicating with WP. It is there mainly for backward compatibility and nothing else nowadays.
XML-RPC has its security issues and thus shouldn't be used anywhere.
Most clients suggested by the client software list are very outdated.
Conclusion: as REST API is the modern way to go and XML-RPC should be forgotten, IMO this article should be deleted completely.
Awesome @pekkakortelainen! I agree. As we discussed on Zoom during Contributor Day today, I also think the explanation could use a little improvement as well; maybe a screenshot and/or analogy or something.
I'll assign you to this so you can edit it. Thank you! 🎉
If the proposed redirect happens, should the REST API article (the redirect target for the Weblog Clients article) also get updated to at least make a mention of XML-RPC (that it existed, technically still works, but is outdated, etc)? (Assuming another XML-RPC specific doc page doesn't exist somewhere.)
It seems the REST API article is more of a replacement for the "Develop Your Own" section of the "Weblog Clients" page, but it does not address the main purpose of the page: listing client apps you can use to connect to a WP site. While I'm sure most of those apps are outdated, aren't at least a few still viable such as WordPress.com Desktop App and maybe MarsEdit (last blog entry 4 days ago)? TypeMetal had a release 10 months ago. I didn't check anything else other than ecto, which does seem defunct.
I can totally understand not wanting to maintain an article on weblog clients since it can quickly become out-of-date or omit newcomers unless regularly maintained. However, I feel that decision should be separate from whether documentation for XML-RPC and/or building your own weblog client should link to or redirect to the REST API article.
Activity
github-actions commentedon Sep 26, 2022
Heads up @femkreations @atachibana - the "user documentation" label was applied to this issue.
github-actions commentedon Sep 26, 2022
Heads up @zzap - the "external links" label was applied to this issue.
pekkakortelainen commentedon Aug 24, 2023
Notes after review:
Conclusion: as REST API is the modern way to go and XML-RPC should be forgotten, IMO this article should be deleted completely.
jennimckinnon commentedon Aug 29, 2023
Awesome @pekkakortelainen! I agree. As we discussed on Zoom during Contributor Day today, I also think the explanation could use a little improvement as well; maybe a screenshot and/or analogy or something.
I'll assign you to this so you can edit it. Thank you! 🎉
estelaris commentedon Sep 9, 2023
I have requested a redirect to the REST API article in DevHub. Once that is created, we can delete the HH article and close this issue
github-actions commentedon Oct 17, 2023
Heads up @docs-reviewers - the "[Status] Review" label was applied to this issue.
coffee2code commentedon Jul 31, 2024
If the proposed redirect happens, should the REST API article (the redirect target for the Weblog Clients article) also get updated to at least make a mention of XML-RPC (that it existed, technically still works, but is outdated, etc)? (Assuming another XML-RPC specific doc page doesn't exist somewhere.)
It seems the REST API article is more of a replacement for the "Develop Your Own" section of the "Weblog Clients" page, but it does not address the main purpose of the page: listing client apps you can use to connect to a WP site. While I'm sure most of those apps are outdated, aren't at least a few still viable such as WordPress.com Desktop App and maybe MarsEdit (last blog entry 4 days ago)? TypeMetal had a release 10 months ago. I didn't check anything else other than ecto, which does seem defunct.
I can totally understand not wanting to maintain an article on weblog clients since it can quickly become out-of-date or omit newcomers unless regularly maintained. However, I feel that decision should be separate from whether documentation for XML-RPC and/or building your own weblog client should link to or redirect to the REST API article.