![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
#4603 closed enhancement (worksforme)
wp.newCategory should prevent adding multiple categories of the same name/slug/parent
| Reported by: | redsweater | Owned by: | josephscott |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | XML-RPC | Version: | 2.2.1 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
This bug is related to http://trac.wordpress.org/ticket/3683 but is intended specifically as a behavior request for wp.newCategory in the XMLRPC-WP interface.
Currently wp.newCategory will happily assign new category IDs for the same term with the same slug at the same hierarchical level. This seems highly unlikely to be in the spirit of what any client is requesting, so to protect the category structure, I propose the following change:
IF the requested category name, slug, and parent ID all match an existing category in the targeted blog, return the existing category ID as if it had just been created.
This would have the happy coincidence of covering a race condition problem that might exist if two users were authorized to edit the same blog, and both submitted changes that caused an identical "newCategory" call to be made at the same time.
Change History (9)
#4
@
17 years ago
- Resolution duplicate
- Status closed → reopened
I think it's dangerous to close bugs as "duplicate" without referencing a specific example of what it is being considered a duplicate of. It's too easy to misunderstand the nuances of the actual bug report. Citing an original gives the original reporter a chance to clearly evaluate whether the original bug is in fact a duplicate, or merely a related issue.
If you don't mind finding at least one example for which this is a duplicate, that will probably also be useful to make a note of so that you can have it handy when you inevitably run into the other bugs which you also consider duplicates.
I've lost count of the number of dups of this one. Look into the Taxonomy component to find a few more of the same issue.