Bop Search Box Item Type For Nav Menus

A: The customizer is still in active development, especially for menus, at the time of writing this and any odd behaviour is likely because of that. Nonetheless, if you do experience any issues, let me know on the support forum. I still recommend using Appearance > Menus

A: This is a known issue with the customizer (at the time of writing). Ignore it, they still work just fine.

A: It is not this plugin but WordPress itself that is causing this issue. When using more than one WordPress HTML4 search form, there is a conflict as id attributes are repeated in the same document (not allowed in HTML). The only solutions to this are to only use one search form per page, or add support for HTML5 search forms to your theme. I advise the latter, see here to find out how this is done. Alternatively, A: There is an issue with your theme's nav walker class. Probably worth getting another theme/if it's yours, fixing it.

A: This is set via the Attribute Title field in the menu item editor in the admin area. However, if your theme doesn't support html5 search forms, this won't work. See here for a support post on how to enable HTML5 support. Note that there are a few id and class changes when going to HTML5 and that if your theme's css/js uses the old ones, you made need to make a few small fixes.

A: This has been rectified, but depending on when you downloaded v1.4.0, it may be incorrect on your system. See this support question for more info and a fix: https://wordpress.org/support/topic/please-dont-modify-prev-used-classes-in-the-plugin-it-breaks-developed-theme

A: There are a number of filters available for the output of the search box and they are written about below. The most comprehensive method is to use the filter hook get_nav_search_box_form and return the html you want to see. For example: add_filter( 'get_nav_search_box_form', function( $current_form, $item, $depth, $args ){ $new_form = '...my_html...'; return $new_form; }, 10, 4 ); Keep in mind that this is being accessed as part of a walk and that $item, $depth and $args are the same as in Walker_Nav_Menu::start_el(). Try to use some of the features demonstrated in the code there.

A: The filter hook bop_nav_search_show_submit_button will do the job of removing. Use: add_filter( 'bop_nav_search_show_submit_button', function( $bool, $item, $depth, $args ){ $bool = false; return $bool; }, 10, 4 ); in your theme's functions.php file - or other similarly suitable php file. If you wish to strictly hide the button (i.e. keep outputting html but have it invisible), use .bop-nav-search input[type="submit"]{ display: none; } in your theme's style.css - or other similarly suitable css file. Note that bop-nav-search is the default class applied list item, so if it's changed, the style rule will need changing accordingly.

A: The filter hook bop_nav_search_screen_reader_text will do the job of removing or changing the text. Use: add_filter( 'bop_nav_search_screen_reader_text', function( $text, $item, $depth, $args ){ $text = ''; //for nothing $text = __( '<span class="screen-reader-text">The text you want</span>', 'myslug' ); //to change - the __() is for theme translation return $text; }, 10, 4 ); in your theme's functions.php file - or other similarly suitable php file. The output should be hidden in a well written theme as it has screen-reader-text class. However, if this is not the case, you may well wish to add .bop-nav-search .screen-reader-text { clip: rect(1px, 1px, 1px, 1px); height: 1px; overflow: hidden; position: absolute !important; width: 1px; } or simply, .screen-reader-text { clip: rect(1px, 1px, 1px, 1px); height: 1px; overflow: hidden; position: absolute !important; width: 1px; } in your theme's style.css - or other similarly suitable css file. Note that bop-nav-search is the default class applied list item, so if it's changed, the style rule will need changing accordingly. Also note that, as per WP defaults, the default output for this filter is different depending on whether your theme supports html5.

A: It is most likely that you have it turned off in the Screen Options tab on your Menus admin page.

A: It is most likely that you have it turned off in the Screen Options tab on your Menus admin page.

A: Your caching plugin is likely being naughty by misusing WP Object Cache. Many of these plugins allow you to turn this on or off; I recommend off. However, you are also likely using an older version of this (BSBITFNM) plugin and you should update. Versions 1.3.1 and above no longer use WP Object Cache and should fix the conflict.