Currently, it is up to any plugin’s author as to where to put a link to the plugin’s option page. I have seen at least the following “solutions”:
- Plugin list
- Dashboard menu
- Plugins menu
- Appearance menu
- Tools menu
- Settings menu
- Tools menu
- Top level
In my opinion, this is very bad style (globally, not necessarily individually). In addition to the mass of links in many different locations, WordPress does not sort them or anything.
As it is now, plugin developers can put anything anywhere in the menues and we probably want it that way; but there really should be a unified way of registering an options page such that is recognised and placed as such. Please see here, too. The old ways could remain valid, but I’d suggest recommending to use the standardised (and easy) way.
I have lately thought about writing a plugin that provides such an frontend, that is offers a function for other plugin authors that registers an options page and cares for placing links to it in the appropriate places. The notion of appropriateness could be hardcoded in a first version and be left to the user in subsequent iterations. I can even image a screen were users can put pages registered by plugins (not necessarily only option pages) were it suits them; if the user thinks this plugin’s options should be there, so be it.
What do you think? In particular:
- As a plugin author, would you delegate to such a plugin?
- Do you think I should build it?
- Should I rather implement the feature directly into WordPress, hoping that the main hackers approve and incorporate it?
2 Answers
There will never be such thing as a restriction of where a plugin can place a link that will display a certain page the plugin is registering.
It’s just in your scenario that a plugin is registering a settings page and the link normally is named settings as well.
As there is no convention or suggestion what plugin authors can/should do, I see it even more probelmatic to restrict this. I doubt that a restriction would be technically effective and on the social side, it will only create problems for those who want/need to circumvent some more restricted approach.
This has various reasons and you are totally right, this can be a problem because it’s not easy to locate all the plugins settings.
For the plugins I code that actually have a settings page, I prefer them to add in the plugin listing – at least as well. I know that some users look there if they don’t locate stuff within the menu.
So it would be nice if core provides an additional routine plugin authors could call to register their settings page. For plugins that don’t do that, the plugin listing could display a greyed out – no settings – or else remark.
Because I know that not all plugin authors do announce their settings page at least in the plugins listing, I’ve create a quicksearch plugin for the admin that let’s you browse the menu quickly: Admin Quicksearch (WordPress Plugin) – It let’s you search the plugin listing quickly as well.
