-
AuthorPosts
-
October 2, 2016 at 7:48 pm #694352
I have some CSS in the quick CSS field but since the last update the CSS does not work. I have copy pasted the css below. Why is this not working anymore?
/* START – do not show logo in desktop design */
.logo { display: none; }
/* END *//* START – do not show logo in mobile design */
@media only screen and (max-width: 767px) {
.responsive .logo { display: none !important; }/* div .main_color .tabcontainer .active_tab_content { background-color: #0694D2; }
*/div .main_color .tabcontainer .active_tab { background-color: #EF7F1B; color: white;}
/* START – remove arrows to previous and next gallery */
#top .avia-post-nav { display: none; }
/* END *//* start – position and thickness line under main menu */
.avia-menu-fx { bottom: 10px; }
.avia-menu-fx {
height: 3px;
width:74%;
left:13%;
}
/* END */#advanced_menu_toggle, #advanced_menu_hide {
margin-top: 10px;
}#header_main {
min-height: 82px;
}
}
/* END */October 3, 2016 at 5:25 am #694411Hey winnieandbuzz,
Please post us your login credentials (in the “private data” field), so we can take a look at your backend.
Login credentials include:
- The URL to the login screen.
- A valid username (with full administration capabilities).
- As well as a password for that username.
- permission to deactivate plugins if necessary.
Best regards,
JordanOctober 7, 2016 at 4:25 pm #696585Hi,
Login details provided. I deactivated ALL plugins but the issue was still there. You may deactivate the plugins but do please look at my comment in the private section to activate one plugin ASAP after deactivating it as it will publish the whole website which I don’t want.
October 7, 2016 at 4:36 pm #696600Hi!
I moved your code from Quick CSS to Style.css file of your child theme in Appearance > Editor and tried adding following code to bottom of Style.css file
.title_container .breadcrumb { display: none !important; }
and it did work fine. Which code is not being applied?
Please note that following code is only being applied on screens smaller than 767px
@media only screen and (max-width: 767px) { .responsive .logo { display: none !important; } /* div .main_color .tabcontainer .active_tab_content { background-color: #0694D2; } */ div .main_color .tabcontainer .active_tab { background-color: #EF7F1B; color: white;} /* START – remove arrows to previous and next gallery */ #top .avia-post-nav { display: none; } /* END */ /* start – position and thickness line under main menu */ .avia-menu-fx { bottom: 10px; } .avia-menu-fx { height: 3px; width:74%; left:13%; } /* END */ #advanced_menu_toggle, #advanced_menu_hide { margin-top: 10px; } #header_main { min-height: 82px; } }
Best regards,
YigitOctober 7, 2016 at 7:47 pm #696692Thank you for looking into this, sadly the css does not work.
One example is the following code:
/* start – position and thickness line under main menu */
.avia-menu-fx { bottom: 10px; }
.avia-menu-fx {
height: 3px;
width:74%;
left:13%;
}
/* END */Previously this would change the thickness of the line under the active menu item. But it does not work anymore. Did the css change in the uodate?
October 7, 2016 at 7:52 pm #696695Hi,
As i mentioned, that is because it is inside a media query and being applied on screens smaller than 767px.
Please change your code to following one@media only screen and (max-width: 767px) { .responsive .logo { display: none !important; } } /* div .main_color .tabcontainer .active_tab_content { background-color: #0694D2; } */ div .main_color .tabcontainer .active_tab { background-color: #EF7F1B; color: white;} /* START – remove arrows to previous and next gallery */ #top .avia-post-nav { display: none; } /* END */ /* start – position and thickness line under main menu */ .avia-menu-fx { bottom: 10px; } .avia-menu-fx { height: 3px; width:74%; left:13%; } /* END */ #advanced_menu_toggle, #advanced_menu_hide { margin-top: 10px; } #header_main { min-height: 82px; }
Best regards,
YigitOctober 7, 2016 at 8:10 pm #696705Thanks Yigit, I will give it a go. :)
October 7, 2016 at 8:11 pm #696707 -
AuthorPosts
- You must be logged in to reply to this topic.