The data for Currently Active Menus is not included in the exports (by default). This is because there is no guarantee the importing site will have the same theme (or same named menus). If changing the menus was a big deal, you could export/import all the data straight out of the database. (This option is … Read more
Use ancestors: $ancestors = array_reverse( get_post_ancestors( $post->ID ) ); // reverse ancestors to make it more intuitive if ( isset( $ancestors[0] ) ) { if ( isset( $ancestors[1] ) ) { // 3rd tier $parent_id = $post->post_parent; } else { // 2nd tier $parent_id = $post->ID; } $args = array( ‘depth’ => 1, ‘child_of’ => … Read more
Menu items are a post type, and the menus to which they belong are taxonomy terms. So to create a post type in order to get a metabox from which you can add menu items seems a bit redundant (effectively duplicating every ‘special item’ in the database). In any case, setting the post type’s visibilty … Read more
the simplest way would be to create two menus on for admin and one for everyone else and display them based on that: if (current_user_can(‘add_users’)){ wp_nav_menu( array(‘menu’ => ‘My Admin Menu’ )); }else{ wp_nav_menu( array(‘menu’ => ‘My Users Menu’ )); }
Did you try with: get_adjacent_post ? get_adjacent_post(false, ‘YourID’, false); wp topic: get_adjacent_posts-exclude-category-syntax
You mention a custom post type, are you also using a custom taxonomy? If so you need to specify this taxonomy in your function call: the_post_navigation(array( ‘prev_text’=>__(‘previous project: %title’), ‘next_text’=>__(‘next project: %title’), ‘in_same_term’ => true, ‘taxonomy’ => ‘wpse240053_custom_taxonomy_name’, )); By default the built-in category taxonomy for Posts is used. This requires WP4.4 or later.
Let’s take a look at wp_get_nav_menu_items code reference. It takes two parameters: $menu – (int|string|WP_Term) (Required) Menu ID, slug, name, or object, $args – (array) (Optional) Arguments to pass to get_posts(). So we can use get_posts args in here… And if we want to get only top-level posts, then post_parent arg comes useful… So something … 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
The filter you need is nav_menu_css_classes. You should be able to test for *in_category* on single post and archive pages, and add the appropriate class there.
One of my favorite ways to do this is to use the Factious plugin. It is still fairly basic and only has a Sidebar widget by default. However, it has an extenable API(ish thing) that lets you write code to place it elsewhere. The reasons why I like it are this: Written by people who … Read more