[wp-trac] [WordPress Trac] #12939: Counterpart to content_save_pre hook not called when getting post content via API

[WordPress Trac]

#12939: Counterpart to content_save_pre hook not called when getting post content
via API
--------------------------+------------------------------
 Reporter:  redsweater    |       Owner:  josephscott
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  XML-RPC       |     Version:  2.9.2
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |     Focuses:
--------------------------+------------------------------
Changes (by DrewAPicture):

 * keywords:   => dev-feedback
 * status:  closed => reopened
 * resolution:  invalid =>
 * milestone:  Future Release => Awaiting Review


Comment:

 To my knowledge, there has never been a `post_content_save_pre` hook, that
 is to say `{$field}_save_pre`. In the case where the field is passed into
 `sanitize_post_field()` with a prefix, two filter hooks are evaluated,
 [https://developer.wordpress.org/reference/hooks/pre_field/ pre_{$field}]
 -- in this case `pre_post_content` -- followed by
 [https://developer.wordpress.org/reference/hooks/field_no_prefix_save_pre/
 {field_no_prefix}_save_pre], in this case `content_save_pre`.

 Based on the comments, I don't think it was ever actually confirmed
 whether the correct (or incorrect) filter hooks were fired for XML-RPC
 requests or not, so moving back to Awaiting Review for investigation.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/12939#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform