Make WordPress Core

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's profile sam2kb Owned by: wonderboymusic's profile wonderboymusic
Milestone: 4.4 Priority: normal
Severity: normal Version:
Component: XML-RPC Keywords: has-patch
Focuses: Cc:


We must allow 0, NULL and empty string values for 'parent' in wp_newTerm and wp_editTerm

Attachments (4)

p (1.1 KB) - added by sam2kb 12 years ago.
21977.diff (926 bytes) - added by markoheijnen 12 years ago.
Patch from root instead of wp-includes folder
unittest.21977.diff (2.8 KB) - added by markoheijnen 12 years ago.
Changed unit tests for this patch
ticket.21977.2ndopnion.diff (1.3 KB) - added by hrishiv90 10 years ago.
Modified patch for the parent reset of term via xmlrpc

Download all attachments as: .zip

Change History (16)

12 years ago

  • Attachment p added

#1 @nacin
12 years ago

  • Milestone changed from Awaiting Review to 3.5
  • Severity changed from major to normal

I don't think this is major — the workaround is to simply not pass 'parent'.

But yes, switching from isset() to ! empty() makes sense.

#2 @nacin
12 years ago

Looks like test_parent_empty() will need to change, and probably be expanded a bit: A similar test does not exist yet for wp/newTerm.

#3 @nacin
12 years ago

  • Type changed from enhancement to defect (bug)

I think it is safe to call this a bug.

12 years ago

Patch from root instead of wp-includes folder

12 years ago

Changed unit tests for this patch

#4 @markoheijnen
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 @nacin
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 @westi
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.

#7 @nacin
12 years ago

  • Keywords punt removed
  • Milestone changed from 3.5 to Future Release

#8 @nacin
12 years ago

  • Keywords 2nd-opinion added

10 years ago

Modified patch for the parent reset of term via xmlrpc

#9 @hrishiv90
10 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.

#10 @chriscct7
9 years ago

  • Keywords needs-patch needs-refresh added; has-patch dev-feedback 2nd-opinion removed

#11 @wonderboymusic
9 years ago

  • Keywords has-patch added; needs-testing needs-patch needs-refresh removed
  • Milestone changed from Future Release to 4.4
  • Owner set to wonderboymusic
  • Status changed from new to assigned

#12 @wonderboymusic
9 years ago

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

In 34580:

XML-RPC: in wp_xmlrpc_server::wp_editTerm(), check ! empty when applying parent logic.

Adds unit tests.

Props hrishiv90, markoheijnen, sam2kb.
Fixes #21977.

Note: See TracTickets for help on using tickets.