Remove AtomPub from core
|Reported by:||nacin||Owned by:|
|Component:||AtomPub||Keywords:||has-patch dev-feedback needs-testing|
AtomPub never received any traction, inside WordPress or out. It's very outdated (written from before there were pages, and when attachments were a post status).
It's hardly used. A stat I heard from WordPress.com is that 200-300 posts per day are published using it, across tens of millions of sites, compared to hundreds of thousands for XML-RPC.
And, unlike XML-RPC, it receives zero love from developers (very few bug reports or enhancements ever filed, and I can count on one hand the number from the last two years), which leads to unfortunate patches when it falls out of date with the rest of core.
Who wants in? Removal process:
Delete wp-app.php and class-wp-atom-server.php. Keep atomlib.php.
If necessary for backwards compatibility, we will stub log_app() somewhere, as well as stub wp_atom_server with a __call method to avoid fatal errors. There must be existence checks here so a plugin can load them back.
Catch wp-app.php requests through WP_Rewrite and deliver a 403 message (as if it were disabled from the admin).
Remove wp-app.php from xmlrpc.php?rsd, and add a hook in there so a plugin can add it back.
Create a plugin that handles wp-app.php, overriding the WP_Rewrite 403, returning a reference to xmlrpc.php?rsd, etc.
Remove all references to APP_REQUEST, instead hiding the admin bar with the show_admin_bar filter, filtering the wp_die() handler with wp_die_handler, and firing the app_publish_post hook off 'publish_post' on our own. The plugin should still define APP_REQUEST for compatibility.
Remove the enable_app option from the DB and the UI. (Related, #21509 for XML-RPC.)
Change History (8)
comment:2 @wonderboymusic — 3 years ago
- Keywords has-patch dev-feedback needs-testing added
- Version set to 2.3
- Resolution set to fixed
- Status changed from new to closed