WordPRess GSoC

Opened 2 years ago

Last modified 22 months ago

#328 new defect

Cannot get other fields when creating a post

Reported by: rmccue Owned by:
Milestone: Priority: normal
Component: JSON REST API Keywords:


It's not possible to create a new post and get back a representation that includes the *_raw fields (or any other non-default fields).

The best solution IMO is to abolish the whole idea of separate fields entirely. Maybe introducing a mode parameter just for the *_raw fields (and automatically enabling this for results from creation/updating), however this still means there's variability.

Change History (6)

#1 @rmccue
2 years ago

  • Priority changed from normal to critical

This causes the tests to fail, so bumping priority.

#2 @rmccue
2 years ago

In 2265:

Goodbye fields, hello context.

See #328.

#3 @rmccue
2 years ago

In 2280:

prepare_post() no longer takes fields

See #328

#4 @rmccue
2 years ago

Appears to be a few small issues where this doesn't get passed around correctly (checking if the user can read a post, e.g.). Leaving open for that.

#5 @bpetty
2 years ago

  • Milestone 2013 Midterm (Beta) deleted
  • Priority changed from critical to normal

Removing milestone as this isn't priority for GSoC deadline.

#6 @dotnetCarpenter
22 months ago

Just so I understand this issue correctly. This means that "Custom fields" in a post is not supported?

Note: See TracTickets for help on using tickets.