How to move CONTACT US from the footer to navbar

[Anton Rahman]

This used to be very easy in vB 4, where there was means to edit navbar from TEMPLATE MANAGER and where the footer contained the code $show['contactus'] that can be just simply moved ?with minor adjustments- to fit in the navbar
Look up
https://www.vbulletin.com/forum/foru...-top-menu-help

But cant seem to find any similar means on vB5 To simply remove CONTACT US from the footer menu and sort of transferring it to the navigation bar menu

Also inspecting the page with firebug shows only that CONTACT US belongs to footer-tabbar, but within footer.css itself we cant see how to remove any footer-tabbar items such as CONTACT US or any other
​​​​​​​
Any ideas ? thanks all..

[Seven Skins]

Login to your site as admin.
Top of the forum homepage click "edit site"
Then "navigation bar" once admin menu appears.
Then new Navigation Item and add your link.

Do the similar procedure to remove contact us link from footer.

[Anton Rahman]

latest topic update :

This seems to be more of a bug that needs to be reported

try to delete ALL BUTTONS from site builder -----> footer -----> main navigation bar

it seems to be that you have to leave at least one button "for some reason"

look up

https://www.vbulletin.com/forum/foru...oter-to-navbar


But after all, any vB wizards that can provide a work around "without using additional.css"?

Just to remove all footer -----> main navigation bar buttons ?

Charity will be greatly appreciated :'-)

[Seven Skins]

You have to use additional.css or edit footer template if you want o hide all links in the footer.

additonal.css

#footer-tabbar .js-footer-nav-list {display: none;}

Or edit footer and remove code:

            <ul class="nav-list h-right js-footer-nav-list h-margin-right-xxl b-comp-menu-horizontal js-comp-menu-horizontal js-comp-menu--dropdown-on-xsmall b-comp-menu-dropdown--inactive" data-dropdown-trigger-phrase="go_to_ellipsis" data-dropdown-menu-classes="h-margin-vert-l b-comp-menu-dropdown--direction-up" data-dropdown-trigger-classes="b-comp-menu-dropdown__trigger--arrow">
                {vb:hook 'footer_right'}
                <vb:each from="navbarItems" value="navbarItem">
                    {vb:set navbarTitle, {vb:raw navbarItem.title}}
                    <vb:if condition="$targetAttr = $navbarItem['newWindow'] == '1' ? ' target=\'_blank\'' : ''"></vb:if>
                    <vb:if condition="!empty($navbarItem['attr'])">
                        {vb:strcat targetAttr, ' '}
                        {vb:strcat targetAttr, {vb:raw navbarItem.attr}}
                    </vb:if>
                    {vb:set normalizedUrl, {vb:raw navbarItem.normalizedUrl}}
                    <vb:if condition="$itemUrl = $navbarItem['isAbsoluteUrl'] ? $normalizedUrl : ($baseurl . '/' . $normalizedUrl)"></vb:if>
                    <vb:if condition="$requestUri = explode('?', $_SERVER['REQUEST_URI'], 2)"></vb:if>
                    <vb:if condition="$requestUri = array_shift($requestUri)"></vb:if>
                    <vb:if condition="$atCurrentItem = ($requestUri == substr($itemUrl, -strlen($requestUri)))"></vb:if>
                    <vb:if condition="$currentClass = $atCurrentItem ? 'current' : ''"></vb:if>
                    <vb:if condition="$atCurrentItem">{vb:set subnavItems, {vb:raw navbarItem.subnav}}</vb:if>

                    <li class="{vb:raw currentClass}">
                        <a{vb:raw targetAttr} href="{vb:var itemUrl}">{vb:phrase {vb:raw navbarTitle}}</a>
                    </li>

                </vb:each>
                <li><a href="#" class="js-footer-go-to-top">{vb:phrase go_to_top}</a></li>
            </ul>

[Anton Rahman]

thanks SEVEN SKINS -again- your solution was better and more comprehensive than that of vBulletin support

look up their solution on

https://www.vbulletin.com/forum/foru...oter-to-navbar

Many thanks and best wishes

[Mark.B]

Originally Posted by Anton Rahman

thanks SEVEN SKINS -again- your solution was better and more comprehensive than that of vBulletin support

look up their solution on

https://www.vbulletin.com/forum/foru...oter-to-navbar

Many thanks and best wishes

You should be aware that the vBulletin support forums do not provide support for customising code, which is what the solution above involves. That is what vbulletin,org is for, which is why you got that answer here.

Code customisations are completely unsupported and may break following an upgrade. That's not to say you shouldn't apply them, as long as you understand the implications, however, having a public dig at the support team for not providing support for something we do not provide support for, isn't really on.

[TheLastSuperman]

Originally Posted by Mark.B

Code customisations are completely unsupported and may break following an upgrade. That's not to say you shouldn't apply them, as long as you understand the implications, however, having a public dig at the support team for not providing support for something we do not provide support for, isn't really on.

It's a good idea to take notes on what you do OR have done to your forum (@everyone) so for example if you have a simple change as this done, you would make notes in a saveable file with info on what was done. After you upgrade check your notes and re-apply any required changes to have all your customization restored . If you have someone do the work for you ask them ahead of time for a change-log or quick notes on what they did (for your record after an upgrade).