Title: Faison's Replies | WordPress.org --- # Faison [ ](https://wordpress.org/support/users/faison/) * [Profile](https://wordpress.org/support/users/faison/) * [Topics Started](https://wordpress.org/support/users/faison/topics/) * [Replies Created](https://wordpress.org/support/users/faison/replies/) * [Reviews Written](https://wordpress.org/support/users/faison/reviews/) * [Topics Replied To](https://wordpress.org/support/users/faison/replied-to/) * [Engagements](https://wordpress.org/support/users/faison/engagements/) * [Favorites](https://wordpress.org/support/users/faison/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 72 total) 1 [2](https://wordpress.org/support/users/faison/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/faison/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/faison/replies/page/4/?output_format=md) [5](https://wordpress.org/support/users/faison/replies/page/5/?output_format=md) [→](https://wordpress.org/support/users/faison/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Navception] Adding sub-menus seems to break menu display](https://wordpress.org/support/topic/adding-sub-menus-seems-to-break-menu-display/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 8 months ago](https://wordpress.org/support/topic/adding-sub-menus-seems-to-break-menu-display/#post-5429431) * Hi natehawkes, * I completely understand, I just wanted to provide you with a fast way to solve the problem on your site while work on the proper solution is under way. * Those two pastebins help a lot. To make Navception work well with other Nav Menu plugins, I had to drastically change how the sub menus were added to the mix. You can see this in some of the menu item IDs: “menu-item-648**-navception2**” and “menu-item-414**-navception2-4**” for example. * I did some exhaustive testing to make sure the changes were solid, but your experience shows that I missed something. I’ll need to recreate this in the next couple of days (sorry, works a bit full this week) so I just need to ask a couple of questions. * I see that you have some submenus nested in other submenus. Does this go any deeper than 2 levels of nesting? Could you show me your call to wp_nav_menu for this menu? Do you know if you’re using a custom Nav Walker? * That should help me get started on figuring out what’s happening here. * Thanks, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Navception] Adding sub-menus seems to break menu display](https://wordpress.org/support/topic/adding-sub-menus-seems-to-break-menu-display/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 8 months ago](https://wordpress.org/support/topic/adding-sub-menus-seems-to-break-menu-display/#post-5429361) * Hi natehawkes, * That’s a pretty big bug :\ If you need to fix this on an existing site right away, you can download version 1.0.0 on github [here](https://github.com/Faison/Navception/tree/1.0.0) * Now on to troubleshooting. Can you give me an example of what the menu structure looks like for the main menu and one of the sub menus that causes the issue? Also, are the menu items still in the html, but hidden, or are they completely removed from the html? I ask this because there was a css class I added in 1.0.0 that was removed in 2.0.0. Basically any details you think would be helpful for me would be great 🙂 * Sorry about the difficulties, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Nav Menu Field] Sub menu showing all the time](https://wordpress.org/support/topic/sub-menu-showing-all-the-time/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 8 months ago](https://wordpress.org/support/topic/sub-menu-showing-all-the-time/#post-5425880) * Hi Again, * This plugin only adds the menu html, it doesn’t add any front end CSS or JavaScript. So adding your own CSS isn’t a hack, it’s recommended 🙂 * Thanks, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Nav Menu Field] Menu not showing on front end](https://wordpress.org/support/topic/menu-not-showing-on-front-end/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 8 months ago](https://wordpress.org/support/topic/menu-not-showing-on-front-end/#post-5425313) * Hi there, * It looks like the Nav Menu Field is set to return the Menu ID. To fix this, edit the field group with the menu in it. Edit the Nav Menu Field. Make sure the option labeled “Return Value” is set to “Nav Menu HTML”. * Give that a shot and let me know if it worked. * Thanks, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Navception] Issues with mega Menu](https://wordpress.org/support/topic/issues-with-mega-menu/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 8 months ago](https://wordpress.org/support/topic/issues-with-mega-menu/#post-5124130) * Hi hartmutnz, * I rewrote most of Navception and it should work well with custom nav walkers, which I believe Mega Menu uses. Might be worth trying again. * Thanks, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Navception] Prevents Custom Navwalkers](https://wordpress.org/support/topic/prevents-custom-navwalkers/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 8 months ago](https://wordpress.org/support/topic/prevents-custom-navwalkers/#post-5063679) * Hey bretterer, * Navception now plays well with Custom Nav Walkers. So if you need menus in your menus in the future, Navception might be a viable option now 🙂 * Thanks, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Nav Menu Field] ACF 5 compatibility](https://wordpress.org/support/topic/acf-5-compatibility/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 8 months ago](https://wordpress.org/support/topic/acf-5-compatibility/#post-5005088) * Hi frebro and Andi (mangopeargroup), * Thank you for testing 2.0.0, It is now up-to-date on wp.org 🙂 * Thanks, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Nav Menu Field] ACF 5 compatibility](https://wordpress.org/support/topic/acf-5-compatibility/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 9 months ago](https://wordpress.org/support/topic/acf-5-compatibility/#post-5005085) * Thanks, I look forward to hearing back from you 😀 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Nav Menu Field] Field not displaying on front-end](https://wordpress.org/support/topic/field-not-displaying-on-front-end/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 9 months ago](https://wordpress.org/support/topic/field-not-displaying-on-front-end/#post-5066197) * Hi rarcommunications, * Did you ever figure out the answer to your questions? I started a new job before you asked your question and just got settled in enough to start answering support questions. So if you still need help, let me know and I’ll see what I can do. * Thanks, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Nav Menu Field] Include the plugins path](https://wordpress.org/support/topic/include-the-plugins-path/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 9 months ago](https://wordpress.org/support/topic/include-the-plugins-path/#post-4907559) * Hi Andi Lee Davis, * Sorry for the late response. The installation instructions were pulled in directly from the plugin template that the developer of ACF provides, and since this was my first plugin, I didn’t know if that should still be valid. * I’ve just updated the plugin (currently just on github) and the installation instructions will be much more clear. Basically make sure you have ACF installed, then install this plugin through the plugin installer. * So sorry for that confusion. * Regarding your question about adding data-filter and data-expand: Assuming you haven’t figured out a way to do that in one way or another, the best way to manage that would be through a filter. I don’t have the time to go into too much detail, but it looks like the filter you would need is “nav_menu_link_attributes”. If you google that, look it up in the codex, or even in WordPress core, that could get you started. * Thanks, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Nav Menu Field] I am stupid….Help](https://wordpress.org/support/topic/i-am-stupidhelp/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 9 months ago](https://wordpress.org/support/topic/i-am-stupidhelp/#post-4862670) * Hi firstforward, * This plugin should just be installed as a plugin, through the plugin installer or via FTP. Those instructions are being updated with the next version of this plugin (which also adds ACF v5 support). You can check out the next version on github: [https://github.com/Faison/ACF-Nav-Menu-Field/tree/2.0.0](https://github.com/Faison/ACF-Nav-Menu-Field/tree/2.0.0) * Sorry about the confusion. * Thanks, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Nav Menu Field] update "include" code in installation instructions](https://wordpress.org/support/topic/update-include-code-in-installation-instructions/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 9 months ago](https://wordpress.org/support/topic/update-include-code-in-installation-instructions/#post-5333606) * Hi Dadra, * The solution suggested in that post wouldn’t fix the issue you’re having. This was the first plugin I made and I blindly followed what the ACF developer put in his plugin template, including the installation instructions. I’m changing the installation instructions soon to say that the plugin should only be installed as plugins are normally installed, because that’s what I now recommend. * Could you try installing this plugin through the WordPress plugin installer and tell me if you get the error still. If you get the error, could you paste it in a response so I can track down the cause? * Also, I have version 2.0.0 in sort of a “beta” state on github. If you would like to try that out (installing through FTP), you can find it here: [https://github.com/Faison/ACF-Nav-Menu-Field/tree/2.0.0](https://github.com/Faison/ACF-Nav-Menu-Field/tree/2.0.0) * Thanks, Faison * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Nav Menu Field] ACF 5 compatibility](https://wordpress.org/support/topic/acf-5-compatibility/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [11 years, 9 months ago](https://wordpress.org/support/topic/acf-5-compatibility/#post-5005081) * Hi Everyone, * Sorry for my absence. I actually started work on adding ACF v5 support earlier this year, but then I got a job at 10up and had to put my plugins on hold while I settled in. * Anyways, I’m settled in now and had the time tonight to put ACF Nav Menu Fields on Github. I started a 2.0.0 branch where I added support for ACF v5 (as well as cleaned up all my original code that made babies cry). If any of you are all still around, I was wondering if you could manually install the 2.0.0 branch and tell me if everything appears to be running smoothly? I just want to have a little bit of testing before pushing the changes live to wordpress.org. * You can find the 2.0.0 branch here: [https://github.com/Faison/ACF-Nav-Menu-Field/tree/2.0.0](https://github.com/Faison/ACF-Nav-Menu-Field/tree/2.0.0) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Project Force Field] Completely disable login](https://wordpress.org/support/topic/completely-disable-login/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [12 years, 1 month ago](https://wordpress.org/support/topic/completely-disable-login/#post-4975929) * Glad to hear, chadmohr! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Project Force Field] Completely disable login](https://wordpress.org/support/topic/completely-disable-login/) * Plugin Author [Faison](https://wordpress.org/support/users/faison/) * (@faison) * [12 years, 1 month ago](https://wordpress.org/support/topic/completely-disable-login/#post-4975911) * When you go to log in, are you going to `/wp-login.php` or `/wp-admin/`? * Does your .htaccess file contain the following lines? * ``` # BEGIN OGFF RewriteEngine On RewriteRule ^safe\-entrance\.php$ wp-login.php [NC,L] RewriteCond %{THE_REQUEST} wp\-login\.php [NC] RewriteRule ^wp\-login\.php$ - [F] RewriteCond %{REQUEST_URI} ^/$ RewriteCond %{QUERY_STRING} ^/?author=([0-9]*) RewriteRule ^(.*)$ - [F] # END OGFF ``` * Thanks, Faison Viewing 15 replies - 1 through 15 (of 72 total) 1 [2](https://wordpress.org/support/users/faison/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/faison/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/faison/replies/page/4/?output_format=md) [5](https://wordpress.org/support/users/faison/replies/page/5/?output_format=md) [→](https://wordpress.org/support/users/faison/replies/page/2/?output_format=md)