Ticket #5230 (closed defect (bug): fixed)
taxonomy - incorrect php fetch_row in update or insert term
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | high | Milestone: | 2.5 |
| Component: | Administration | Version: | 2.3 |
| Severity: | critical | Keywords: | taxonomy term slug alias_of needs-patch |
| Cc: |
Description
taxonomy - incorrect ->fetch_row in wp_update or wp_insert term :
the script block if $alias_of is present (I am developping new powerful taxonomy features)
must be replace by ->get_row to work and create alias of a previous term
line 1094 and 930
Change History
Just a question :
why the milestone is set to 2.4 ?
why the modification in taxonomy.php can not be made sooner because the 'WordPress DB Class' don't contain the error causing ->fetch_row (never present in other scripts ) and must be replace by ->get_row which solve the pb...
a trac newbies
Replying to michelwp:
Just a question :
why the milestone is set to 2.4 ?
why the modification in taxonomy.php can not be made sooner because the 'WordPress DB Class' don't contain the error causing ->fetch_row (never present in other scripts ) and must be replace by ->get_row which solve the pb...
a trac newbies
In General interim releases e.g. 2.3.1 only contain major bug fixes. Also bugs are fixed in trunk (i.e. 2.4) first and then backported to the current interim release branch if required.
