WordPress.org

Make WordPress Core

Opened 2 years ago

Last modified 3 months ago

#19288 new defect (bug)

Erroneous custom taxonomy screen menu behaviour

Reported by: johnbillion Owned by:
Milestone: Awaiting Review Priority: normal
Severity: trivial Version: 3.0
Component: Taxonomy Keywords: needs-patch
Focuses: Cc:

Description

I don't think this could get any more edge case and it's of trivial severity, but I thought I'd report it for completeness' sake.

If a user has the ability to manage terms on a post type, but not the ability to edit posts of that post type, and the post type has more than one taxonomy, then the post type menu doesn't expand as expected when viewing one of the term management screens for that post type.

Steps to reproduce:

  • Register a custom post type that uses its own capability mapping (resulting in edit_foos etc).
  • Register at least two custom taxonomies for this post type, with or without its own capability mapping.
  • Give a user (or role) the ability to manage the taxonomy terms but not the ability to edit posts of the post type.

When viewing one of the term management screens for the given post type, the menu doesn't expand as expected (although the new 3.3 fly-outs do show).

Change History (2)

comment:1 nacin2 years ago

  • Version changed from 3.3 to 3.0

Assuming this can be reproduced in 3.0. Moving out of the reports-against-3.3 list.

comment:2 nacin3 months ago

  • Component changed from General to Taxonomy
Note: See TracTickets for help on using tickets.