Make WordPress Core

Opened 13 years ago

Closed 11 years ago

Last modified 11 years ago

#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)

24802.patch (611 bytes ) - added by Chouby 13 years ago.

Download all attachments as: .zip

Change History (7)

@Chouby
13 years ago

#1 @Chouby
13 years ago

  • Keywords has-patch added

#2 @nacin
13 years ago

  • Keywords needs-unit-tests added

Makes sense at a glance. Unit tests would help make this happen.

#3 @nacin
13 years ago

  • Version trunk3.0

#4 @Chouby
12 years ago

Obviously, this ticket should have been fixed by the resolution of #5809. I propose to close it.

#5 @Chouby
11 years ago

  • Resolutioninvalid
  • Status newclosed

#6 @netweb
11 years ago

  • Milestone Awaiting Review
Note: See TracTickets for help on using tickets.