This topic has 5 replies, 2 voices, and was last updated 9 years, 9 months ago ago by Eva Kemp
Hi guys,
Just a quick question.
In the release notes I’ve just seen “IMPROVED : Menu on screens 992 – 1200px”
is there an easy way I can set the mobile ‘hamburger’ icon to appear up to 1200px as it did previously? (As a feature suggestion, that breakpoint would be a good configuration option.)
Also, is there any reason why the standard WP child theme method of using a style.css in the child theme folder, has been broken/disabled in favour of using a custom.css in the default Royal theme folder?
I’ve got it working now, after reading another ticket, just wondered the reasons behind the change?!?!
Hello,
Please try to add this code in custom.css file:
.navbar #st-trigger-effects {
display: block;
}
style.css of child theme is working fine. You need create it as described in the documentation:
http://codex.wordpress.org/Child_Themes
Thank you.
Regards,
Eva Kemp.
Morning Eva,
thanks for the quick reply.
On the child-theme issue. I’m sorry, but it doesn’t work as it did. I had the site I’m working on functioning correctly and working with the child-theme css fine. Then I upgraded Royal to 1.6.1 and the styles in the child theme were then ignored.
https://www.8theme.com/topic/my-child-css-not-working-after-update/
https://www.8theme.com/topic/custom-css-in-child-theme-not-being-read-since-recent-update/
https://www.8theme.com/topic/custom-css-in-child-theme-not-being-read-since-recent-update/
the above thread seem to agree!
No matter, I’ve adjusted my setup and am now working with the custom.css as recommended in one of those threads above.
As for the top-menu change- sorry, the solution you provided didn’t work I’m afraid Eva. 8(
Please see the private info for URL and FTP details.
actually Eva,
now I know how to enable the hamburger, I can probably do it myself.
Consider this closed unless I come back with a headache! 8)
Cheers
Hello,
You’re welcome.
Regards,
Eva Kemp.
The issue related to '‘1.6.1 top menu’' has been successfully resolved, and the topic is now closed for further responses