Make WordPress Core

Opened 20 months ago

Last modified 7 weeks ago

#43516 reviewing enhancement

Allowing default category to be applied to all CPT associated to 'category' taxonomy

Reported by: enrico.sorcinelli Owned by: SergeyBiryukov
Milestone: Future Release Priority: normal
Severity: normal Version: 5.1
Component: Taxonomy Keywords: has-unit-tests has-patch
Focuses: Cc:
PR Number:


This patch allows to apply the default category term also for post types that have the category taxonomy, not only for post.

It's not a too remote case to register new post type and associate it also with the category taxonomy.
Currently in this case, the default_category option value is never applied.

I sent two patches. The first one apply the default category term to all post types associated with the category taxonomy.

If for legacy reason we don't want introduce any behaviour compatibility break - for example with third party plugins - I sent the second one that introduce a new default_category_post_types filter allowing to define for which post types (in addition to post) to set the default_category.

Attachments (2)

43516.default-category-all-cpt.patch (3.0 KB) - added by enrico.sorcinelli 20 months ago.
43516.default-category-filter-cpt.patch (3.7 KB) - added by enrico.sorcinelli 20 months ago.

Download all attachments as: .zip

Change History (11)

#1 @enrico.sorcinelli
20 months ago

  • Keywords has-unit-tests has-patch added

#2 @SergeyBiryukov
20 months ago

  • Milestone changed from Awaiting Review to 5.0
  • Owner set to SergeyBiryukov
  • Status changed from new to reviewing

This ticket was mentioned in Slack in #core by enrico.sorcinelli. View the logs.

17 months ago

#5 @pento
13 months ago

  • Milestone changed from 5.0 to 5.1

#6 @pento
10 months ago

  • Milestone changed from 5.1 to 5.2

#7 @desrosj
8 months ago

  • Milestone changed from 5.2 to 5.3

This ticket has not received any attention during the 5.2 cycle. With beta 1 tomorrow, going to punt this to 5.3.

#8 @davidbaumwald
7 weeks ago

@SergeyBiryukov Can this be reasonably included for version 5.3 Beta 1 tomorrow? If not, can we punt this to 5.4?

#9 @davidbaumwald
7 weeks ago

  • Milestone changed from 5.3 to Future Release

With version 5.3 Beta 1 releasing shortly, this enhancement is being punted to Future Release.

Note: See TracTickets for help on using tickets.