You are definitely on the right track, but wp_nav_menu will output a menu with a lot of containers and classnames; to keep it semantic in the terms of Semantic UI, you’ll be in good hands if you build the structure yourself. Get the name of the registered menu in the menu manager. Check register_nav_menu in … Read more
I know this is an old thread but the problem still exists. I think this is a bug. Default queries such as nav should not be affected in making custom search page. Anyways, this is how I fixed it: function fix_nav_menu_in_search($query) { if (is_search()) { $query->set(‘post_type’, [‘your_cpt’, ‘nav_menu_item’]); } return $query; } add_filter(‘pre_get_posts’, ‘fix_nav_menu_in_search’);
Here’s my solution : First, make all of your pages you want to move to be a subitem of some other item(the best way is creating one for this action bacuse you will delete parent item). Remeber that when you move your items you must move it with parent item like above. Then put items … Read more
Since there is no filter to remove this option, your best best to to stick to using CSS by putting the following in your child theme’s functions.php: add_action( ‘admin_head’, ‘wpse_225635_menu_css’ ); function wpse_225635_menu_css() { global $pagenow; if ( $pagenow == ‘nav-menus.php’ ) { ?> <style type=”text/css”> .auto-add-pages { display: none; } </style> <?php } }
Guessing the only way you get it without loop through the menu, is getting the post meta directly. Navigation menus are saved as custom post type into wp_posts, so you can get it with get_posts or get_post_meta. If it’s a custom link menu item, the code below should do it. Where $menu_id is you menu … Read more
If you created the theme yourself, you should take a look at the WordPress Codex. They have a section called Navigation Menus. It contains all information you need about registering your menus the right way, so they are customizable. To Keep things short: Add this code to your theme’s functions.php to register your menu: function … Read more
Thanks Dharmishtha, but I found the answer in below stack which worked really well without throwing any debug errors: How to remove menus section from WordPress theme customizer The correct way to disable ‘Menus’ and ‘Widgets’ (in Customizer) lies in creating a plugin with below code (taken from the above mentioned post to make it … Read more
OK, it took me a little while to debug this behaviour, but… Everything is clear for me right now… I’m not sure if this is fully intentional… Why is it so? So… The line breaks are stored in DB correctly. Then in wp_setup_nav_menu_item the description field is filled based on post_content column of given menu … Read more
You have to edit the files in: wordpress/wp-content/themes/twentyseventeen/template-parts/navigation/navigation-top.php and then create a custom walker, try to take a look here. Try in this way: <?php /** * Displays top navigation * * @package WordPress * @subpackage Twenty_Seventeen * @since 1.0 * @version 1.2 */ ?> <div class=”container”> <nav class=”navbar navbar-expand-lg navbar-light” id=”mainNav”> <a class=”navbar-brand js-scroll-trigger” … Read more
I just figured out my own issue which I am hoping might help others if they get stuck in this situation. Essentially the problem seemed to be that modsecurity caused the 500 Internal Server error because for some reason (which I have yet to understand) the menu page was sending a bunch of data in … Read more