[wp-trac] [WordPress Trac] #45114: Fire publishing related hooks after all data is saved via the REST API.
WordPress Trac
noreply at wordpress.org
Thu Sep 24 03:36:34 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:
---------------------------+-----------------------
Changes (by peterwilsoncc):
* milestone: Awaiting Review => 5.6
Comment:
Moving this on to the 5.6 milestone for visibility.
My proposal is:
* split functions per [attachment:"45114.diff"]
* in REST requests, prevent `wp_insert_post()` from firing the hooks
* Fire the hooks after term and meta updates are processed in REST
requests just prior to the existing hooks
* add some unit tests to the patch
Helen has suggested bringing this ticket up in a dev-chat which I shall do
next week.
The key questions I have are:
* is it too late to fix this back-compat change?
* would a _fix_ end up breaking a bunch of plugins?
* rubber-ducking how this could break things.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/45114#comment:29>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list