Opened 5 months ago

Last modified 2 weeks ago

#23169 new enhancement

Introduce register_post_status_for_object_type

Reported by: kovshenin Owned by:
Priority: normal Milestone: Future Release
Component: General Version:
Severity: normal Keywords: needs-patch editorial-flow
Cc: danielbachhuber, sabreuse, sirzooro, DrewAPicture, justin@…, kovshenin, lol@…, maorhaz@…, pippin@…

Description

Similar to what register_taxonomy_for_object_type does with taxonomies.

Attachments (1)

23169.patch​ (1.6 KB) - added by SergeyBiryukov 5 months ago.

Download all attachments as: .zip

Change History (12)

comment:1   sirzooro — 5 months ago

IMHO this should go to #12706.

comment:2   sabreuse — 5 months ago

  • Cc sabreuse added

comment:3   sirzooro — 5 months ago

  • Cc sirzooro added

comment:4   DrewAPicture — 5 months ago

  • Cc DrewAPicture added

SergeyBiryukov — 5 months ago

comment:5 follow-up: ↓ 7   SergeyBiryukov — 5 months ago

Took a stab in 23169.patch​.

comment:6   greenshady — 4 months ago

  • Cc justin@… added

comment:7 in reply to: ↑ 5   kovshenin — 4 months ago

  • Cc kovshenin added

Replying to SergeyBiryukov: In 23169.patch​ you set the default post types to post and page, but there may be existing plugins that rely on their registered post status to apply to all post types, including custom post types. For backwards compatibility, I think that if the post_type/object_type argument is omitted in register_post_status, we should register for all post statuses, which can also be tricky, because at the time of calling, some post types might not be registered yet.

comment:8   sc0ttkclark — 3 months ago

  • Cc lol@… added

comment:9   maor — 3 months ago

  • Cc maorhaz@… added

comment:10   mordauk — 2 weeks ago

  • Cc pippin@… added

comment:11   SergeyBiryukov — 2 weeks ago

  • Milestone changed from 3.6 to Future Release
Note: See TracTickets for help on using tickets.