[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fsXBDVT_0Y7TJVPT1y52gJoIQB4qQl7t-EyOW1mPapIU":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"faison","Faison","https:\u002F\u002Fprofiles.wordpress.org\u002Ffaison\u002F",3,9220,85,30,84,"2026-04-05T01:30:51.378Z",[14,39,57],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":20,"downloaded":21,"rating":22,"num_ratings":23,"last_updated":24,"tested_up_to":25,"requires_at_least":26,"requires_php":27,"tags":28,"homepage":34,"download_link":35,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"advanced-custom-fields-nav-menu-field","Advanced Custom Fields: Nav Menu Field","2.0.0","\u003Cp>Add \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FNavigation_Menus\" rel=\"nofollow ugc\">Navigation Menus\u003C\u002Fa> to \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fadvanced-custom-fields\u002F\" rel=\"ugc\">Advanced Custom Fields\u003C\u002Fa> (ACF) with the Nav Menu Field plugin! This plugin adds the Nav Menu Field type to ACF (version 5 & 4), allowing you to select from the menus you create in the WordPress Admin backend to use on your website’s frontend.\u003C\u002Fp>\n\u003Cp>Using ACF, you can set the Nav Menu Field to return the selected menu’s:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>ID for lightweight coding,\u003C\u002Fli>\n\u003Cli>Object for more involved programming, or\u003C\u002Fli>\n\u003Cli>HTML (generated from \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fwp_nav_menu\" rel=\"nofollow ugc\">wp_nav_menu\u003C\u002Fa>) for quickly displaying a menu.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>I created this plugin because I needed to display a secondary menu that changed depending on what page you’re on. Most of those pages were children of the same page, but then I had to throw a couple of Custom Post Types in there too. Because of the Custom Post Types, I couldn’t just grab the top most parent for the current page and use \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fwp_list_pages\" rel=\"nofollow ugc\">wp_list_pages\u003C\u002Fa>. So I did some research and decided to extend the functionality of my favourite plugin, \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fadvanced-custom-fields\u002F\" rel=\"ugc\">Advanced Custom Fields\u003C\u002Fa>. Now when I create a new Page or Custom Post, I just select the menu from a drop down menu!\u003C\u002Fp>\n\u003Cp>Feel free to try this add-on on your dev site, ask questions on the support link above, and please review this add-on. By leaving a rating and review, you help this plugin become even better!\u003C\u002Fp>\n\u003Ch4>Advanced Custom Fields Compatibility\u003C\u002Fh4>\n\u003Cp>This add-on will work with:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>version 5\u003C\u002Fli>\n\u003Cli>version 4\u003C\u002Fli>\n\u003C\u002Ful>\n","Add-On plugin for Advanced Custom Fields (ACF) that adds a 'Nav Menu' Field type.",9000,133924,100,33,"2017-11-28T12:59:00.000Z","4.0.38","3.4","",[29,30,31,32,33],"acf","acf4","acf5","advanced-custom-fields","custom-fields","http:\u002F\u002Ffaisonz.com\u002Fwordpress-plugins\u002Fadvanced-custom-fields-nav-menu-field\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fadvanced-custom-fields-nav-menu-field.2.0.0.zip",0,null,"2026-03-15T15:16:48.613Z",{"slug":40,"name":41,"version":17,"author":5,"author_profile":6,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":22,"num_ratings":46,"last_updated":47,"tested_up_to":25,"requires_at_least":48,"requires_php":27,"tags":49,"homepage":55,"download_link":56,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"navception","Navception","\u003Ch4>About Navception\u003C\u002Fh4>\n\u003Cp>Navception: The act of embedding a pre-constructed WordPress Menu inside another WordPress Menu.\u003C\u002Fp>\n\u003Cp>Navception adds a simple feature to WordPress Menus, but opens the door to powerful possibilities. New to your WordPress Nav Menu editor, is a box that lets you add menus into your menus! This allows you to create one menu to include as a submenu once in another menu, multiple times in another menu, or multiple times in multiple menus. What makes this so powerful is that if you decide that your submenu needs another link added to it, you only have to update it in one place! Navception, a simple concept with powerful results!\u003C\u002Fp>\n\u003Cp>Let’s look at a couple of scenarios:\u003C\u002Fp>\n\u003Ch4>Without Navception\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>If you have a submenu you need repeated across your site: First you have to add all the links everywhere you want the submenu, then to update the submenu you have to modify the links everywhere the submenu exists.\u003C\u002Fli>\n\u003Cli>If you have too many menu items in your menu: You have to pick and choose which menu items are removed to make room for new ones.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>With Navception\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>If you have a submenu you need repeated across your site: First you create the submenu as a stand-alone WordPress menu and embed it where you need it once, then to update the submenu you only need to modify the links in the stand-alone menu.\u003C\u002Fli>\n\u003Cli>If you have too many menu items in your menu: You make some of the submenus separate WordPress menus and embed those new menus into the original menu to make room for more menu items.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Navception’s Inception\u003C\u002Fh4>\n\u003Cp>Navception became a thought when working on a client’s main menu. This menu was a typical 3 level menu, with two submenus that were repeated 4 times each. Those submenus were a hassle to add and a pain to maintain. When I realized that I wanted a plugin that allowed me to create a submenu once and include it as a menu item in a separate menu, I was surprised to find that no such plugin existed.\u003C\u002Fp>\n\u003Cp>Navception became a necessity when working on that same client’s main menu. This menu became so large that I received the following warning: “You are approaching the post variable limit imposed by your server configuration. Exceeding this limit may automatically delete menu items when you save.” It turns out that every Nav Menu Item in the WordPress Admin area has roughly 8 inputs associated with it. One of the aforementioned submenus contained 7 menu items, or 56 inputs. Using Navception, I created that submenu as a stand-alone WordPress menu, then included it as 1 menu item in the client’s main menu. This reduced the inputs generated by that submenu from 56 to 8. Since that submenu was included 4 times, I not only avoided the Post Variable Limit, but I also made the menu easier to manage.\u003C\u002Fp>\n\u003Ch4>Dangers of Navception\u003C\u002Fh4>\n\u003Cp>When embedding menus in other menus, you must take care not to include the same menu in itself. When done directly or indirectly, this can cause your website to go into an infinite loop (aka Limbo) when attempting to display the menu. I added some safeguards to keep you from accidentally causing this to happen, though I’m only 90% confident that I covered all scenarios. If you ever put your website into Limbo, you only need to remove the menu you embedded, then please make a post in the support forum telling me what you did so I can cover that case as well.\u003C\u002Fp>\n","Embed WordPress Menus inside of other WordPress Menus!",200,10367,9,"2014-10-22T03:46:00.000Z","3.5",[50,51,52,53,54],"menu","menu-item","menus","submenu","submenus","http:\u002F\u002Ffaisonz.com\u002Fwordpress-plugins\u002Fnavception\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnavception.2.0.0.zip",{"slug":58,"name":59,"version":60,"author":5,"author_profile":6,"description":61,"short_description":62,"active_installs":63,"downloaded":64,"rating":65,"num_ratings":66,"last_updated":67,"tested_up_to":68,"requires_at_least":69,"requires_php":27,"tags":70,"homepage":27,"download_link":76,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"project-force-field","Project Force Field","0.6.1","\u003Cp>\u003Ca href=\"http:\u002F\u002Ffaisonz.com\u002F\" title=\"Faison Zutavern's Personal Blog\" rel=\"nofollow ugc\">Faison Zutavern\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fjvalcq\" title=\"Jon's WordPress.org Profile\" rel=\"nofollow ugc\">Jon Valcq\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Femmaee\" title=\"Emma's WordPress.org profile\" rel=\"nofollow ugc\">Emma Edgar\u003C\u002Fa>, from \u003Ca href=\"http:\u002F\u002Fwww.orionweb.net\u002F\" title=\"Milwaukee Area Web Developers\" rel=\"nofollow ugc\">Orion Group LLC\u003C\u002Fa>, bring superior Brute Force Attack protection to WordPress with their new plugin, \u003Cem>Project Force Field\u003C\u002Fem>. By tracking failed login attempts and taking advantage of Apache’s mod_rewrite module, Project Force Field stops Brute Force Attacks from bogging down your sites and servers.\u003C\u002Fp>\n\u003Cp>\u003Cem>Special thanks to \u003Ca href=\"http:\u002F\u002Fwww.aykcreative.com\u002F\" title=\"Ayk Creative | Graphic Support for your Projects\" rel=\"nofollow ugc\">Chris Aykroid\u003C\u002Fa> for the plugin banner 😀\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch4>Contributing\u003C\u002Fh4>\n\u003Cp>If you would like to contribute or fork Project Force Field, we currently have a repo on Bitbucket. You can \u003Ca href=\"https:\u002F\u002Fbitbucket.org\u002Foriongroup\u002Fproject-force-field\u002F\" rel=\"nofollow ugc\">find it here\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Features!\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Sends a 403 error code to anyone visiting \u002Fwp-login.php\u003C\u002Fstrong> – All brute force attacks we’ve seen target \u002Fwp-login.php. By responding with a 403 error, \u003Cstrong>your WordPress files aren’t loaded, the Database isn’t queried\u003C\u002Fstrong>, and the attacker doesn’t figure out your password.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Changes the default login url\u003C\u002Fstrong> – While a so-called hacker is being deflected by your new Force Field, you will log in with ease at \u002Fwp-admin\u002F. When you do that, WordPress will redirect you to the new, proper login url.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Automatically changes the login when a Brute Force Attack is detected\u003C\u002Fstrong> – When too many login failures occur within a minute, Project Force Field shifts polarity! The new login you previously used now responds with a 403 error, and a large random number is now used as your login url! After some time, the login will return back to normal.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Unlimited polarity shifts\u003C\u002Fstrong> – If a Brute Force Attacker gets smart and writes a script to check for the new login url, Project Force Field will continue to detect the attack and change the login.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Define the login yourself\u003C\u002Fstrong> – By defining \u003Ccode>OGFF_LOGIN\u003C\u002Fcode> in your wp-config.php, you can set the login to be \u003Cem>almost\u003C\u002Fem> anything you want.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stops WordPress User Enumeration Exploit\u003C\u002Fstrong> – Many brute force attacks use the WordPress User Enumeration exploit to easily figure out valid usernames. We stop that to protect your site, and respond with a 403 to save your server.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Future Features!\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Multisite Support\u003C\u002Fstrong> – It’s not there yet, that’s pretty lame, so I’m going to fix that before anything else!\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Adjust the login failure threshold\u003C\u002Fstrong> – Currently, Project Force Field assumes a brute force is underway when there have been 30 login failures within a minute. This might not be ideal for large websites, so we want to let you increase that amount to 300 if needed.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Add optional email notification for brute force events\u003C\u002Fstrong> – If you want to know when your website is under attack, we want to let you know. In a near future version, we will let you add email addresses to be notified of brute force attacks, and any other important related events that we add in the future.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Add last resort .htaccess password lockdown\u003C\u002Fstrong> – If a so-called hacker writes a script that continues to learn the new login url, Project Force Field won’t help much. In an upcoming version, we will check to see how many times the login url was changed, determine if the Brute Force Attack is smart, and lockdown the login with an .htaccess password.\u003C\u002Fli>\n\u003C\u002Ful>\n","Save your WordPress sites and servers from certain death during brute force attacks with Project Force Field by Orion Group!",20,3420,92,16,"2014-05-13T04:12:00.000Z","3.9.40","3.8",[71,72,73,74,75],"apache","brute-force","brute-force-attack","brute-force-protection","modrewrite","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fproject-force-field.0.6.1.zip"]