It seems that menu items have to be added in a particular order: generic menu pages before options pages; and options pages before management pages. Is this the case? If so, what is the required order? (I will try to discern this for myself, and will report back, but I thought someone else might know.) — Sam Wilson 08:27, 10 Nov 2007 (UTC)
Except if you are creating your own top-level menu, or adding more than one sub-menu to an existing top-level menu, I believe that the submenus go in the order you want them to appear.
jhodgdon 01:35, 20 Nov 2007 (UTC)
The code posted for Top Level Menus does not work (or perhaps outdated). When I tried it for my plugin it did not work, and I finally worked it out (refer to this Post for more information about the problem.)
The top level submenu needed a unique identifier which references the file displaying the page (in my case was __FILE__). I'm not sure how to do it with external files however.
Please confirm, and edit the page if necessary.
Cheers
Dazzer 10:16, 3 January 2008 (UTC)
The information about using add_action(...) seems hidden to me. Took me a while to spot it. I think it should perhaps be more clearly explained and more prominently displayed.
In the sample at the top we use 'manage_options' as the $capability argument. Would 'edit_theme_options' be more appropriate/typical ? FrancescoRizzi 15:07, 13 February 2011 (UTC)
Shouldn't people use the Settings API for creating settings pages? I added a note to Adding_Administration_Menus#Sample_Menu_Page indicating that the reader should look into the Settings API, but it would be helpful if someone could explain the difference between the example code and using the settings API.