Introducing menu_page_url()
June 10, 2010 15 Comments
We’ve just added a new api into WordPress 3.0 to make plugin writing that bit easier – #13829
It is now really easy to get the url for a plugin page that you have registered to make it easy to link between different plugin pages. You use the new function like this:
add_options_page('Best Evar Menu', 'Best Evar Menu', 'manage_options', 'best_evar_menu', 'best_evar_options_page');
menu_page_url( 'best_evar_menu' );
The function will by default echo the url out but if you want you can get it returned for processing by setting the second argument to false.
Advertisement
Like this:
4 bloggers like this post.
About Peter Westwood
Pingback: Just added menu_page_url() – http://west… « WordPress Development Updates
There is a “for” missing between “returned” and “processing” in the last paragraph.
Cheers!
Noted and fixed. Thanks!
Awesome!
Nice.
Excellent! that will actually come in handy, I think…
Cool!
Now we don’t need anymore to know which kind of page it is, must the mage tag
Will this work for any page, including themes pages?
Shouldn’t this be admin_menu_url() rather? menu_page_url() sounds like we’re implementing an API for newly menu items.
Not really.
All the front end menu functions refer to themselves as
*nav_menu*All the back end menu functions for the admin menus refer to themselves
add_*_pageIs there a counter-part function that will return the $hookname for the URL? That would make it perfect!
What would the use case for this be?
If you want the hookname for the current page it is already there as a global I believe
Thanks Peter. I used it tonight. Very handy
Just tried to use this in my plugin and I didn’t get it to work.
My code looks like this:
add_pages_page( CMS_TPV_NAME, CMS_TPV_NAME, “edit_pages”, “cms-tpv-pages-page”, “cms_tpv_pages_page” );
echo menu_page_url(“cms-tpv-pages-page”);
// echoes “http://localhost/wordpress3/wp-admin/edit.php?post_type=page?page=cms-tpv-pages-page”
See that is outputs a questionmark instead of an ampersand. Don’t know if I did anything wrong here..
That looks like a bug in the implementation – please raise a ticket in trac with details
Should now be fixed – http://core.trac.wordpress.org/changeset/15268