WordPress.org

Make WordPress Core

Opened 12 years ago

Closed 7 years ago

#7301 closed enhancement (wontfix)

AtomPub interface should accept new categories provided by clients

Reported by: redsweater Owned by: josephscott
Milestone: Priority: normal
Severity: normal Version: 2.6
Component: AtomPub Keywords: needs-patch
Focuses: Cc:

Description

The AtomPub interface successfully exposes access to the existing categories of a particular blog, via the URL:

http://[myblog]/wp-app.php/categories

But the category listing is identified as "fixed", and this pans out. When a client attempts to provide a category term with a name that has not been seen before, the interface just ignores it.

It would be a nice enhancement to change the category collection to an editable one, and support provision of arbitrary new category names on supplied posts to the wp-app interface.

As it is now, there is no way to add categories via the AtomPub interface.

Change History (11)

#1 @matt
12 years ago

  • Milestone changed from 2.7 to 2.8

#2 @AlanJCastonguay
12 years ago

A quick read of wp_set_object_terms() suggests that if a new post/page entry is provided when creating/updating a post/page, the new category will be added to the category taxonomy, rather than ignored. The new category would then be visible at /wp-app.php/categories.

Still, the /wp-app/categories interface is not a collection, and one cannot PUT or DELETE a category from the AtomPUB API.

#3 @FFEMTcJ
12 years ago

  • Keywords needs-patch added
  • Milestone changed from 2.8 to Future Release

#4 @Denis-de-Bernardy
11 years ago

  • Component changed from General to XML-RPC

#5 @josephscott
11 years ago

  • Component changed from XML-RPC to AtomPub

#6 @Japh
8 years ago

  • Cc japh@… added
  • Resolution set to invalid
  • Status changed from new to closed

Changes to the AtomPub protocol should now happen in the Atom Publishing Protocol plugin.

#7 @SergeyBiryukov
8 years ago

  • Keywords needs-patch removed
  • Milestone Future Release deleted

#8 @markoheijnen
8 years ago

Do we really close tickets like this as invalid since AtimPub can be removed from core it doesn't mean we should loose this tickets.
We only shouldn't accept new ones.

#9 @Japh
8 years ago

Well we're not "losing it", as it is still here historically. But if the issue still exists, it's no longer a core issue, and my comment should have notified the OP that it needs posting elsewhere.

#10 @SergeyBiryukov
8 years ago

  • Keywords needs-patch added
  • Milestone set to WordPress.org
  • Resolution invalid deleted
  • Status changed from closed to reopened

Perhaps we should track AtomPub plugin tickets in WordPress.org milestone, like we do for importers.

#11 @nacin
7 years ago

  • Milestone WordPress.org deleted
  • Resolution set to wontfix
  • Status changed from reopened to closed

As AtomPub was removed from core in 2012, see #21866. There is a plugin for it here: http://wordpress.org/plugins/atom-publishing-protocol/.

I doubt anyone really interfaces with WordPress via AtomPub anymore. Did anyone ever truly use it? I heard that when WordPress.com had it enabled, a few dozen posts came through it a day, all from few clients.

So realistically, AtomPub is essentially considered "end of life" to us. This plugin was merely done for backwards compatibility.

Closing this ticket as wontfix.

Note: See TracTickets for help on using tickets.