Hi UnLambda,
You can disable the ShiftNav toggle bar if you want in the Control Panel and add a Toggle wherever you want
Hi
Do you have a short-code or a tutorial how to make a hamburger button (see the link below) for this toggle instead of a long redundant bar with redundant text header ?
http://s1.bild.me/bilder/030315/56807502016-01-25_202012.jpg
You can just do something like this:
[shiftnav_toggle target="shiftnav-main" class="shiftnav-toggle-button" icon="bars"]Toggle Menu[/shiftnav_toggle]
I just wanted to leave a burger button shown with green arrow on the left. All the rest entire black (red arrows) bar and toggle button in middle of the black bar I wanted to get rid of.
http://s1.bild.me/bilder/030315/88950242016-01-27_041314.jpg
Right, since you want to change the standard functionality of the plugin, you’ll need to do some customizations. So use the code I gave you, remove the “Toggle Menu” part, then write some CSS to style it how you like and position it with position:fixed to display it in the proper position.
That customization exists in Pro version of your plugin in form of a check-box witch removes entire black bar and toggle button in the center of black bar ? It would be very expected to have only a sliding burger toggle button witch stays on the same place when scrolling. All that without without the redundant long black bar with toggle button in center.
Please look at this
http://contactform.looks-awesome.com/
It doesn’t have anything to do with the Pro version. The “Display Toggle Bar” setting is available in the free version as well, so you can disable the main toggle either way.
The plugin demo makes it clear what this plugin does – it creates a bar across the top of your site which you can use to toggle the menu. If you want something different from that, you are more than welcome to customize it, and ShiftNav gives you the tools to make those customizations (the ability to disable the main toggle, and place your own however you like via shortcode, HTML, or PHP). I’ve explained to you how to get the result you want, now it’s up to you to implement that. Just because a plugin doesn’t meet your use case’s exact requirements doesn’t mean that’s an issue with the plugin.
