ClassicPress PetitionsClassicPress Petitions
This is a read-only archive. Post or comment on the live version of this page on our forums.

Pages before Posts and change of admin menu

October 2, 2018 · 09:53 · Pieter Bos

Since ClassicPress has set itself in the market as the business-focused CMS, I think that the Admin Sidebar menu can receive a much needed overhaul.

For starters Pages should be placed higher up in the Dashboard than Posts.

Ideally the order would become:

  • Dashboard
  • Pages
  • CPTs
  • Posts (with Comments being a submenu - see here)
  • Media
  • Appearance
  • Plugins
  • Users
  • Tools
  • Settings
  • and ideally all Settings of Plugins come below here, so the Dashboard can no longer be hijacked anymore).
+46 more
Difficulty: Moderate
Request: Modify feature
Fabian Wolf

at best, there might be a real reduction of all that clutter, although I dont know yet how to achieve this. Each CPT is usually adding another entry in the menu, and at some point, one has to scroll a lot ..

Ray Gulick

I like Pieter's organization. I'd like CP to consider replacing the side menu with a horizontal menu fixed to the top, similar to W2O Admin Dropdown Menu ( It can get pretty cluttered too (any menu with more than 10-12 items will be), but at least it's always in view and leaves more of the screen width for what you're working on.

Karissa Skirmont

OMG yes to all! It's so frustrating to have Plugins willy nilly go everywhere in any order. You have to play hide and go seek to find where the setting tab is!


I like this idea. I like the suggestion of CPTs in the menu, hoping that the follow through would be all CPTs are sub menu items to that. A lot of themes add CPTs all over the place in WordPress. It would be nice to have them contained if possible. Don't know if it is though.

Pieter Bos

Not sure if all CPTs should be gathered as items under 1 menu. We usually build a bespoke theme for our clients and most of them come with at least one, sometimes more CPTs. These all have a function on the site and a place in the backend and I would not want to have to explain to clients that they can find the logic in a submenu :)

Regarding moving the Setting menus of plugins to the bottom, I have implemented that already in a plugin I developed a while ago. This works excellent for a plugin like Jetpack and Gravity Forms has its own function to move its position. See and

Ray Gulick

CPTs can be major content types, and deserve a top-level position, IMO.

Code Potent

I'm not for any of this. Any plugin can inject itself wherever it wants to be placed; this is a blessing and a curse, but it works. If a CPT needs a top-level menu, the author should take 37 seconds and write a function that generates the entry.

Fredrik Forsmo

Not saying that this is the best solution but maybe move content cpts to a content menu like this

Pieter Bos

That is a great idea Frederik!

Glenn Dixon

I would also like to see the option to hide items (from yourself, or from other users) be baked in. Something simple, checkboxes, etc., for pieces you don't use. Mainly helpful when things get cluttered...

Daniel Klose

I'm also not a fan of plugins Hijacking Main Menus, but I also don't believe there is a real solution to the problem. I think the only way to improve the current situation would be to offer the option to easily reorganize the Menu Items. Plugins like Try to do that but, you quickly run into Plugins/Menu Items that fail to get reassigned, so to be honest I'm not sure if it can be done at all.

Pieter Bos

@Daniel Klose - it actually is quite easy to move all plugins to the bottom :) Have a look here to see how it's done:

Daniel Klose

@pieter, but in this specific example there seems to be a call especially for gravity forms. Does this mean gravity forms for example would not adhere to a general custom_menu_order filter call? If so, with 50k plugins out there I doubt this is a feasible approach to the problem as there are surely more than a handful that do similar things?

Mike Schinkel

@pieter - I expect many of the petitions for ClassicPress are about establishing a default different than WordPress and/or a standard that does not exist in WordPress. Given that, I expect many of the things petitioned here are easy to do with hooks, but doing them with hooks does not make them default nor a standard approach. #jmtcw #fwiw

Pieter Bos

@Daniel - yes that is true , GF is an exception which potentially could be one of many. The first rule though moves what I believe is the majority to the bottom, including plugins like Jetpack, which usually places itself at the very top right under "Dashboard".

@Mike - I am not aware that I have made such claim

Ray Gulick

I'd like to see this suggestion (reorganizing items on the admin menu), along with a lot of other admin UI suggestions made via petition, be part of a more comprehensive admin redesign effort (

Pieter Bos

I think that by the time v1 is out of the door and we start by seriously looking at petitions that have the required number of votes, we will also need to start combining things. There are numerous comments related petitions and as Ray points out, there are also a few already related to various things to do with the admin UI.

James Nylen

Is this something that could be addressed as a plugin first? I would strongly recommend starting that way if possible, that way we can iterate there and recommend the plugin for testing.

If you'd like to put something up on GitHub under the ClassicPress name, let me know and I'll create a repository for it. ClassicPress/organize-admin-menus is one idea for the name.

Peter B

Upvoted. Maybe even call Posts as "Blog posts" and find a new name for CPTs without the word post in that new name.

Laurence Bahiirwa