When posting/updating content with raw/rendered fields, accepted parameter should not be nested about lifterlms-rest HOT 6 CLOSED

Accidentally I was already only accepting the 'content' => string format when creating/updating. :D

from lifterlms-rest.

Good :-D

The spec needs to make this explicit though, carry on with your mistake I'm working on figuring out how to update the spec accordingly

from lifterlms-rest.

Yes sure, thanks!

from lifterlms-rest.

Documentation is unclear in WP Core but in practice it's possible to create/update a post with either of the following payloads for fields which return an object with rendered and raw properties:

{
    "content": "this is the raw html content"
}

Or:

{
    "content": {
       "raw": "this is the raw html content"
    }
}

So the updated spec will allow for both:

Example spec:

description: Post title.
oneOf:
  - type: string
    description: Raw title.
    example: Getting Started with LifterLMS
    writeOnly: true
  - type: object
    properties:
      rendered:
        type: string
        description: Rendered title.
        example: Getting Started with LifterLMS
        readOnly: true
      raw:
        type: string
        description: Raw title. Useful when displaying title in the WP Block Editor. Only returned in `edit` context.
        example: Getting Started with LifterLMS

from lifterlms-rest.

Mmm yeah I looked at the core code and actually wanted to ask if we wanted to replicate it, but then I thought that no, we didn't want to, why should we? :)
Anyway ok, will update the code to reflect this spec.
Basically the core code looks for the value of the field, if it's a string it will be used, otherwise the 'raw' nested field will be used (if set, of course).
https://github.com/WordPress/WordPress/blob/cf3fa9f7c8038447303eea1fbd3636c5fece28cd/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php#L982
(well you know better than me where to look)

from lifterlms-rest.

Spec ended up looking a little different than above. Documentation will not reflect the way this will work but lets follow the WP core as noted.

from lifterlms-rest.