Make WordPress Core

Opened 12 years ago

Closed 12 years ago

#11577 closed feature request (invalid)

New Menu for active plugins

Reported by: metacortex Owned by:
Milestone: Priority: low
Severity: minor Version: 2.9
Component: Administration Keywords:
Focuses: Cc:


Hi. There are a couple of proposals about admin menu items.

Idea 1

Would be nice to enable a new menu item which stores plugins. I'm sure that more than one developer will prefer and respect this space (specially for usability reasons) for point their plugin link, and over time the user will get used to this feature.

Actually major part of plugins use the Settings menu to appear, causing a shuffle between plugins and core settings. I'm not suggesting to limite the option to plugins developers, but offer a new way to place the links, while the Settings menu has been cleaned.

idea 2

To give a possibility to the backend admins to move their menu items as they wish, and also to create new menu wrappers.

Change History (3)

#1 @janeforshort
12 years ago

  • Milestone set to Future Release
  • Type changed from enhancement to feature request
  • Version set to 2.9

Hi Metacortex. In general, it's better to post ideas first in the <a href="http://wordpress.org/extend/ideas/">Ideas forum</a>, to the wp-hackers list, or at http://wpdevel.wordpress.com for general discussion, as Trac is meant for active development tasks (where discussion ideally centers on how to code something). That said, I'm a little confused by your suggestion. "A new menu item which stores plugins" seems like it would be redundant, given that there is already a top-level nav item called Plugins.

Re some using Settings and some using Plugins with a configuration screen, that varies by plugin because they all do different things. It would be nice to see them a bit more standardized as to which gets a Settings screen vs a settings screen in a top-level category vs a configuration screen, but I don't think we need more menu items to accomplish that, I think we just need to all agree to some standard practices around configuration and settings screens.

#2 @scribu
12 years ago

  • Milestone Future Release deleted

Closing as per what Jane said: the problem mentioned in the ticket requires discussion first. Open a new ticket when an agreement has been reached.

#3 @scribu
12 years ago

  • Resolution set to invalid
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.