Opened 12 years ago
Closed 9 years ago
#21977 closed defect (bug) (fixed)
Allow 0, NULL and empty string values for 'parent'.
Reported by: | sam2kb | Owned by: | wonderboymusic |
---|---|---|---|
Milestone: | 4.4 | Priority: | normal |
Severity: | normal | Version: | |
Component: | XML-RPC | Keywords: | has-patch |
Focuses: | Cc: |
Description
We must allow 0, NULL and empty string values for 'parent' in wp_newTerm and wp_editTerm
Attachments (4)
Change History (16)
#1
@
12 years ago
- Milestone changed from Awaiting Review to 3.5
- Severity changed from major to normal
#2
@
12 years ago
Looks like test_parent_empty() will need to change, and probably be expanded a bit: http://unit-tests.trac.wordpress.org/browser/trunk/tests/xmlrpc/wp/editTerm.php. A similar test does not exist yet for wp/newTerm.
#3
@
12 years ago
- Type changed from enhancement to defect (bug)
I think it is safe to call this a bug.
#4
@
12 years ago
Changed the unit tests and added extra ones to wp.editTerm and wp.newTerm. Also updated the patch of Sam to have it from the root instead of the wp-includes folder.
#5
@
12 years ago
- Keywords dev-feedback punt added
Does this patch allow for a term with a parent to be set to then have no parent?
#6
@
12 years ago
I'm not sure about this.
By definition the datatype that should be passed here is a string containing an integer, this is the return value of get_term
and the new/edit functions should expect the same.
So ideally the correct value for parent is probably and empty string or '0' and all the tests should be updated to send numbers as strings.
I'm not sure [UT1118] adds completely correct tests.
#9
@
11 years ago
- Keywords needs-testing added
I have added modified patch solution which allows to reset the term parent to 0 (i.e no-parent), and also handles properly the null and empty values for parent.
https://core.trac.wordpress.org/attachment/ticket/21977/ticket.21977.2ndopnion.diff
#10
@
9 years ago
- Keywords needs-patch needs-refresh added; has-patch dev-feedback 2nd-opinion removed
I don't think this is major — the workaround is to simply not pass 'parent'.
But yes, switching from isset() to ! empty() makes sense.