#24802 closed defect (bug) (invalid)
Don't set slug explicitely to null in wp_update_nav_menu_object
| Reported by: | Chouby | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Menus | Version: | 3.0 |
| Severity: | normal | Keywords: | has-patch needs-unit-tests |
| Cc: | Focuses: |
Description
This new ticket is related to #23199, #21950, #5809 (shared terms)
If a user creates a new nav menu with the same name as an existing term in another taxonomy, the term is shared with this other taxonomy. This is known and probably not an issue here.
But when the menu is saved, calling update_term with the slug explicitely set to null does modify the (shared) term slug.
Attachments (1)
Change History (7)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Makes sense at a glance. Unit tests would help make this happen.