Opened 23 months ago

Closed 21 months ago

#18076 closed defect (bug) (fixed)

get_term() should never query for term_id = 0

Reported by: mdawaffe Owned by: westi
Priority: normal Milestone: 3.3
Component: General Version: 3.2
Severity: normal Keywords: westi-likes has-patch commit
Cc:

Description

In one branch of its logic, get_term() casts the input as an integer and uses that value to lookup the term by term_id (first in the cache, then in the DB). That's unnecessary for 0.

This can happen on every page load via wp_get_nav_menu_object( $string ).

Attached bails on 0.

Attached also switches the prepared query to use %d instead of %s.

Attachments (1)

18076.diff​ (933 bytes) - added by mdawaffe 23 months ago.

Download all attachments as: .zip

Change History (4)

mdawaffe — 23 months ago

comment:1   westi — 23 months ago

  • Keywords 3.3-early westi-likes commit added
  • Owner set to westi
  • Status changed from new to accepted

comment:2   westi — 21 months ago

  • Keywords 3.3-early removed
  • Milestone changed from Awaiting Review to 3.3

comment:3   westi — 21 months ago

  • Resolution set to fixed
  • Status changed from accepted to closed

In [18591]:

Optimise get_term to not query for term_id = 0. Also improve the prepared query to use %d for the term_id.
Fixes #18076 props mdawaffe.

Note: See TracTickets for help on using tickets.