[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fudCbXfIW6hnOGb50yVXM5kh_xma-PnXPHFn4NVJeuWM":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"wizzud","https:\u002F\u002Fprofiles.wordpress.org\u002Fwizzud\u002F",3,3280,85,30,84,"2026-04-05T06:16:40.985Z",[13,38,55],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":19,"downloaded":20,"rating":21,"num_ratings":22,"last_updated":23,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":27,"homepage":33,"download_link":34,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"custom-menu-wizard","Custom Menu Wizard Widget","3.3.1","\u003Cp>This plugin is a boosted version of the WordPress “Custom Menu” widget.\u003Cbr \u002F>\nIt provides full control over most of the parameters available when calling WP’s \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Freference\u002Ffunctions\u002Fwp_nav_menu\u002F\" rel=\"nofollow ugc\">wp_nav_menu()\u003C\u002Fa> function, as well as providing pre-filtering of the menu items in order to be able to select a specific portion of the custom menu. It also automatically adds a couple of custom classes. And there’s a shortcode that enables you to include the widget’s output in your content.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important!\u003C\u002Fstrong> This plugin provides \u003Cstrong>\u003Cem>nothing\u003C\u002Fem>\u003C\u002Fstrong> – \u003Cem>zip, zilch, nada, bupkis\u003C\u002Fem> – in the way of frontend styling! The\u003Cbr \u002F>\nappearance of any final output is down to you and your theme, so if you’re just looking for something to re-style\u003Cbr \u002F>\na menu then I’m sorry but this plugin \u003Cem>won’t do that\u003C\u002Fem>!\u003C\u002Fp>\n\u003Cp>Features include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Display an entire menu, just a branch of it, just certain level(s) of it, or even just specific items from it!\u003C\u002Fli>\n\u003Cli>Select a branch based on a specific menu item, or the current menu item (currently displayed page)\u003C\u002Fli>\n\u003Cli>Specify a relative or absolute level to start at, and the number of levels to output\u003C\u002Fli>\n\u003Cli>Include ancestor item(s) in the output, with or without siblings\u003C\u002Fli>\n\u003Cli>Exclude certain menu items, or levels of items\u003C\u002Fli>\n\u003Cli>Make the output conditional upon the current menu item being found in different stages of the filter selection process\u003C\u002Fli>\n\u003Cli>Automatically add cmw-level-N and cmw-has-submenu classes to output menu items\u003C\u002Fli>\n\u003Cli>Allow the widget title to be entered but not output, or to be set from the current menu item or selected branch item\u003C\u002Fli>\n\u003Cli>Select hierarchical or flat output, both options still abiding by the specified number of levels to output\u003C\u002Fli>\n\u003Cli>Specify custom class(es) for the widget block, the menu container, and the menu itself\u003C\u002Fli>\n\u003Cli>Modify the link’s output with additional HTML around the link’s text and\u002For the link element itself\u003C\u002Fli>\n\u003Cli>Use Ordered Lists (OL) for the top and\u002For sub levels instead of Unordered Lists (UL)\u003C\u002Fli>\n\u003Cli>Shortcode, \u003Ccode>[cmwizard]\u003C\u002Fcode>, available to run the widget from within content\u003C\u002Fli>\n\u003Cli>Shortcode can reference a widget instance, making maintenance of multiple occurences of the same (or very similar) shortcode a lot easier\u003C\u002Fli>\n\u003Cli>Interactive “assist” to help with the widget settings and\u002For shortcode definition\u003C\u002Fli>\n\u003Cli>Utility to find posts containing this plugin’s shortcode\u003C\u002Fli>\n\u003Cli>Specify an alternative configuration to use under certain conditions (dual-scenario capability)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Current documentation for the \u003Cstrong>Widget Options\u003C\u002Fstrong> can be found\u003Cbr \u002F>\nunder \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcustom-menu-wizard\u002Fother_notes\u002F\" rel=\"ugc\">Other Notes\u003C\u002Fa>.\u003Cbr \u002F>\nThe associated \u003Cstrong>Shortcode Attributes\u003C\u002Fstrong> are documented\u003Cbr \u002F>\nunder \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcustom-menu-wizard\u002Finstallation\u002F\" rel=\"ugc\">Installation\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>You may find that the documentation here is truncated, so I have reproduced the readme.txt\u003Cbr \u002F>\n    as \u003Ca href=\"http:\u002F\u002Fwww.wizzud.com\u002Fcmw-doc.html\" rel=\"nofollow ugc\">cmw-doc.html\u003C\u002Fa>.\u003Cbr \u002F>\n    This file is also now included in the plugin download, and is linked to from the Custom Menu Wizard entry\u003Cbr \u002F>\n    on the admin Plugins page.\u003Cbr \u002F>\n    My apologies if this causes – or has caused – any confusion.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>\u003Cstrong>Please, do not be put off by the number of options available!\u003C\u002Fstrong> I suspect (and I admit that I’m guessing!) that for the majority of users\u003Cbr \u002F>\nthere are probably a couple of very common scenarios:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Show an entire menu…\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Drag a new Custom Menu Wizard widget into the sidebar, and give it a title (if you want one)\u003C\u002Fli>\n\u003Cli>Select the menu you wish to use (if it’s not already selected)\u003C\u002Fli>\n\u003Cli>Save the widget!\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cem>Equivalent shortcode resembles…\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>[cmwizard menu=N title=”Your Title”\u002F]\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Show the current menu item, plus any descendants…\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Drag a new Custom Menu Wizard widget into the sidebar, and give it a title (if you want one)\u003C\u002Fli>\n\u003Cli>Select the menu you wish to use (if it’s not already selected)\u003C\u002Fli>\n\u003Cli>Open the FILTERS section :\n\u003Cul>\n\u003Cli>under Primary Filter, click on the \u003Cem>Branch\u003C\u002Fem> radio\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Save the widget!\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cem>Equivalent shortcode resembles…\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>[cmwizard menu=N title=”Your Title” branch=current\u002F]\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Show just the descendants of the current menu item (if there are any)…\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Drag a new Custom Menu Wizard widget into the sidebar, and give it a title (if you want one)\u003C\u002Fli>\n\u003Cli>Select the menu you wish to use (if it’s not already selected)\u003C\u002Fli>\n\u003Cli>Open the FILTERS section :\n\u003Cul>\n\u003Cli>under Primary Filter, click on the \u003Cem>Branch\u003C\u002Fem> radio\u003C\u002Fli>\n\u003Cli>under Secondary Filter, set \u003Cem>Starting at\u003C\u002Fem> to “+1 (children)”\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Save the widget!\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cem>Equivalent shortcode resembles…\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>[cmwizard menu=N title=”Your Title” branch=current start_at=”+1″\u002F]\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Always show the top level items, but when the menu contains the current item then also show that current item, with its ancestors and immediate children…\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Drag a new Custom Menu Wizard widget into the sidebar, and give it a title (if you want one)\u003C\u002Fli>\n\u003Cli>Select the menu you wish to use (if it’s not already selected)\u003C\u002Fli>\n\u003Cli>Open the FILTERS section :\n\u003Cul>\n\u003Cli>under Primary Filter, click on the \u003Cem>Branch\u003C\u002Fem> radio\u003C\u002Fli>\n\u003Cli>under Secondary Filter, set \u003Cem>Depth\u003C\u002Fem> to “2 levels” (ie. current item plus immediate children)\u003C\u002Fli>\n\u003Cli>under Inclusions, set \u003Cem>Branch Ancestors\u003C\u002Fem> to “to level 1 (root)”, and set \u003Cem>Level\u003C\u002Fem> to “1”\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Open the ALTERNATIVE section :\n\u003Cul>\n\u003Cli>set \u003Cem>On condition\u003C\u002Fem> to “Current Item is NOT in…” and “Menu” (the 2nd dropdown)\u003C\u002Fli>\n\u003Cli>in the \u003Cem>Then switch settings to\u003C\u002Fem> textarea, type in “[cmwizard depth=1\u002F]” (without the quotes!)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Save the widget!\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cem>Equivalent shortcode resembles…\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>[cmwizard menu=N branch=current depth=2 ancestors=1 include_level=”1″ alternative=”no-current,menu”]depth=1[\u002Fcmwizard]\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If you like this widget (or if you don’t?), please consider taking a moment or two to give it a\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fview\u002Fplugin-reviews\u002Fcustom-menu-wizard\" rel=\"ugc\">Review\u003C\u002Fa> : it helps others, and gives me valuable feedback.\u003C\u002Fp>\n\u003Cp>\u003Cem>Documentation for version 2 of the widget\u003Cbr \u002F>\ncan be found \u003Ca href=\"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fcustom-menu-wizard\u002Ftags\u002F2.0.6\u002Freadme.txt\" rel=\"nofollow ugc\">here\u003C\u002Fa>\u003Cbr \u002F>\nor \u003Ca href=\"http:\u002F\u002Fwww.wizzud.com\u002Fv210-readme.html\" rel=\"nofollow ugc\">here\u003C\u002Fa>.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch3>WIDGET OPTIONS\u003C\u002Fh3>\n\u003Cp>There are quite a few options, which makes the widget settings box very long. I have therefore grouped most of the options into\u003Cbr \u002F>\ncollapsible logical sections (with remembered state once saved).\u003C\u002Fp>\n\u003Cp>The associated \u003Cstrong>SHORTCODE ATTRIBUTES\u003C\u002Fstrong> are documented\u003Cbr \u002F>\nunder \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcustom-menu-wizard\u002Finstallation\u002F\" rel=\"ugc\">Installation\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cem>\u003Cstrong>Always Visible\u003C\u002Fstrong>\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Title\u003C\u002Fstrong> \u003Cem>(textbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Set the title for your widget.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Hide\u003C\u002Fstrong> \u003Cem>(checkbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Prevents the entered \u003Ccode>Title\u003C\u002Fcode> being displayed in the front-end widget output.\u003C\u002Fp>\n\u003Cp>In the Widgets admin page, I find it useful to still be able to see the \u003Ccode>Title\u003C\u002Fcode> in the sidebar when the widget is closed, but I\u003Cbr \u002F>\ndon’t necessarily want that \u003Ccode>Title\u003C\u002Fcode> to actually be output when the widget is displayed at the front-end. Hence this checkbox.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Select Menu\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Choose the appropriate menu from the dropdown list of Custom Menus currently defined in your WordPress application. The\u003Cbr \u002F>\nfirst one available (alphabetically) is already selected for you by default.\u003C\u002Fp>\n\u003Ch3>Filters Section\u003C\u002Fh3>\n\u003Cp>Filters are applied in the order they are presented.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Cem>Primary Filter\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Level\u003C\u002Fstrong> \u003Cem>(radio, default On, & select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Filters by level within the selected menu, starting at the level selected here. This is the default setting\u003Cbr \u002F>\nfor a new widget instance, which, if left alone and with all other options at their default, will show the entire selected menu.\u003C\u002Fp>\n\u003Cp>Example : If you wanted to show all the options that were at level 3 or below, you could check this radio and set the select to “3”.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Branch\u003C\u002Fstrong> \u003Cem>(radio & select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Filters by branch, with the head item of the branch being selected from the dropdown. The dropdown presents all the\u003Cbr \u002F>\nitems from the selected menu, plus a “Current Item” option (the default). Selecting “Current Item” means that the head item of the\u003Cbr \u002F>\nbranch is the current menu item (as indicated by WordPress), provided, of course, that the current menu item actually corresponds to\u003Cbr \u002F>\na menu item from the currently selected menu!\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Items\u003C\u002Fstrong> \u003Cem>(radio & textbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Filters by the menu items that you specifically pick (by menu item id, as a comma-separated list). The simplest way\u003Cbr \u002F>\nto get your list of ids is to use the “assist”, and [un]check the green tick box at the right hand side of each depicted menu item that\u003Cbr \u002F>\nyou want. Alternatively, just type your list of ids into the box.\u003C\u002Fp>\n\u003Cp>If the id is appended with a ‘+’, eg. ’23+’, then all the item’s descendants will also be included.\u003C\u002Fp>\n\u003Cp>Example : If you only wanted to show, say, 5 of your many available menu items, and those 5 items are not in one handy branch of the menu,\u003Cbr \u002F>\nthen you might want to use this option.\u003C\u002Fp>\n\u003Cp>Example : If your menu has 6 root branches – “A” thru to “F” – and you were only interested in branches “B” (id of, say, 11) and\u003Cbr \u002F>\n“E” (id of, say, 19), you could set \u003Ccode>Items\u003C\u002Fcode> to be “11+,19+”, which would include “B” with all its descendants, and “E” with all its\u003Cbr \u002F>\ndescendants.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Cem>Secondary Filter\u003C\u002Fem>\u003C\u002Fstrong> \u003Cem>(not applicable to an \u003Ccode>Items\u003C\u002Fcode> filter)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Starting at\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This is only applicable to a \u003Ccode>Branch\u003C\u002Fcode> filter and it allows you to shift the starting point of your output within the confines\u003Cbr \u002F>\nof the selected branch. By default it is set to the selected branch item itself, but it can be changed to a relative of the branch item (eg.\u003Cbr \u002F>\nparent, grandparent, children, etc) or to an absolute, fixed level within the branch containing the selected branch item (eg. the root\u003Cbr \u002F>\nlevel item for the branch, or one level below the branch’s root item, etc).\u003C\u002Fp>\n\u003Cp>Example : If you wanted the entire “current” branch then, with \u003Ccode>Branch\u003C\u002Fcode> set to “Current Item”, you might set \u003Ccode>Starting at\u003C\u002Fcode> to “1 (root)”.\u003Cbr \u002F>\nAlternatively, if you wanted the children of the current menu item then \u003Ccode>Starting at\u003C\u002Fcode> could be set to “+1 (children)”.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Item, if possible\u003C\u002Fstrong> \u003Cem>(radio, default On)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This is the default filter mechanism whereby, if \u003Ccode>Starting at\u003C\u002Fcode> can only result in a single item (ie. it is the branch item itself, or\u003Cbr \u002F>\nan ancestor thereof) then only that item and its descendants are considered for filtering.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Level\u003C\u002Fstrong> \u003Cem>(radio)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Changes the default filter mechanism such that if \u003Ccode>Starting at\u003C\u002Fcode> results in the selection of the branch item or one of its ancestors,\u003Cbr \u002F>\nthen all siblings of that resultant item are also included in the secondary filtering process.\u003C\u002Fp>\n\u003Cp>Example : If Joe and Fred are siblings (ie. they have a common parent) and Joe is the selected branch item – with \u003Ccode>Starting at\u003C\u002Fcode> set\u003Cbr \u002F>\nto Joe – then the secondary filter would normally only consider Joe and its descendants. However, if \u003Ccode>Level\u003C\u002Fcode> was enabled instead of\u003Cbr \u002F>\n    Item, then both Joe and Fred, \u003Cem>and all their descendants\u003C\u002Fem>, would be considered for filtering.\u003C\u002Fp>\n\u003Cp>Note that there is one exception, and that is that if \u003Ccode>Starting at\u003C\u002Fcode> results in a root-level item, then \u003Ccode>Allow all Root Items\u003C\u002Fcode> must\u003Cbr \u002F>\nbe enabled in order to allow the other sibling root items to be added into the filter process.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Allow all Root Items\u003C\u002Fstrong> \u003Cem>(checkbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>In the right conditions – see \u003Ccode>Level\u003C\u002Fcode> above – this allows sibling root items to be considered for secondary filtering.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>For Depth\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This the number of levels of the menu structure that will be considered for inclusion in the final output (in complete\u003Cbr \u002F>\nignorance of any subsequent Inclusions or Exclusions).\u003C\u002Fp>\n\u003Cp>The first level of output is the starting level, regardless of\u003Cbr \u002F>\nhow that starting level is determined (see \u003Ccode>Starting at\u003C\u002Fcode> and \u003Ccode>Relative to Current Item\u003C\u002Fcode> options). So if you ask\u003Cbr \u002F>\nfor a Depth of 1 level, you get just the starting level; if you ask for a Depth of 2, you get the starting level and\u003Cbr \u002F>\nthe one below it.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Relative to Current Item\u003C\u002Fstrong> \u003Cem>(checkbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>By default, \u003Ccode>For Depth\u003C\u002Fcode> (above) is relative to the first item found, but this may be overridden to be relative to the\u003Cbr \u002F>\ncurrent menu item \u003Cstrong>\u003Cem>if\u003C\u002Fem>\u003C\u002Fstrong>  \u003Ccode>For Depth\u003C\u002Fcode> is not unlimited \u003Cstrong>and\u003C\u002Fstrong> the current menu item can found within the selected menu.\u003Cbr \u002F>\nIf the current menu item is not within the selected menu then it falls back to being relative to the first item found.\u003C\u002Fp>\n\u003Cp>Please note that the current item must also be within the constraints set by the \u003Ccode>Starting at\u003C\u002Fcode> option. In other words, if\u003Cbr \u002F>\ncurrent item is \u003Cem>above\u003C\u002Fem> the \u003Ccode>Starting at\u003C\u002Fcode> level in the menu structure then it will \u003Cstrong>not\u003C\u002Fstrong> be used to alter the determination of\u003Cbr \u002F>\nDepth.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Cem>Inclusions\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>These allow certain other items to be added to the output from the secondary filters.\u003C\u002Fp>\n\u003Cp>The first 3 are only applicable to a \u003Ccode>Branch\u003C\u002Fcode> filter. Please note that they only come into effect when the \u003Ccode>Branch\u003C\u002Fcode> filter item is at\u003Cbr \u002F>\nor below the \u003Ccode>Starting at\u003C\u002Fcode> level, and do not include any items that would break the depth limit set in the Secondary Filter options.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Branch Ancestors\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Include any ancestors (parent, grandparent, etc) of the items selected as the \u003Ccode>Branch\u003C\u002Fcode> filter.\u003Cbr \u002F>\nAncestors can be set to go up to an absolute level, or to go up a certain number of levels relative to the \u003Ccode>Branch\u003C\u002Fcode> filter item.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>… with Siblings\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>In conjunction with \u003Ccode>Branch Ancestors\u003C\u002Fcode>, also include all siblings of those ancestors.\u003Cbr \u002F>\nAs with Ancestors, their siblings can be set to go up to an absolute level, or to go up a certain number of levels relative\u003Cbr \u002F>\nto the \u003Ccode>Branch\u003C\u002Fcode> filter item. Note that while it is possibe to set a larger range for siblings than ancestors, the final output\u003Cbr \u002F>\nis limited by \u003Ccode>Branch Ancestors\u003C\u002Fcode> setting.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Branch Siblings\u003C\u002Fstrong> \u003Cem>(checkbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Include any siblings of the item selected as the \u003Ccode>Branch\u003C\u002Fcode> filter (ie. any items at the same level and within\u003Cbr \u002F>\nthe same branch as the \u003Ccode>Branch\u003C\u002Fcode> item).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Level\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This allows an entire level of items to be included, optionally also including all levels either above or below it.\u003Cbr \u002F>\nThis replaces the \u003Ccode>All Root Items\u003C\u002Fcode> checkbox (pre v3.0.4), which only allowed for the inclusion of the root level items.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Cem>Exclusions\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Item Ids\u003C\u002Fstrong> \u003Cem>(textbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This is a comma-separated list of the ids of menu items that you do \u003Cem>not\u003C\u002Fem> want to appear in the final output.\u003Cbr \u002F>\nThe simplest way to get your list of ids is to use the “assist”, and [un]check\u003Cbr \u002F>\nthe red cross box at the left hand side of each depicted menu item. Alternatively, just type your list of ids into the box.\u003C\u002Fp>\n\u003Cp>If the id is appended with a ‘+’, eg. ’23+’, then all the item’s descendants will also be excluded.\u003C\u002Fp>\n\u003Cp>Example : If you wanted to show the entire “A” branch, with the sole exception of one grandchild of “A”, say “ABC”, then you could\u003Cbr \u002F>\nset \u003Ccode>Branch\u003C\u002Fcode> to “A”, and \u003Ccode>Exclusions\u003C\u002Fcode> to the id of the “ABC” item.\u003C\u002Fp>\n\u003Cp>Example : If you have a menu with 4 root items – “A”, “B”, “C” & “D” – and you wanted to show all items, with descendants, for all bar\u003Cbr \u002F>\nthe “C” branch, then you could set \u003Ccode>Level\u003C\u002Fcode> to “1 (root)” and \u003Ccode>Exclusions\u003C\u002Fcode> to, say, “12+”, where “12” is the menu item id for “C” and\u003Cbr \u002F>\nthe “+” indicates that all the descendants of “C” should also be excluded.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Level\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This allows an entire level of items to be excluded, optionally also excluding all levels either above or below it.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Cem>Qualifier\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Current Item is in\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This allows you to specify that there only be any output shown when\u002Fif the current menu item is one of the menu items selected\u003Cbr \u002F>\nfor output at a particular stage in the filter processing.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>“Menu”\u003C\u002Fem> : the current menu item has to be somewhere within the selected menu.\u003C\u002Fli>\n\u003Cli>\u003Cem>“Primary Filter”\u003C\u002Fem> : the current menu item has to be within the scope of the selected primary filter. So if you selected, say, a child\u003Cbr \u002F>\nof “A” as the \u003Ccode>Branch\u003C\u002Fcode> item, then if “A” was the current menu item there would be no output with this qualifier.\u003C\u002Fli>\n\u003Cli>\u003Cem>“Secondary Filter”\u003C\u002Fem> : the current menu item has to be within the items as restricted by the secondary filters. So if you\u003Cbr \u002F>\nselected \u003Ccode>Branch\u003C\u002Fcode> as “A”, with \u003Ccode>Starting at\u003C\u002Fcode> set to “+1 (children)”, then if “A” was the current menu item there would be no output with this qualifier.\u003C\u002Fli>\n\u003Cli>\u003Cem>“Inclusions”\u003C\u002Fem> : the current menu item has to be in within the items as set by the primary and secondary filters, and the inclusions.\u003C\u002Fli>\n\u003Cli>\u003Cem>“Final Output”\u003C\u002Fem> : the current menu item has to be in the final output.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Fallbacks Section\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>\u003Cem>If Current Item has no children\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This gets applied at the Secondary Filter stage, and its eligibility and\u003Cbr \u002F>\napplication are therefore determined and governed by the other Secondary Filter settings.\u003C\u002Fp>\n\u003Cp>It only comes into play (possibly) when a \u003Ccode>Branch\u003C\u002Fcode> filter is set as “Current Item”, and the \u003Ccode>Starting at\u003C\u002Fcode>\u003Cbr \u002F>\nand \u003Ccode>For Depth\u003C\u002Fcode> settings are such that the output should start at or below the current item,\u003Cbr \u002F>\nand would normally include some of the current item’s descendants\u003Cbr \u002F>\n(eg. \u003Ccode>Starting at\u003C\u002Fcode> “the Branch”, \u003Ccode>For Depth\u003C\u002Fcode> “1 level” does \u003Cem>not\u003C\u002Fem> invoke the fallback).\u003Cbr \u002F>\nThe fallback allows for the occasion when the current menu item \u003Cem>does not have\u003C\u002Fem> any immediate children.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Unlabelled Select\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Enable the fallback by selecting one of\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>Start at : -1 (parent)\u003C\u002Fem> : overrides the \u003Ccode>Starting at\u003C\u002Fcode> option to be the immediate parent of the Current Item\u003C\u002Fli>\n\u003Cli>\u003Cem>Start at : the Current Item\u003C\u002Fem> : overrides the \u003Ccode>Starting at\u003C\u002Fcode> option to be the Current Item\u003C\u002Fli>\n\u003Cli>\u003Cem>No output!\u003C\u002Fem> : self-explanatory\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>…and Include its Siblings\u003C\u002Fstrong> \u003Cem>(checkbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This will add in the siblings of the item selected above (excluding the “No output!” setting!).\u003C\u002Fp>\n\u003Cp>Note : This \u003Cem>only\u003C\u002Fem> adds the siblings, not the siblings’ descendants! However, if the \u003Ccode>Level\u003C\u002Fcode> radio (in Secondary Filter stage above) is\u003Cbr \u002F>\nset, then all the item’s siblings \u003Cem>and their descendants\u003C\u002Fem> will automatically be included, and [un]setting this option will have no effect.\u003Cbr \u002F>\nAlso note that if the fallback results in a root-level item being selected as the new \u003Ccode>Starting at\u003C\u002Fcode> item, then the inclusion of siblings\u003Cbr \u002F>\noutside the current branch depends on the setting of the \u003Ccode>Allow all Root Items\u003C\u002Fcode> checkbox.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>For Depth\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Override the current \u003Ccode>For Depth\u003C\u002Fcode> setting. Note that any depth value set here will be relative to the current item, regardless\u003Cbr \u002F>\nof the current setting of \u003Ccode>...Relative to\u003C\u002Fcode>!\u003C\u002Fp>\n\u003Cp>As an example, this option may be useful in the following scenario : item A has 2 children, B and C; B is the current menu item but has\u003Cbr \u002F>\nno children, whereas C has loads of children\u002Fgrandchildren. If you fallback to B’s parent – A – with Unlimited depth set, then you will\u003Cbr \u002F>\nget A, B, C, and \u003Cem>all\u003C\u002Fem> C’s dependents! You may well want to override depth to limit the output to, say, just A, B and C, by setting this\u003Cbr \u002F>\nfallback option to “1”? Or maybe A, B, C, and C’s immediate children, by setting “2”?\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Cem>If no Current Item can be found\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Try items marked Parent of Current\u003C\u002Fstrong> \u003Cem>(checkbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This gets applied right at the start of processing, when determining\u003Cbr \u002F>\nwhich of the menu items (if any) should be regarded as the unique “Current Item” by this widget.\u003Cbr \u002F>\nUnder certain conditions, WordPress will mark an item as being the parent of a current item …\u003Cbr \u002F>\nbut there won’t actually be a current item marked! This occurs, for example, when displaying a full post for which there is\u003Cbr \u002F>\nno specific related menu item, yet there \u003Cem>is\u003C\u002Fem> a menu item for a Category that the displayed post belongs to :\u003Cbr \u002F>\nWordPress will then mark the related Category as being the parent of the current item (the post) even though\u003Cbr \u002F>\nit can’t mark the post as being the current item (because there’s no specific item for it within the menu).\u003C\u002Fp>\n\u003Cp>Enabling this fallback will make the widget look for these situations – only as a last resort! –\u003Cbr \u002F>\nand set (one of) the found “parent” item(s) as the Current Item.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Cem>If more than 1 possible Current Item\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Use the last one found\u003C\u002Fstrong> \u003Cem>(checkbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Occasionally it is possible for CMW to have more than one possible candidate for Current Item. Since there can only be one\u003Cbr \u002F>\nCurrent Item, CMW picks the \u003Cem>first one\u003C\u002Fem> encountered. However, this may cause a problem where, for example, a root level item \u003Cstrong>and\u003C\u002Fstrong>\u003Cbr \u002F>\none of its sub-menu items are \u003Cem>both\u003C\u002Fem> set to list items from Category A, and the page being displayed is a full post that belongs\u003Cbr \u002F>\nto category A : CMW will more than likely determine that the root level item is the Current Item, whereas you really need the\u003Cbr \u002F>\nsub-menu item to be the Current Item (probably to maintain consistency with what is produced when other sub-menu items are “current”).\u003C\u002Fp>\n\u003Cp>Enabling this fallback will make CMW use the last-found (instead of first-found) candidate for Current item, ie. when\u003Cbr \u002F>\nthe choice is between a submenu item or its parent item, the submenu item will be used.\u003C\u002Fp>\n\u003Cp>Note that this option is most likely to only have any effect when the \u003Ccode>If no Current Item can be found\u003C\u002Fcode> fallback (above) is\u003Cbr \u002F>\nenabled, but given that any other plugin\u002Ftheme could affect the menu item structure that gets passed thru to CMW it is not\u003Cbr \u002F>\nimpossible for other configurations to also be affected.\u003C\u002Fp>\n\u003Ch3>Output Section\u003C\u002Fh3>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Hierarchical\u003C\u002Fstrong> \u003Cem>(radio, default On)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Output in the standard nested list format. The alternative is \u003Ccode>Flat\u003C\u002Fcode>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Flat\u003C\u002Fstrong> \u003Cem>(radio)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Output in a single list format, ignoring any parent-child relationship other than to maintain the same physical order as would be\u003Cbr \u002F>\npresented in a \u003Ccode>Hierarchical\u003C\u002Fcode> output (which is the alternative and default).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Cem>Set Title from\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>These allow you to set the \u003Ccode>Title\u003C\u002Fcode> option from a menu item, and, if brought into play, the \u003Ccode>Hide\u003C\u002Fcode> flag is ignored.\u003Cbr \u002F>\nNote that the item providing the \u003Ccode>Title\u003C\u002Fcode> only has to be within the selected menu; it does not have to be present in the final output!\u003Cbr \u002F>\nNote also that a \u003Ccode>Current Item\u003C\u002Fcode> setting will be used in preference to a \u003Ccode>Branch Item\u003C\u002Fcode> setting.\u003C\u002Fp>\n\u003Cp>A relative setting – such as \u003Ccode>Currrent Item\u003C\u002Fcode> “-2 levels” – will top out at the root-level ancestor (which\u003Cbr \u002F>\ncould be the Current\u002FBranch Item!) if there aren’t enough ancestors available.\u003Cbr \u002F>\nAlso, an absolute setting – such as \u003Ccode>Branch Item\u003C\u002Fcode> “level 4” – will bottom out at the Current\u002FBranch Item\u003Cbr \u002F>\nif it’s at\u002Fabove the absolute level specified.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Current Item\u003C\u002Fstrong> \u003Cem>(select)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Sets \u003Ccode>Title\u003C\u002Fcode> from the current menu item (if current menu item is in the selected menu), or an ancestor\u003Cbr \u002F>\nof that item, either at an absolute or relative level.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Branch Item\u003C\u002Fstrong> *(select)\u003C\u002Fp>\n\u003Cp>Only applicable to a \u003Ccode>Branch\u003C\u002Fcode> filter, and sets \u003Ccode>Title\u003C\u002Fcode> from the \u003Ccode>Branch\u003C\u002Fcode> item, or an ancestor\u003Cbr \u002F>\nof that item, either at an absolute or relative level.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Make it a Link\u003C\u002Fstrong> \u003Cem>(checkbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>If the widget \u003Ccode>Title\u003C\u002Fcode> does actually get set using one of the options above, then this will\u003Cbr \u002F>\nput an anchor around the title, using the information from the menu item that supplies the title.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Cem>Change UL to OL\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The standard for menus is to use UL (unordered list) elements to display the output. These settings give you the option to\u003Cbr \u002F>\nswap the ULs out for OLs (ordered lists).\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Top Level\u003C\u002Fstrong> \u003Cem>(checkbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Swap the outermost UL for an OL.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Sub-Levels\u003C\u002Fstrong> \u003Cem>(checkbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Swap any nested (ie. not the outermost) ULs for an OLs.\u003C\u002Fp>\n\u003Ch3>Container Section\u003C\u002Fh3>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Element\u003C\u002Fstrong> \u003Cem>(textbox, default “div”)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>The menu list is usually wrapped in a “container” element, and this is the tag for that element.\u003Cbr \u002F>\nYou may change it for another tag, or you may clear it out and the container will be completely removed. Please note that\u003Cbr \u002F>\nWordPress is set by default to only accept “div” or “nav”, but that could be changed or extended by any theme or plugin.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Unique ID\u003C\u002Fstrong> \u003Cem>(textbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This allows you to specify your own id (which should be unique) for the container.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Class\u003C\u002Fstrong> \u003Cem>(textbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This allows you to add your own class to the container element.\u003C\u002Fp>\n\u003Ch3>Classes Section\u003C\u002Fh3>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Menu Class\u003C\u002Fstrong> \u003Cem>(textbox, default “menu-widget”)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This is the class that will be applied to the list element that holds the entire menu.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Widget Class\u003C\u002Fstrong> \u003Cem>(textbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This allows you to add your own class to the outermost element of the widget, the one that wraps the entire widget output.\u003C\u002Fp>\n\u003Ch3>Links Section\u003C\u002Fh3>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Before the Link\u003C\u002Fstrong> \u003Cem>(textbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Text or HTML that will be placed immediately before each menu item’s link.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>After the Link\u003C\u002Fstrong> \u003Cem>(textbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Text or HTML that will be placed immediately after each menu item’s link.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Before the Link Text\u003C\u002Fstrong> \u003Cem>(textbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Text or HTML that will be placed immediately before each menu item’s link text.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>After the Link Text\u003C\u002Fstrong> \u003Cem>(textbox)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Text or HTML that will be placed immediately after each menu item’s link text.\u003C\u002Fp>\n\u003Ch3>Alternative Section\u003C\u002Fh3>\n\u003Cp>This is new at v3.1.0 and provides a limited dual-scenario capability, based on a couple of conditions. For example, let’s say you\u003Cbr \u002F>\nwant to show the Current Item and its immediate children, \u003Cem>but\u003C\u002Fem> if there isn’t a Current Item then you want to show the top 2 levels\u003Cbr \u002F>\nof the menu : previously this was not possible solely with CMW, but now you can configure the main widget settings for the “current item”\u003Cbr \u002F>\nscenario, and add an Alternative setting for when no Current Item can be determined.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>On condition\u003C\u002Fstrong> \u003Cem>(2 selects)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Select the appropriate condition for when your Alternative configuration should be used, and also the stage within the\u003Cbr \u002F>\nFilter processing when this condition should be tested for (similar to the Qualifier, \u003Ccode>Current Item is in\u003C\u002Fcode>). You need\u003Cbr \u002F>\nvalues in both selects for the Alternative to be considered.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Then switch settings to\u003C\u002Fstrong> \u003Cem>(textarea)\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This should contain a CMW-generated shortcode equivalent of the configuration that you want to switch to. Please note that leaving\u003Cbr \u002F>\nthis empty will \u003Cstrong>not\u003C\u002Fstrong> prevent the Alternative kicking in if the conditions are set and met! An empty \u003Ccode>switch to\u003C\u002Fcode> will merely default\u003Cbr \u002F>\nto the CMW’s base settings (Level 1, unlimited Depth). Also note that Alternatives cannot be nested : a primary configuration is\u003Cbr \u002F>\nallowed one chance to switch and that’s it, so providing an Alternative-that-has-an-Alternative will not work.\u003C\u002Fp>\n\u003Cp>The Assist \u003Cem>will work\u003C\u002Fem> with an Alternative – in that it displays the appropriate output – but it can get confusing as to which\u003Cbr \u002F>\nconfiguration set is being used. There is a message displayed whenever the Alternative kicks in (green if successful, red if it\u003Cbr \u002F>\nshould have kicked in but couldn’t due to an error in the alternative settings) so please take note of it.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A bit more information about the \u003Cstrong>Alternative\u003C\u002Fstrong> is available\u003Cbr \u002F>\nin \u003Ca href=\"http:\u002F\u002Fwww.wizzud.com\u002F2014\u002F10\u002F03\u002Fcustom-menu-wizard-wordpress-plugin-version-3-1\u002F\" rel=\"nofollow ugc\">this article\u003C\u002Fa>.\u003C\u002Fp>\n","Show branches or levels of your menu in a widget, or in content using a shortcode, with full customisation.",3000,263532,94,49,"2018-04-02T12:35:00.000Z","4.9.29","3.9","5.4",[28,29,30,31,32],"custom-menu","menu","navigation","partial-menu","widget","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcustom-menu-wizard\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-menu-wizard.3.3.1.zip",0,null,"2026-03-15T15:16:48.613Z",{"slug":39,"name":40,"version":41,"author":4,"author_profile":5,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":53,"download_link":54,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"menu-in-menu","Menu In Menu","1.0.0","\u003Cp>This plugin enables a Custom Menu to “include” any other Custom Menu, so groups of items that get repeated across multiple menus can be defined just once and then included into any other menu at will.\u003C\u002Fp>\n\u003Cp>If you have a set of menu items that you repeat across several menus, it can be a bit of a pain when\u003Cbr \u002F>\none of that set needs updating and you have to go through all your menus changing each one.\u003C\u002Fp>\n\u003Cp>This plugin allows you to define the subset of items as a separate menu, and then include that menu\u003Cbr \u002F>\ninto any other menu. If you then need to maintain one of the items in the subset, you only need to update\u003Cbr \u002F>\none menu, and the change automatically gets reflected in all the other menus that include that subset!\u003C\u002Fp>\n\u003Cp>It’s as easy to use as adding a Post, Page, Category or Tag to your menu…\u003C\u002Fp>\n\u003Cp>With the plugin activated, go to your Menus page in admin.\u003Cbr \u002F>\nAs well as being able to add Posts, Categories, etc, to your menu, you should now see a metabox for\u003Cbr \u002F>\n\u003Cstrong>Navigation Menus\u003C\u002Fstrong> which has checkboxes for each of your defined Menus (if you don’t see the metabox,\u003Cbr \u002F>\ncheck your Screen Options settings at the top of the page).\u003Cbr \u002F>\nAll you need to do is create your submenu (as you would any other menu),\u003Cbr \u002F>\nopen the menu you want to insert the new submenu into,\u003Cbr \u002F>\nselect the submenu from the Navigation Menus metabox,\u003Cbr \u002F>\nAdd it,\u003Cbr \u002F>\nand position it.\u003Cbr \u002F>\nSave and you’re done!\u003C\u002Fp>\n\u003Cp>The inserted Menu \u003Cem>replaces\u003C\u002Fem> the Navigation Menu item in the menu. You can insert multiple instances of the\u003Cbr \u002F>\nsame submenu into one menu, and you can include a submenu into as many other menus as you need.\u003C\u002Fp>\n\u003Ch4>Perpetual Loops\u003C\u002Fh4>\n\u003Cp>The one thing that the plugin guards against is getting into a never-ending loop : it won’t prevent you\u003Cbr \u002F>\nsetting one up (see FAQs as to why), but it \u003Cem>will not\u003C\u002Fem> output any submenu that has itself as an antecedent.\u003C\u002Fp>\n\u003Cp>For example, you can set up menus such that Menu A includes Menu B, which includes Menu C. Fine, no problem.\u003Cbr \u002F>\nHowever, if you were to also add Menu B into Menu C as a Navigation Menu item,\u003Cbr \u002F>\nthen no matter which menu you choose to output, you have a potential loop\u003Cbr \u002F>\n(… B, includes C, includes B, includes C, … and so on).\u003C\u002Fp>\n\u003Cp>If WP_DEBUG is enabled, the plugin will print a warning wherever it has taken action to prevent a loop condition.\u003Cbr \u002F>\nThis behaviour can be changed by hooking into a filter (see FAQs).\u003C\u002Fp>\n\u003Ch4>Frontend Only\u003C\u002Fh4>\n\u003Cp>The plugin only performs the menu replacement at the frontend of WordPress (ie. not on Admin pages).\u003Cbr \u002F>\nThis behaviour can be changed by hooking into a filter (see FAQs),\u003Cbr \u002F>\nbut please ensure that you do \u003Cstrong>not\u003C\u002Fstrong> enable it for the Menus admin page!\u003C\u002Fp>\n","Place one Custom Menu inside another Custom Menu",200,9607,100,4,"2016-04-02T09:19:00.000Z","4.5.33","4.3","",[29],"http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fmenu-in-menu\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmenu-in-menu.1.0.0.zip",{"slug":56,"name":57,"version":58,"author":4,"author_profile":5,"description":59,"short_description":60,"active_installs":61,"downloaded":62,"rating":46,"num_ratings":63,"last_updated":64,"tested_up_to":65,"requires_at_least":66,"requires_php":51,"tags":67,"homepage":73,"download_link":74,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"shortcodes-in-use","Shortcodes In Use","1.2.1","\u003Cul>\n\u003Cli>Can’t recall where, or if, you’ve used a certain shortcode?\u003C\u002Fli>\n\u003Cli>Want to remove a plugin and unsure if it provides shortcodes or whether you’re using them?\u003C\u002Fli>\n\u003Cli>Don’t know what shortcodes come with WordPress?\u003C\u002Fli>\n\u003Cli>Found one unrecognised shortcode but unsure where there might be others?\u003C\u002Fli>\n\u003Cli>Need to swap out a theme and don’t know if it has shortcodes that you’ve used?\u003C\u002Fli>\n\u003Cli>Want to use a shortcode for a specific bit of information but can’t remember exactly what it’s called?\u003C\u002Fli>\n\u003Cli>Need to a change a parameter for all occurences of a shortcode?\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This is a simple administration tool that lists occurences of shortcodes within post content and\u002For custom fields, and\u002For widget settings.\u003Cbr \u002F>\nYou can select, or search for, specific shortcodes, and it can filter down to a provider, location, or post type.\u003Cbr \u002F>\nIt is intended to help administrators\u002Feditors locate where shortcodes have been used, so that they can be updated, renamed, deleted, or whatever.\u003C\u002Fp>\n\u003Cp>Features include :\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Search string(s) to match against shortcode tags – space or comma delimited for multple search strings\u003C\u002Fli>\n\u003Cli>Filter by the type of provider of shortcode – whether it is provided by a plugin, your theme, internal to WordPress (eg. \u003Ccode>[gallery]\u003C\u002Fcode>), or unknown (an inactive\u002Fdeleted plugin, maybe?)\u003C\u002Fli>\n\u003Cli>Filter by a specific provider – a named plugin, for example\u003C\u002Fli>\n\u003Cli>Filter by any number of specific, recognised shortcodes\u003C\u002Fli>\n\u003Cli>Filter by where to look for the shortcode – post content, post meta data (custom fields), or widgets\u003C\u002Fli>\n\u003Cli>Filter by the type of post that contains the shortcode\u003C\u002Fli>\n\u003Cli>Results include (where relevant and available) : either the widget name and its sidebar, or a linked post title and the type of post; the shortcode and its parameters; the shortcode provider (WordPress, plugin, theme, or unknown), and where it was found\u003C\u002Fli>\n\u003Cli>Has its own shortcode, for use when a plugin or theme only declares a shortcode when not in the admin backend\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>What it does \u003Cstrong>not\u003C\u002Fstrong> do :\u003C\u002Fp>\n\u003Cul>\n\u003Cli>It does \u003Cem>not\u003C\u002Fem> provide any insight as to what any shortcode does, or how to use\u002Fconfigure it.\u003C\u002Fli>\n\u003Cli>It does \u003Cem>not\u003C\u002Fem> look at custom tables, theme options, transients.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you like this plugin (or if you don’t?), please consider taking a moment or two to give it a\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fview\u002Fplugin-reviews\u002Fshortcodes-in-use\" rel=\"ugc\">Review\u003C\u002Fa> : it helps others, and gives me valuable feedback.\u003C\u002Fp>\n\u003Ch3>Shortcode\u003C\u002Fh3>\n\u003Cp>The shortcode for this plugin is…\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[shortcodes_in_use\u002F]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>…and output is restricted to users with \u003Cstrong>edit_posts\u003C\u002Fstrong> capability.\u003C\u002Fp>\n\u003Cp>The attributes available are in line with the options available in the Tool, and each one is a filter.\u003Cbr \u002F>\nSetting an attribute for all possible values is the same as omitting that attribute.\u003C\u002Fp>\n\u003Cp>Separate filters are ANDed, ie. specifying \u003Ccode>provider=\"wordpress\" post_type=\"page\"\u003C\u002Fcode> limits the results\u003Cbr \u002F>\nto shortcode tags that are in a page \u003Cstrong>AND\u003C\u002Fstrong> provided by WordPress core.\u003C\u002Fp>\n\u003Cp>Multiple values within a filter are ORed, ie. specifying \u003Ccode>post_type=\"post page\" provider=\"wordpress\"\u003C\u002Fcode>\u003Cbr \u002F>\nlimits the results to WordPress’s own shortcode tags that are in either a post \u003Cstrong>OR\u003C\u002Fstrong> a page.\u003C\u002Fp>\n\u003Cp>When you run the Tool in admin, the equivalent shortcode for the selected options is provided at the end\u003Cbr \u002F>\nof the results. Also, the \u003Cem>sanitized\u003C\u002Fem> shortcode is repeated at the top of the shortcode’s output.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>search\u003C\u002Fstrong> (string) : A space or comma is interpreted as a delimiter, so…\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[shortcodes_in_use search=\"foo bar\"\u002F]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>…looks for any shortcode tag that contains either “foo” or “bar”.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>provider\u003C\u002Fstrong> (string) : Any one or more of \u003Cem>unknown\u003C\u002Fem>, \u003Cem>wordpress\u003C\u002Fem>, \u003Cem>plugin\u003C\u002Fem>, or \u003Cem>theme\u003C\u002Fem>,\u003Cbr \u002F>\ndelimited by either a comma or a space. For example…\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[shortcodes_in_use provider=\"plugin unknown\"\u002F]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>…reports any shortcode tag whose provider cannot be determined, or whose provider has be\u003Cbr \u002F>\ndetermined as being a plugin.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>location\u003C\u002Fstrong> (string) : Any one or more of \u003Cem>title\u003C\u002Fem>, \u003Cem>content\u003C\u002Fem>, \u003Cem>excerpt\u003C\u002Fem>, \u003Cem>meta\u003C\u002Fem> or \u003Cem>widget\u003C\u002Fem>,\u003Cbr \u002F>\ndelimited by either a comma or a space. For example…\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[shortcodes_in_use location=\"content excerpt\"\u002F]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>…reports any shortcode tag found in any main content or excerpt area.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>post_type\u003C\u002Fstrong> (string) : Any one or more of WordPress’s standard post types – \u003Cem>post\u003C\u002Fem>, \u003Cem>page\u003C\u002Fem>,\u003Cbr \u002F>\n\u003Cem>attachment\u003C\u002Fem>, etc – and\u002For any custom post types. Multiple post types are comma- or space-delimited.\u003Cbr \u002F>\nFor example…\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[shortcodes_in_use post_type=\"post,page\"\u002F]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>…reports any shortcode tag found in a post of type ‘post’ or ‘page’.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>tag\u003C\u002Fstrong> (string) : Any one or more shortcode tags, delimited by either a comma or a space. For\u003Cbr \u002F>\nexample…\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[shortcodes_in_use tag=\"shortcodes_in_use, custom_menu_wizard\"\u002F]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>…reports any occurence of either of those two shortcode tags.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>name\u003C\u002Fstrong> (string) : This allows you to specify a specific plugin and\u002For theme by name. Multiple\u003Cbr \u002F>\nnames are comma- or space-delimited, and each name \u003Cstrong>\u003Cem>must\u003C\u002Fem>\u003C\u002Fstrong> begin with either “plugin\u002F” or “theme\u002F”.\u003Cbr \u002F>\nFor example…\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[shortcodes_in_use name=\"plugin\u002FShortcodes In Use, theme\u002FTwenty Fifteen\"\u002F]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>…reports any occurence of a shortcode tag belonging to either the Shortcodes In Use plugin or\u003Cbr \u002F>\nthe Twenty Fifteen theme. Instead of the \u003Cem>name\u003C\u002Fem> of the plugin\u002Ftheme, you can supply their\u003Cbr \u002F>\ncontaining folder, so this would be an alternative for the example above…\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[shortcodes_in_use name=\"plugin\u002Fshortcodes-in-use, theme\u002Ftwentyfifteen\"\u002F]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003C\u002Ful>\n","List all the shortcodes that you have used within your content or custom fields, and find out exactly where they have been used.",80,5841,8,"2016-01-26T16:46:00.000Z","4.4.34","3.8",[68,69,70,71,72],"admin","find","locate","shortcode","tool","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fshortcodes-in-use\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fshortcodes-in-use.1.2.1.zip"]