[wp-trac] [WordPress Trac] #45114: Fire publishing related hooks after all data is saved via the REST API.

WordPress Trac noreply at wordpress.org
Wed Sep 30 22:50:35 UTC 2020


#45114: Fire publishing related hooks after all data is saved via the REST API.
---------------------------+-----------------------
 Reporter:  peterwilsoncc  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  reopened
 Priority:  normal         |   Milestone:  5.6
Component:  REST API       |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  dev-feedback   |     Focuses:
---------------------------+-----------------------

Comment (by peterwilsoncc):

 This was discussed at length in the 0500 UTC dev-chat on September 30,
 2020.

 Out of this discussion, three options were suggested for this ticket:

 1. close `wontfix`
 2. move the hooks per my suggestion above
 3. add a new hook/s that fire after posts, their terms and meta data are
 all updated common to the classic editor, REST API, XML-RPC and other
 methods for updating a post.

 At the conclusion of the discussion, attendees were asked for their
 preference and new hook/s was in the majority, followed by moving the
 existing hooks in the REST API.

 Emoji reaction votes are not scientific and lack nuance, but it's worth
 noting the people expressing an opinion all had many years of experience
 contributing the WP Core. The poll can be found in Slack at
 https://wordpress.slack.com/archives/C02RQBWTW/p1601444099240400

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


More information about the wp-trac mailing list