Make WordPress Core

Opened 13 years ago

Closed 12 days ago

#23020 closed defect (bug) (wontfix)

wp.getPageList should act like wp.getPages

Reported by: daniloercoli's profile daniloercoli Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.2
Component: XML-RPC Keywords: has-patch needs-refresh dev-feedback
Focuses: Cc:

Description

I know that wp.getPageList is obsolete, but I think it should act like wp.getPages At the moment wp.getPageList returns even the trashed pages and doesn't return the status of the page.

The weird behavior i've seen with wp.getPageList on a third-party client is shown below:

  • Refresh the pages list.
  • The Page 'A' is in the list.
  • Select the page 'A' and delete it.
  • Refresh the pages list and the page is still there. Doh!

Attachments (1)

wp_getPageList.diff (2.1 KB) - added by daniloercoli 13 years ago.

Download all attachments as: .zip

Change History (5)

#1 @SergeyBiryukov
13 years ago

  • Version changed from trunk to 2.2

#2 @redsweater
13 years ago

It seems like it would be harmless to add additional information e.g. the status of a page, but changing the behavior to no longer include pages that previously were included seems dangerous to existing clients. Is it possible some clients are relying on the old functionality to e.g. include trashed pages?

You might consider adding a 4th, optional parameter to wp.getPageList that would be suitable for limiting the statuses of pages that are returned. Then again, perhaps I'm overthinking it, but do at least think about whether clients may be depending on the generous return values of this method.

#3 @chriscct7
10 years ago

  • Keywords needs-refresh dev-feedback added; mobile removed
  • Severity changed from minor to normal

#4 @callumbw95
12 days ago

  • Resolution set to wontfix
  • Status changed from new to closed

Hi All,
Just taken a look into this, and as the XML-RPC feature as a whole is no longer under active development in WordPress Core and is considered a legacy API it makes sense to close this ticket. The focus for all modern WordPress development has shifted to the REST API.
As of such I will mark this ticket as invalid but please feel free to reopen this if you wish to further continue this discussion. 😃

Note: See TracTickets for help on using tickets.