[wp-trac] [WordPress Trac] #35082: get_adjacent_post() when using in term doesn't account for child terms

[WordPress Trac]

#35082: get_adjacent_post() when using in term doesn't account for child terms
-------------------------------+-----------------------------
 Reporter:  WazzaJB            |       Owner:
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Future Release
Component:  Posts, Post Types  |     Version:  trunk
 Severity:  normal             |  Resolution:
 Keywords:  needs-patch        |     Focuses:  template
-------------------------------+-----------------------------

Comment (by WazzaJB):

 I was always on the fence about whether this was a bug or should be tagged
 as enhancement, I think it entirely rests on the use case for the
 taxonomy. My example above is a really sound reason of why you'd expect
 this behaviour, however some users may want/expect the current approach
 which is much looser.

 I agree, this is quite a massive change and as you state it could have
 dire consequences for other sites. I'll have a deeper look at #26937 and
 see if there is anything I can potentially add into the mix however I
 would say that moving to WP_Query is probably not viable, performance and
 backwards compatibility being the primary reasons.

 I'll have a look at creating a patch with a filter approach so that more
 can be manipulated with this.

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