Digital experiences for all disciplines
New Landing › How can we help? › Themeforest Theme Support › Neighborhood › Make nav use hamburger menu at 1200px and below
New Landing › How can we help? › Themeforest Theme Support › Neighborhood › Make nav use hamburger menu at 1200px and below
- This topic has 32 replies, 2 voices, and was last updated 9 years by David Martin – Support.
-
Posted in: Neighborhood
-
December 7, 2015 at 9:16 pm #233790This reply has been marked as private.December 9, 2015 at 2:06 pm #234225
Can you add your FTP details?
Thanks.
December 9, 2015 at 4:26 pm #234265This reply has been marked as private.December 9, 2015 at 5:02 pm #234268I added the changes to the child theme.
Please check now.
Thanks.
December 9, 2015 at 5:21 pm #234277It’s hamburger all the time now….
December 9, 2015 at 5:23 pm #234278I’m gonna have to put the site under construction. I’ll do the updates right away. Could you please check back with me in 15 min? I have a million stuff to custom change on in the php files everytime the theme updates.
December 9, 2015 at 5:26 pm #234279Hi,
Sorry, just seen you were referring to the menu request also.
The menu hamburger modification request+sticky menu combination is not possible, the two conflict and I cannot make them reliably work for you on that requested screensize. Unfortunately that customisation will fall beyond our scope of support as it is more work than a small customisation.
Please also ask your host to setup a staging site environment where you can test updates/css tweaks away from the live site.
Thanks,
David.December 9, 2015 at 5:29 pm #234281Ok. Thank you.
December 9, 2015 at 5:34 pm #234285No problem, if you get the staging site set up here is the CSS for your reference:
@media only screen and (max-width: 1200px) { #logo { margin: 10px 20px 5px; float: none!important; width: auto; } #logo a { display: block!important; height: auto!important; } #logo a:first-child { float: left; } #logo img { margin: 0 auto; padding: 0!important; float: none!important; } #header-section #header { padding: 15px 0 0; } #header-section.header-4 #header { padding: 15px 0; } #header-section.header-5 #header { padding: 15px 0; } #header-section > #main-nav { border-top: 0; } #main-nav .row > .span9 { width: 100%; margin-left: 0; margin-bottom: 0; } #main-navigation { display: none; float: none; -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; max-width: 100%; padding: 20px; margin: 0 0 20px!important; } nav .menu > li { float: none; display: block; padding: 2px 0; width: 100%; font-size: 12px; border-top: 1px solid #e4e4e4; overflow: hidden; line-height: inherit!important; text-align: left; border: 0; } nav .menu > li:first-child { border-top-width: 0; } nav.std-menu ul.menu > li.parent > a:after { display: none; } nav .menu li a { padding: 8px 0; margin: 0; } nav .menu ul li a { padding-top: 10px; padding-bottom: 10px; font-weight: normal; } nav .menu > li > ul.sub-menu { padding: 0; } nav .menu > li > ul.sub-menu li { width: 100%!important; float: none!important; border: 0!important; } li.menu-item.sf-mega-menu.sf-mega-menu-natural-width > ul.sub-menu { width: 100%!important; } li.menu-item.sf-mega-menu.no-headings > ul.sub-menu > li ul { padding: 0!important; } nav .menu > li > ul.sub-menu li a { padding: 8px 15px; } li.menu-item.sf-mega-menu > ul.sub-menu { position: relative; left: 0; } li.menu-item.sf-mega-menu > ul.sub-menu > li.menu-item > a, li.menu-item.sf-mega-menu > ul.sub-menu > li.menu-item > span.title { margin: 0; } nav .menu ul.sub-menu, nav#top-bar-menu .menu > li > ul.sub-menu { background-color: transparent!important; position: relative; border-left: 0; border-right: 0; border-bottom: 0; left: 0; -webkit-box-shadow: none; -moz-box-shadow: none; box-shadow: none; opacity: 1; top: 0!important; padding-left: 0; pointer-events: all; } #main-navigation ul.menu > li { display: block; border-bottom: 1px solid #e3e3e3; } #main-navigation ul.menu > li:first-child { border-top: 1px solid #e3e3e3; } #main-navigation ul.menu > li > ul { margin-top: 10px; margin-bottom: 20px; } #main-navigation ul li.parent > a:after { content: "\f078"; font-family: FontAwesome; font-weight: normal; font-style: normal; display: inline-block; text-decoration: inherit; font-size: 24px; margin-right: -3px; opacity: 0.5; float: right; border-bottom: 0!important; right: 0; left: auto; font-size: 14px; font-weight: normal; margin-top: -11px; top: 50%; } #main-navigation li.parent.sub-menu-open > a:after { content: "\f077"; } li.menu-item.sf-mega-menu > ul.sub-menu > li ul { padding-top: 10px; padding-bottom: 10px; } nav .menu ul li > a { max-width: 100%; } nav#main-navigation .menu > li > a, .header-4 nav .menu > li > a, .header-4 nav .menu > li > a, .header-5 nav .menu > li > a, .header-4 nav#main-navigation .menu > li > a, .header-5 nav#main-navigation .menu > li > a { padding: 12px 0; } nav .menu ul.sub-menu li:first-child:before { display: none; } .header-right > nav:first-child, .header-2 .header-right, .header-3 .header-left, .header-3 .header-right, .header-1 .header-left, .header-1 .header-right, .header-5 .header-left > nav { display: none; } .header-4 #main-navigation, .header-5 #main-navigation { float: none; -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; max-width: 100%; padding: 20px; margin: 0!important; } .header-4 .header-right, .header-5 .header-left { margin-bottom: 0; width: 100%; margin-left: 0; } nav#main-navigation .menu ul ul { left: 5%!important; } nav .menu .sub-menu .parent > a:after { display: none; } }
December 9, 2015 at 6:14 pm #234303For some reason ALL my widgets menues footers etc is gone now. Redoing everything by hand. The new child theme is called Version: 3.2.0, right? It’s confusing that it is not called child. I’m note sure what is active anymore.
December 9, 2015 at 6:21 pm #234307Hi,
If the WP thinks a new child theme has been activated the widgets and menus will need to be dragged back into the widget areas and the menu locations set again.
The child theme should be called
neighborhood-child
unless you have made a specific new child theme?Thanks,
David.December 9, 2015 at 6:59 pm #234321I activated the the stuff you see in the images. Please let me know what happened here cuz I didn’t change no child name or nuttin.
Attachments:
You must be logged in to view attached files.December 9, 2015 at 7:02 pm #234327Now, alla my widgets think they are Eng as a set up language so I have to translate them back and forth. This is so stressful on my own live site.
December 10, 2015 at 4:09 pm #234652Apologies for the inconvenience this update caused. Please ask your host to setup a staging site for you, where you can test updates/CSS tweaks away from the live site.
Thanks.
December 10, 2015 at 6:19 pm #234704Hi David!
I figured out the the issue with the child. While updating, I accidentally updated the child to another version of the mother theme. Fixed that.
The language widget issue is solved by a work around solution: Display Widget plugin.
I still have a problem that happens every time I update theme:
Top nav “tag line” and Woo commerce modals loose their ENG translation. Please see attached image of this when my site is set to ENG.
1. Webbdesign • Väggdekor • Skyltfönster • Logo • Tryck • Canvas – is marked as ENG in WPML sting translation so I can’t translate it from there.
2. If you click for example the “Email customer care” modal, it shows the Swedish text in the pop up.It would be really nice to not have this issue every time I update, as it takes me half a day to fix everything like this. Please help.
<3
A
-
Posted in: Neighborhood
You must be logged in and have valid license to reply to this topic.