Skip to:

Opened 8 years ago

Closed 8 years ago

Last modified 6 years ago

#2832 closed task (blessed) (fixed)

post_parent__in support can be deprecated

Reported by: johnjamesjacoby's profile johnjamesjacoby Owned by: johnjamesjacoby's profile johnjamesjacoby
Milestone: 2.6 Priority: normal
Severity: normal Version: 2.1
Component: Tools - Code Improvements Keywords: commit


Support for post_parent__in and post_parent__not_in were added to WordPress core in #WP11056. As a result, we can remove our bbp_query_post_parent__in() filter and rely fully on WordPress to handle this for us going forward.

Change History (4)

#1 @johnjamesjacoby
8 years ago

  • Owner set to johnjamesjacoby
  • Resolution set to fixed
  • Status changed from new to closed

In 5820:

Queries: Remove post_parent__in query-parameter filter.

This commit removes the bbp_query_post_parent__in() filter that was introduced in r2996, and uses WordPress core's built in query parameters introduced in #WP11056.

Fixes #2832.

#2 @netweb
8 years ago

Actually, speaking of blame fu, the bbp_query_post_parent__in() filter was introduced in r2997 ;)

#3 @johnjamesjacoby
8 years ago

Off by one errors and all that. Thanks.

#4 @johnjamesjacoby
6 years ago

In 6410:

Queries: Deprecate bbp_query_post_parent__in() in the 2.5 branch.

4.7 is the minimum WordPress version, so we can support post_parent__not_in directly.

See #2832.

Note: See TracTickets for help on using tickets.