Make WordPress Core

Opened 7 years ago

Closed 3 years ago

#9031 closed enhancement (wontfix)

Support more URL schemes in Atompub backend

Reported by: znarfor Owned by: josephscott
Milestone: Priority: normal
Severity: normal Version: 2.7
Component: AtomPub Keywords: needs-patch atom
Focuses: Cc:


Today, browsing posts through Atompub backend is very limited. You have only one endpoint (wp-app.php/posts) and the ability to iterate on it (page 2, page 3, page X). You have no way to query or refine your search at all (filter by author, by tag, search, etc).

Too bad, because WP ship with everything needed in its core to do that very easily.

What i propose is to handle URLs in Atompub the same way they are supported in Wordpress core. All we need is:

1) Add a new route in Atompub backend, to match this kind of queries (not exhaustive):

  • wp-app.php/posts/author/xxx
  • wp-app.php/posts/author/xxx/page/2
  • wp-app.php/posts/tag/xxx
  • wp-app.php/posts?s=XXXX

2) Handle Atompub requests correctly in WP::parse_request

3) Remove Atompub current offset & pagination handling, let WP core do the job.

4) Generate correctly next/last/prev/self Atom links

Attachments (2)

wp-app-more_urls.diff (1.8 KB) - added by znarfor 7 years ago.
wp-classes-handle-app.diff (845 bytes) - added by znarfor 7 years ago.

Download all attachments as: .zip

Change History (7)

#1 @josephscott
7 years ago

  • Cc joseph@… added
  • Component changed from General to AtomPub
  • Owner changed from anonymous to josephscott

Couple of things I noticed when I tried out these patches:

Typo on this line: wp('what_to_show=posts&orderby=modified'));

Should be: wp('what_to_show=posts&orderby=modified');

This removes the posts collection (wp-app.php/posts) from the service document

There doesn't appear to be any way to discover these other URLs that can be used

#2 @znarfor
7 years ago

  • Cc znarf@… added

Right Joseph, this patch needs more work. I will update the ticket when i'll have something better.

#3 @ryan
7 years ago

  • Milestone changed from 2.8 to Future Release

#4 @Denis-de-Bernardy
6 years ago

  • Keywords needs-patch added; has-patch removed

#5 @nacin
3 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

No traction, closing.

Note: See TracTickets for help on using tickets.