[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ffhacumJlE4jP1KevtrogQybIXulWOlB_pAVHEHlirjg":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":38,"analysis":136,"fingerprints":197},"custom-right-click-menu","Custom right click menu","1.1.1","ezhil","https:\u002F\u002Fprofiles.wordpress.org\u002Fezhil\u002F","\u003Cp>Custom right click menu plugin enables you to create a context menu instead of blocking right click for copyright and other issues.\u003C\u002Fp>\n\u003Ch3>Installation and usage\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Add and activate the plugin\u003C\u002Fli>\n\u003Cli>Enter the no of fields required\u003C\u002Fli>\n\u003C\u002Ful>\n","Custom right click menu plugin enables you to create a context menu instead of blocking right click for copyright and other issues.",10,4191,90,4,"2013-04-11T11:01:00.000Z","3.5.2","3.0","",[20,21,22,23,24],"context-menu","custom-menu","menu","right-click","right-click-menu","http:\u002F\u002Fprofiles.wordpress.org\u002Fezhil\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-right-click-menu.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":27,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},2,50,30,84,"2026-04-04T22:56:48.463Z",[39,57,73,92,115],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":28,"downloaded":47,"rating":48,"num_ratings":49,"last_updated":18,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":18,"download_link":55,"security_score":48,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":56},"super-custom-right-click-menu","Right Click Menu Builder – Custom Context Menu Maker","1.0.0","Jose Varghese","https:\u002F\u002Fprofiles.wordpress.org\u002Fjosevarghese\u002F","\u003Cp>\u003Cstrong>Right Click Menu Builder\u003C\u002Fstrong> is the ultimate solution for creating a professional \u003Cstrong>Custom Context Menu\u003C\u002Fstrong> for your website. Instead of the standard browser right-click options, you can now provide your visitors with helpful navigation shortcuts, branded links, and intuitive submenus.\u003C\u002Fp>\n\u003Cp>This \u003Cstrong>Right Click Menu Maker\u003C\u002Fstrong> is designed for speed and ease of use. With a powerful drag-and-drop interface, you can reorder menu items, create nested submenus, and customize the design to match your brand—all without touching a single line of code.\u003C\u002Fp>\n\u003Cp>Whether you want to improve your site’s User Experience (UX) or create a unique interaction for your web application, this plugin gives you complete control over the \u003Cstrong>Right Click\u003C\u002Fstrong> behavior on your WordPress site.\u003C\u002Fp>\n\u003Ch3>Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Custom Right Click Menu\u003C\u002Fstrong>: Completely override the default browser context menu.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Drag & Drop Builder\u003C\u002Fstrong>: Easily organize and reorder your right-click menu items.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Nested Submenus\u003C\u002Fstrong>: Create multi-level navigation for better organization.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Open in New Tab\u003C\u002Fstrong>: Choose to open links in the same window or a new tab.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Full Design Control\u003C\u002Fstrong>: Customize text colors, background colors, and font sizes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mobile & Touch Support\u003C\u002Fstrong>: Optional long-press support for mobile devices.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Lightweight & Fast\u003C\u002Fstrong>: Optimized for performance with minimal CSS and JS footprint.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Accessibility Ready\u003C\u002Fstrong>: Full keyboard navigation support.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Use Cases\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Fast Navigation\u003C\u002Fstrong>: Add quick links to your most important pages.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Branding\u003C\u002Fstrong>: Add your logo or custom actions to the right-click interface.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Shortcuts\u003C\u002Fstrong>: Provide easy access to contact forms, social media, or search.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Advanced UX\u003C\u002Fstrong>: Create specific actions for logged-in users or members.\u003Cbr \u002F>\nEasy to Use =\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Col>\n\u003Cli>Install and activate the plugin\u003C\u002Fli>\n\u003Cli>Go to Settings > Right Click Menu\u003C\u002Fli>\n\u003Cli>Customize colors and font size\u003C\u002Fli>\n\u003Cli>Add your menu items and submenus using drag & drop\u003C\u002Fli>\n\u003Cli>Save your settings and enjoy your custom right-click menu!\u003C\u002Fli>\n\u003C\u002Fol>\n","Build a fully customizable WordPress right-click menu. Replace default browser menus with a custom context menu using a drag-and-drop builder.",266,100,1,"6.9.4","5.0","7.4",[20,21,54,23,24],"navigation","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsuper-custom-right-click-menu.1.0.0.zip","2026-03-15T10:48:56.248Z",{"slug":24,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":11,"downloaded":64,"rating":65,"num_ratings":33,"last_updated":66,"tested_up_to":50,"requires_at_least":67,"requires_php":18,"tags":68,"homepage":71,"download_link":72,"security_score":48,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"Right Click Menu","2.2.1","Suman Biswas","https:\u002F\u002Fprofiles.wordpress.org\u002Fsumanbiswas013\u002F","\u003Cp>User will get a site menu by mouse right click on any page.\u003Cbr \u002F>\nAdmin can set a menu from admin menu section.\u003C\u002Fp>\n\u003Ch3>A brief Markdown Example\u003C\u002Fh3>\n","User will get a site menu by mouse right click on any page. Admin can set a menu from admin menu section.",1642,60,"2026-01-28T20:30:00.000Z","3.0.1",[69,21,22,24,70],"admin-menu","wordpress-menu","http:\u002F\u002Fdeveloperssuman.orgfree.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fright-click-menu.2.0.zip",{"slug":74,"name":75,"version":76,"author":77,"author_profile":78,"description":79,"short_description":80,"active_installs":81,"downloaded":82,"rating":65,"num_ratings":49,"last_updated":83,"tested_up_to":84,"requires_at_least":85,"requires_php":18,"tags":86,"homepage":90,"download_link":91,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"wp-awesome","HUEM: Huge Upload Enabler, mostly","1.0.1","frodeborli","https:\u002F\u002Fprofiles.wordpress.org\u002Ffrodeborli\u002F","\u003Cp>HUEAM is a plugin that tries to make improvements to WordPress, while not interfering with the way WordPress works. When you install the plugin, you will not notice any immediate changes – but these features have been silently enabled.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Smart Context Menus\u003C\u002Fli>\n\u003Cli>Chunked uploads to bypass php.ini and .htaccess upload limitations.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>We’re looking into more exciting improvements to add, and you will be able to easily enable or disable them.\u003C\u002Fp>\n\u003Ch3>Smart Context Menus\u003C\u002Fh3>\n\u003Cp>Right clicking any element in site preview mode now will render a nice context menu – that will take you directly to the appropriate admin page for editing. You (or your customer) will never again have to ask where to find the feature. It will save you thousands of mouse clicks.\u003C\u002Fp>\n\u003Cp>Pro tip: If you want to see the browser native context menu, simply hold CTRL while right clicking.\u003C\u002Fp>\n\u003Cp>Pro tip 2: You can extend the context menu by using the filter \u003Ccode>wpa_context_menu\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Pro tip 3: Disable the context menus in your wp-config.php file like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('WPAWESOME_DISABLE_CONTEXT_MENUS', true);\u003Ch3>Huge uploads\u003C\u002Fh3>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>By making WordPress upload files in multiple chunks, you can now upload huge files through the standard WordPress user interface. No more editing of  .htaccess files, or php.ini files. The uploaded file will be split into chunks that are 1.9 MB large. The chunks are stored in the temp folder – until all chunks have been uploaded. At that time – the plugin will combine all the chunks into one file again.\u003C\u002Fp>\n\u003Cp>Pro tip: You can override the maximum upload size by defining the \u003Ccode>WPAWESOME_UPLOAD_LIMIT\u003C\u002Fcode> constant.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('WPAWESOME_UPLOAD_LIMIT', '10000000'); \u002F\u002F 10 MB upload limit\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Pro tip 2: Disable the context menus in your wp-config.php file like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('WPAWESOME_DISABLE_HUGE_UPLOADS', true);\u003Ch3>3 * Esc to login\u003C\u002Fh3>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Clicking ESC three times, when you’re not logged in – will take you directly to the login page. This way, you won’t have to remember the URL of the page that prompted you to login. You’ll be there instantly after login, and then you can right click the article (or widget or comment) to edit it.\u003C\u002Fp>\n\u003Cp>Pro tip: Disable the context menus in your wp-config.php file like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('WPAWESOME_DISABLE_FAST_LOGIN', true);\u003Ch3>Contribute\u003C\u002Fh3>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Module Authors\u003C\u002Fh4>\n\u003Cp>The plugin can be easily extended by adding a filter \u003Ccode>add_filter( 'wpa_context_menu', 'my_context_menu', 10, 2)\u003C\u002Fcode>. The \u003Ccode>function my_context_menu\u003C\u002Fcode> must accept $menu and $items arguments. $items is inspected to detect which element the user clicked. You can look at tag names, class names, element ids and more. If you want to add menu items, you’ll simply modify the $menu array structure to add your own choices.\u003C\u002Fp>\n\u003Cp>The best way to contribute, is if your module or theme integrates with HUEAM or if you contribute a patch. Patches should fix bugs, improve the user experience or add features. Please don’t provide patches that make WP Awesome support other modules, unless that other module is extremely popular.\u003C\u002Fp>\n\u003Cp>There’s a \u003Ca href=\"https:\u002F\u002Fbitbucket.org\u002Fwpmotor\u002Fwpawesome\" rel=\"nofollow ugc\">GIT repository and wiki\u003C\u002Fa> too if you want to contribute a patch, a translation, provide bug reports or in any other way contribute.\u003C\u002Fp>\n\u003Ch4>Translators\u003C\u002Fh4>\n\u003Cp>The plugin currently has very few translatable strings, but there are a couple. If you want to contribute with translations there are two ways:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Send a pull request to our bitbucket repository, with your translation file in the Languages\u002F folder.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Upload your pot-file to  https:\u002F\u002Fbitbucket.org\u002Fwpmotor\u002Fwpawesome\u002Fissues\u002Fnew and mark it as a proposal. We support translation files, but have only a very few translations available at the moment.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Recommended Settings\u003C\u002Fh3>\n\u003Cp>There are no configuration needed to use this plugin. Just install it, and you are ready. Setting defaults can be configured in wp-config.php, and they can be overridden in the WP Awesome options panel.\u003C\u002Fp>\n","Allows you to bypass the upload size limitations of the server.",20,3336,"2017-01-03T23:10:00.000Z","4.7.32","4.6",[87,20,23,88,89],"content-aware-menu","upload-limit","usability","http:\u002F\u002Fplugins.wpmotor.no\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-awesome.1.0.1.zip",{"slug":93,"name":94,"version":95,"author":96,"author_profile":97,"description":98,"short_description":99,"active_installs":100,"downloaded":101,"rating":13,"num_ratings":102,"last_updated":103,"tested_up_to":104,"requires_at_least":17,"requires_php":18,"tags":105,"homepage":110,"download_link":111,"security_score":112,"vuln_count":113,"unpatched_count":28,"last_vuln_date":114,"fetched_at":30},"ag-custom-admin","AGCA – Custom Dashboard & Login Page","7.2.6","cusmin","https:\u002F\u002Fprofiles.wordpress.org\u002Fcusmin\u002F","\u003Cp>With this plugin you can easily customize WordPress \u003Cstrong>admin panel\u003C\u002Fstrong>, \u003Cstrong>login page\u003C\u002Fstrong>, \u003Cstrong>admin menu\u003C\u002Fstrong>, \u003Cstrong>admin bar\u003C\u002Fstrong> etc. in tiny details.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>ADMIN BAR\u003C\u002Fstrong>: Hide or change admin bar items. Remove WordPress traces from the admin bar. Brand it with the custom colors.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ADMIN MENU\u003C\u002Fstrong>: Change and remove the existing and add custom admin menu items. Brand it with the custom colors.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>COLORIZER\u003C\u002Fstrong>: This tool is integrated with Absolutely Glamorous Custom Admin panel and can be used to change default WordPress admin panel colors, admin bar, admin menu, login page, backgrounds and text.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>BRANDING\u003C\u002Fstrong>: Brand your admin panel pages with custom content, colors, images and text.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ADMIN PANEL OPTIONS\u003C\u002Fstrong>: There are dozens of other admin panel options used to improve WordPress UX on admin and login pages items like Dashboard widgets, Help and Screen options, WordPress logos, links, menus etc. See the full list down below.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Recommended\u003C\u002Fh4>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fcusmin.com\u002Fupgrade-to-cusmin\u002F?ref=wporg-recommended\" rel=\"nofollow ugc\">CUSMIN\u003C\u002Fa>\u003C\u002Fstrong>\u003Cbr \u002F>\n  Cusmin is the premium version of the Absolutely Glamorous Custom Admin with the advanced features for customization and branding. It’s perfect for professionals, but can be also used on personal sites as well.\u003C\u002Fp>\n\u003Cp>  Please check how this pro plugin can help you to completely \u003Ca href=\"https:\u002F\u002Fcusmin.com\u002Fblog\u002Fcustomize-wordpress-dashboard\u002F?ref=wporg-recommended\" rel=\"nofollow ugc\">customize your WordPress dashboard\u003C\u002Fa>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>General Settings\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Hide \u003Cstrong>Screen Options\u003C\u002Fstrong> menu\u003C\u002Fli>\n\u003Cli>Hide \u003Cstrong>Help\u003C\u002Fstrong> menu\u003C\u002Fli>\n\u003Cli>Hide Color scheme on Profile page\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Admin Bar Settings\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Hide admin bar completely\u003C\u002Fli>\n\u003Cli>Show Log out button only if admin bar is completely hidden\u003C\u002Fli>\n\u003Cli>Hide admin bar on site pages only\u003C\u002Fli>\n\u003Cli>Replace WordPress logo with custom branding image\u003C\u002Fli>\n\u003Cli>Change link on admin bar logo\u003C\u002Fli>\n\u003Cli>Custom page title template on admin pages (change  =>  tag)\u003C\u002Fli>\n\u003Cli>Add custom branding image above the content in admin bar\u003C\u002Fli>\n\u003Cli>Hide WordPress logo\u003C\u002Fli>\n\u003Cli>Hide site name\u003C\u002Fli>\n\u003Cli>Hide admin bar logo context menu\u003C\u002Fli>\n\u003Cli>Hide update notifications block\u003C\u002Fli>\n\u003Cli>Hide \u003Cstrong>Comments\u003C\u002Fstrong> block\u003C\u002Fli>\n\u003Cli>Hide \u003Cstrong>New\u003C\u002Fstrong> menu block\u003C\u002Fli>\n\u003Cli>Hide \u003Cstrong>New\u003C\u002Fstrong> > \u003Cstrong>Post\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Hide \u003Cstrong>New\u003C\u002Fstrong> > \u003Cstrong>Link\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Hide \u003Cstrong>New\u003C\u002Fstrong> > \u003Cstrong>Page\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Hide \u003Cstrong>New\u003C\u002Fstrong> > \u003Cstrong>User\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Hide \u003Cstrong>New\u003C\u002Fstrong> > \u003Cstrong>Media\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Change site name to custom text\u003C\u002Fli>\n\u003Cli>Hide yellow WordPress update notification\u003C\u002Fli>\n\u003Cli>Change Howdy text\u003C\u002Fli>\n\u003Cli>Change Log Out text\u003C\u002Fli>\n\u003Cli>Remove \u003Cstrong>Edit My Profile\u003C\u002Fstrong> option from context menu\u003C\u002Fli>\n\u003Cli>Show \u003Cstrong>Log Out\u003C\u002Fstrong> button only on the right\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Admin Footer Options\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Hide footer completely\u003C\u002Fli>\n\u003Cli>Change\u002Fremove footer text\u003C\u002Fli>\n\u003Cli>Change\u002Fremove footer version text\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Dashboard Page Options\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Change Dashboard heading text\u003C\u002Fli>\n\u003Cli>Add custom Dashboard HTML content\u003C\u002Fli>\n\u003Cli>Hide dashboard widgets\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Login Page Options\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Hide back to blog text\u003C\u002Fli>\n\u003Cli>Change back to blog text\u003C\u002Fli>\n\u003Cli>Change login image\u003C\u002Fli>\n\u003Cli>Change hyperlink on login image\u003C\u002Fli>\n\u003Cli>Hide login image\u003C\u002Fli>\n\u003Cli>Round corners on login boxes\u003C\u002Fli>\n\u003Cli>Hide register and lost password links\u003C\u002Fli>\n\u003Cli>Change hyperlink on register button\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Admin Menu Options\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Rename menu and sub-menu items\u003C\u002Fli>\n\u003Cli>Hide menu and sub-menu items\u003C\u002Fli>\n\u003Cli>Add new buttons with custom links\u003C\u002Fli>\n\u003Cli>Remove icons from admin menu buttons\u003C\u002Fli>\n\u003Cli>Remove spaces between admin menu buttons\u003C\u002Fli>\n\u003Cli>Remove admin menu arrow on hover\u003C\u002Fli>\n\u003Cli>Round admin sub-menu popups\u003C\u002Fli>\n\u003Cli>Remove \u003Cstrong>Collapse\u003C\u002Fstrong> button\u003C\u002Fli>\n\u003Cli>Add custom branding image above the admin menu\u003C\u002Fli>\n\u003Cli>Add custom link to branding image\u003C\u002Fli>\n\u003Cli>Change admin menu auto-folding settings\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Colorizer\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Change background and text colors on admin and login page\u003C\u002Fli>\n\u003Cli>Change admin menu colors\u003C\u002Fli>\n\u003Cli>Change widget colors\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Advanced\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Add custom CSS\u003C\u002Fli>\n\u003Cli>Add custom JavaScript\u003C\u002Fli>\n\u003Cli>Export\u002Fimport customizations settings\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fcusmin.com\u002Fupgrade-to-cusmin\u002F?ref=wporg-pro\" rel=\"nofollow ugc\">PRO FEATURES\u003C\u002Fa>\u003C\u002Fstrong>\u003Cbr \u002F>\n  If you need even more advanced customization options, please check our \u003Ca href=\"https:\u002F\u002Fcusmin.com\u002Fblog\u002Fcustomize-wordpress-dashboard\u002F?ref=wporg-pro\" rel=\"nofollow ugc\">PRO WordPress customizing plugin\u003C\u002Fa>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Contact\u003C\u002Fh4>\n\u003Cp>For any additional help, please check our \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fag-custom-admin\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fag-custom-admin\" rel=\"ugc\">SUPPORT\u003C\u002Fa> page.\u003C\u002Fp>\n","CHANGE: admin menu, login page, admin bar, dashboard widgets, custom colors, custom CSS & JS, logo & images",20000,1060634,64,"2025-05-30T08:22:00.000Z","6.8.5",[106,107,108,21,109],"custom-admin","custom-dashboard","custom-login","white-label","https:\u002F\u002Fcusmin.com\u002Fagca","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fag-custom-admin.7.2.6.zip",97,5,"2024-04-24 00:00:00",{"slug":116,"name":117,"version":118,"author":119,"author_profile":120,"description":121,"short_description":122,"active_installs":123,"downloaded":124,"rating":125,"num_ratings":126,"last_updated":127,"tested_up_to":128,"requires_at_least":129,"requires_php":130,"tags":131,"homepage":134,"download_link":135,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"custom-menu-wizard","Custom Menu Wizard Widget","3.3.1","wizzud","https:\u002F\u002Fprofiles.wordpress.org\u002Fwizzud\u002F","\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",[21,22,54,132,133],"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",{"attackSurface":137,"codeSignals":164,"taintFlows":185,"riskAssessment":186,"analyzedAt":196},{"hooks":138,"ajaxHandlers":160,"restRoutes":161,"shortcodes":162,"cronEvents":163,"entryPointCount":28,"unprotectedCount":28},[139,145,148,152,156],{"type":140,"name":141,"callback":142,"file":143,"line":144},"action","admin_init","sa_register_settings","rc.php",47,{"type":140,"name":146,"callback":147,"file":143,"line":126},"admin_menu","rc_admin_menus",{"type":140,"name":149,"callback":150,"file":143,"line":151},"wp_enqueue_scripts","jq_rc_load",124,{"type":140,"name":153,"callback":154,"file":143,"line":155},"wp_head","rc_main_sc",206,{"type":140,"name":157,"callback":158,"file":143,"line":159},"wp_footer","rc_foot_sc",207,[],[],[],[],{"dangerousFunctions":165,"sqlUsage":166,"outputEscaping":168,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":184},[],{"prepared":28,"raw":28,"locations":167},[],{"escaped":28,"rawEcho":169,"locations":170},8,[171,174,175,177,178,180,182,183],{"file":143,"line":172,"context":173},96,"raw output",{"file":143,"line":172,"context":173},{"file":143,"line":176,"context":173},99,{"file":143,"line":176,"context":173},{"file":143,"line":179,"context":173},174,{"file":143,"line":181,"context":173},216,{"file":143,"line":181,"context":173},{"file":143,"line":181,"context":173},[],[],{"summary":187,"deductions":188},"The \"custom-right-click-menu\" plugin, version 1.1.1, exhibits a generally good security posture in terms of its attack surface and known vulnerability history.  The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the potential entry points for attackers. Furthermore, the complete lack of recorded CVEs and the use of prepared statements for all SQL queries are strong indicators of responsible development and a proactive approach to security. The plugin also reports no file operations or external HTTP requests, which further reduces the risk of certain attack vectors.\n\nHowever, the static analysis reveals a critical weakness: 0% of output escaping. With 8 total outputs identified, this means that all user-provided data or dynamic content displayed by the plugin is likely not being properly sanitized before rendering. This opens the door to potential Cross-Site Scripting (XSS) vulnerabilities, where an attacker could inject malicious scripts into the website, impacting users or the site itself. The lack of capability checks and nonce checks also means that any logic executed by the plugin may not have sufficient authorization or integrity checks, although the limited attack surface mitigates the immediate impact of this in the current version.\n\nIn conclusion, while the plugin has a clean vulnerability history and avoids common pitfalls like raw SQL and external requests, the complete failure in output escaping represents a significant and immediate risk. Addressing this vulnerability is paramount to improving the plugin's overall security. The limited attack surface and lack of known vulnerabilities are positive attributes, but the XSS risk needs to be prioritized.",[189,191,194],{"reason":190,"points":169},"0% of output escaping found",{"reason":192,"points":193},"0 capability checks found",3,{"reason":195,"points":193},"0 nonce checks found","2026-03-16T23:40:05.109Z",{"wat":198,"direct":203},{"assetPaths":199,"generatorPatterns":200,"scriptPaths":201,"versionParams":202},[],[],[],[],{"cssClasses":204,"htmlComments":205,"htmlAttributes":206,"restEndpoints":207,"jsGlobals":208,"shortcodeOutput":209},[],[],[],[],[],[]]