Opened 3 years ago
Closed 3 years ago
#14875 closed defect (bug) (worksforme)
Apperance Menu Not Showing Up
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Administration | Version: | 3.0.1 |
| Severity: | normal | Keywords: | |
| Cc: | tim@… |
Description
Site admins can see the full Appearance menu (widgets, theme options, editor, etc.).
Regular admins can not. They are cut off from everything.
The themes I use are designed around regular admins being able to manage widgets.
Attachments (1)
Change History (9)
- Keywords reporter-feedback added
- Severity changed from critical to normal
Hi Nacin,
Thanks for the response.
I'm not using custom panels, nor am I using custom role definitions. I'm using the built-in "super admin" and "administrator" roles.
If a user is a "super admin," they can see all of the submenus under "Appearance" (like Widgets, Theme Options, etc.).
If a user has the role "administrator" on a MultiSite blog, but not the "super admin" role, they can see an Appearance menu, but it has no submenus at all.
I've disabled/removed all plugins in use, tried installing a custom role manager to add the role "edit_theme_options," but nothing helps.
I just recently upgraded from WPMU 2.9.2. in 2.9.2, everything worked fine.
Tim
Nacin,
More info. I created a plugin that added "edit_theme_options" to the administrator role. This fixes the issue.
However, I'm not seeing why the administrator role doesn't have this by default in 3.0 MultiSite.
Thanks,
Tim
- Resolution set to fixed
- Status changed from new to closed
Closing this as I believe it's only a bug when upgrading from WPMU to WP. The plugin I attached fixes the issue.
- Resolution fixed deleted
- Status changed from closed to reopened
Sounds like the upgrade script didn't assign the new capability. This is generally the result of custom upgrades, or custom roles.

Two potential issues here.
For custom panels, you may be using edit_themes. This is the incorrect cap, because that applies to file modifications, which are blocked by default on multisite at the capability level. The correct cap, prior to 3.0, would be switch_themes. As of 3.0, that cap would be edit_theme_options.
That takes me to the second issue, for core panels. These now use edit_theme_options. If you are using custom role definitions or bypassing the database with $wp_user_roles, then you need to add edit_theme_options to those roles.