[wp-trac] [WordPress Trac] #54125: Rest API tax_relation=OR doesn't seem to work correctly

WordPress Trac noreply at wordpress.org
Fri Aug 2 17:57:21 UTC 2024


#54125: Rest API tax_relation=OR doesn't seem to work correctly
-------------------------------+------------------------------
 Reporter:  roverlap           |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  REST API           |     Version:  5.8
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  rest-api
-------------------------------+------------------------------
Changes (by antonvlasenko):

 * keywords:   => reporter-feedback


Comment:

 == Reproduction report.

 === Environment
 - WordPress: 6.7-alpha-58576-src
 - PHP: 7.3.33
 - Server: Apache/2.4.57 (Unix) PHP/7.3.33
 - Database: mysqli (Server: 5.7.43 / Client: mysqlnd 5.0.12-dev)
 - Browser: Safari 17.6 (macOS)
 - Theme: Twenty Twenty-Three 1.5
 - MU-Plugins: None activated
 - Plugins:
   * WordPress Beta Tester 3.5.3

 === Actual Results
 - ❌ Bug cannot be reproduced.

 === Additional Notes
 I've created four posts with related term objects. When executing the
 following REST API query:
 `/wp/v2/custompost?&_fields=id,title&custom-tax1=ID1&custom-
 tax2=ID2&tax_relation=OR`

 the endpoint correctly returned the first two post objects. The database
 query executed was:
 {{{
 SELECT SQL_CALC_FOUND_ROWS  wp_posts.ID
                                          FROM wp_posts  LEFT JOIN
 wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id)
                                          WHERE 1=1  AND (
   wp_term_relationships.term_taxonomy_id IN (2)
   OR
   wp_term_relationships.term_taxonomy_id IN (3)
 ) AND wp_posts.post_type = 'custompost' AND ((wp_posts.post_status =
 'publish'))
                                          GROUP BY wp_posts.ID
                                          ORDER BY wp_posts.post_date DESC
                                          LIMIT 0, 10
 }}}

 and it returned correct results.

 Are you able to reproduce this bug on the latest (6.6) WordPress version,
 @roverlap? If not, could this ticket be closed?

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


More information about the wp-trac mailing list