Opened 13 years ago
Closed 10 years ago
#16550 closed enhancement (fixed)
wp_set_post_categories should take an integer
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.7 | Priority: | normal |
Severity: | normal | Version: | 3.0 |
Component: | Taxonomy | Keywords: | has-patch |
Focuses: | Cc: |
Description
wp_set_post_categories();
can only be passed an array of cat ids. If you pass it an integer, it resets the value to the default category even though the category exists.
This happens as the if statement runs an OR check to see if the second parameter is not an array or empty. If one is true, it just goes on ahead and resets the parameter to be the default category regardless if the value was empty or a string.
Patch fixes this by strict typing the second parameter to an array. It also strict types the default category id as it was being returned as a string.
Attachments (4)
Change History (10)
#4
@
13 years ago
- Milestone changed from Awaiting Review to Future Release
- Summary changed from wp_set_post_categories is defected to wp_set_post_categories should take an integer
- Type changed from defect (bug) to enhancement
- Version changed from 3.1 to 3.0
Re-classifying this ticket. It's not a defect -- wp_set_post_categories() explicitly takes an array, so array( 3 )
rather than 3
.
Other functions such as wp_set_object_terms() seem to not mind taking a scalar argument. So this looks like a fine enhancement.
Please provide a patch relative to trunk.