Tons of problems after I updated Theme to 3.3.9

  • Nicolas, this is the worse update ever! I don’t even know where to start, I have so many problems.

    The vast majority is related to the fact that my HUEMAN was (or is) heavily customised, it’s light coloured rather than dark (as the original). Now my custom css is being ignored, my css code comes up always second in Firebug!

    When I initially opened my page I was shocked (I still am)!
    The top, under the heaeder, has a dark background, mine is light beige. The menu has a dark background, but with my styling of dark grey, almost black text on it – so you can’t see anything clearly.

    Weirdest thing: I added an !important to some of my color specifications in my custom css – now it’s kind of alright in Firefox 52.0 – but still completely messy in Chrome and IE (nothing is fixed).
    My website is dare2go.com and it should look like this:
    https://www.dropbox.com/s/munsjccebdb990n/dare2go-50%25.jpg?dl=0

    Throughout the pages there are the weirdest colour changes:
    on the home page the post titles (links) are now blue
    the background of comment bubble is now green (should be orange)
    the category link (under featured image) is also blue, should be #333
    the background of the ‘Follow’ in the sidebar is blue, should be orange
    …and so on (there are dozens, if not hundred flaws).

    How do I get my custom css (which is part of my child theme) to be globally recognised – so that things are back to normal?

    —————————————————–

    Next issue:
    some widgets do not display in the sidebar – sometimes!
    Like on the our front page we have a text widget ‘About Us’ (Hello & Welcome) and a Facebook widget (Jetpack) – on individual posts these don’t show anymore! I haven’t touched any ‘Visibility’ settings for any widgets. So what’s going wrong there?

    Worse for me:
    1. we have travel blog and are full-time on the road, currently in the Amazon province of Peru. I rely solely on mobile data (very patchy and expensive here) and solar power (which we don’t get enough of because we are in the cloud forest). I don’t know when and how to find space to deal with this any further!
    2. I just paid a developer to implement a new front-page for our site (not yet active because of reason 1, above) – this was working fine and is now similarly messed up since the theme update.

    I want my website back the way is used to be! Desperate!

Viewing 7 replies - 1 through 7 (of 7 total)

  • It’s the dynamic styles option in the customizer doing some of the color changes, you can’t disable it anymore. Why? I don’t know.

    Theme Author presscustomizr

    (@nikeo)

    Hi @sho-down, the dynamic style won’t print custom style when colors are set to default in the customizer.
    This will fix a part of your problem.
    If the update introduces too many problems and you don’t have the ability to fix them right now, I would suggest to roll back to the previous version of the theme.
    You can download the previous version from the Hueman github page, uninstall the current one and install the previous version manually on your website.
    I hope this wil help ??

    @nikeo I’ve set the primary and secondary colors back to default but it still prints the inline css and overwrites my A link colors:
    screenshot

    This is all the CSS being inlined:

    <style type="text/css" id="hu-dynamic-style">/* Dynamic CSS: For no styles in head, copy and put the css below in your child theme's style.css, disable dynamic styles */body { font-size:1.00rem; }@media only screen and (min-width: 720px) {
        .nav > li { font-size:1.00rem; }
      }.sidebar .widget { padding-left: 20px; padding-right: 20px; padding-top: 20px; }::selection { background-color: #3b8dbd; }
::-moz-selection { background-color: #3b8dbd; }a,.themeform label .required,#flexslider-featured .flex-direction-nav .flex-next:hover,#flexslider-featured .flex-direction-nav .flex-prev:hover,.post-hover:hover .post-title a,.post-title a:hover,.s1 .post-nav li a:hover i,.content .post-nav li a:hover i,.post-related a:hover,.s1 .widget_rss ul li a,#footer .widget_rss ul li a,.s1 .widget_calendar a,#footer .widget_calendar a,.s1 .alx-tab .tab-item-category a,.s1 .alx-posts .post-item-category a,.s1 .alx-tab li:hover .tab-item-title a,.s1 .alx-tab li:hover .tab-item-comment a,.s1 .alx-posts li:hover .post-item-title a,#footer .alx-tab .tab-item-category a,#footer .alx-posts .post-item-category a,#footer .alx-tab li:hover .tab-item-title a,#footer .alx-tab li:hover .tab-item-comment a,#footer .alx-posts li:hover .post-item-title a,.comment-tabs li.active a,.comment-awaiting-moderation,.child-menu a:hover,.child-menu .current_page_item > a,.wp-pagenavi a{ color: #3b8dbd; }.themeform input[type="submit"],.themeform button[type="submit"],.s1 .sidebar-top,.s1 .sidebar-toggle,#flexslider-featured .flex-control-nav li a.flex-active,.post-tags a:hover,.s1 .widget_calendar caption,#footer .widget_calendar caption,.author-bio .bio-avatar:after,.commentlist li.bypostauthor > .comment-body:after,.commentlist li.comment-author-admin > .comment-body:after{ background-color: #3b8dbd; }.post-format .format-container { border-color: #3b8dbd; }.s1 .alx-tabs-nav li.active a,#footer .alx-tabs-nav li.active a,.comment-tabs li.active a,.wp-pagenavi a:hover,.wp-pagenavi a:active,.wp-pagenavi span.current{ border-bottom-color: #3b8dbd!important; }.s2 .post-nav li a:hover i,
.s2 .widget_rss ul li a,
.s2 .widget_calendar a,
.s2 .alx-tab .tab-item-category a,
.s2 .alx-posts .post-item-category a,
.s2 .alx-tab li:hover .tab-item-title a,
.s2 .alx-tab li:hover .tab-item-comment a,
.s2 .alx-posts li:hover .post-item-title a { color: #82b965; }
.s2 .sidebar-top,.s2 .sidebar-toggle,.post-comments,.jp-play-bar,.jp-volume-bar-value,.s2 .widget_calendar caption{ background-color: #82b965; }.s2 .alx-tabs-nav li.active a { border-bottom-color: #82b965; }
.post-comments span:before { border-right-color: #82b965; }
      .search-expand,
#nav-topbar.nav-container { background-color: #26272b; background-color: rgba(38,39,43,0.8) }
@media only screen and (min-width: 720px) {
  #nav-topbar .nav ul { background-color: #26272b; }
}
        #header { background-color: #26272b; }
@media only screen and (min-width: 720px) {
  #nav-header .nav ul { background-color: #26272b; }
}
        #header .nav-container.mobile-sticky { background-color: #26272b; }#nav-header.nav-container { background-color: #26272b; }
@media only screen and (min-width: 720px) {
  #nav-header .nav ul { background-color: #26272b; }
}
        #footer-bottom { background-color: #131315; }.site-title a img { max-height: 130px; }body { background-color: #eaeaea; }</style>
    • This reply was modified 7 years, 7 months ago by Sho-Down.
    Thread Starter webbeetle

    (@webbeetle)

    [It’s a BIG nightmare for me right now – since we’re anyhow way behind with ‘work’ (like blog updates, sorting/naming photos, keeping up with social media sharing, etc.) due to lack of power to use our computers. I mentioned our situation above. Now I face this trouble! I could have easily published a new blog post (write text, prepare photos, publish) in less time than I wasted on this crap! The stress is going so far that yesterday I had an unnecessary fight with my wife… All we needed!]

    So, today I wasted several hours and expensive mobile bandwidth going through ‘WP Customizer’ to change colours – some things are now fixed, some still don’t work!

    [I actually don’t even like to use the WP Customizer Tool – it’s another of these new WordPress features I could have done without. For me, relying only on expensive mobile data, it’s nothing but a waste of money. But that’s with all changes to WordPress: only fancy optical gadgets which to me are absolutely useless and make it rather more difficult to use WP. Ask my wife how often she wastes time {or asks me} looking for some function links which now only show up when you hover your mouse in the right spot. Who needs such crap?]

    And new problems are showing:

    The main issue now is the TOP MENU!

    1. the Menu has lost its stickiness! That was one feature which really made me chose HUEMAN. Now it’s not working anymore!

    2. I set the Menu background back to white. But now I lost my styling, which included a thin coloured bottom border line and a gentle drop shadow. The bottom border only shows correctly if you hover your mouse over the menu.

    3. But – and now it gets worse! – when you scroll a little down the page the Menu reverts back to black background! I have black text for Menu links – which one can’t read anymore!

    4. the Menu shows exactly the same behaviour (I should say ‘Bugs’) on Mobile!

    5. the Mobile Menu has lost its ‘Search’ button!

    I have tested this in both, Firefox 52 and Chrome 45.

    I have taken a number of screen captures, which show the different behaviours through the scrolling stages – all in one file (50% size):
    https://www.dropbox.com/s/77v44e7psgymvac/menu-not-sticky.jpg?dl=0

    The sticky MENU is important to me! I don’t give a toss about a sticky sidebar (as I was ready to dump it all together – Mobile visitors never get to see it, and they now make 60% of our readership)!

    But since I’m at the sidebar:
    The issue, that some widgets are NOT showing on ‘Post’ pages remains! These are 2, Hello & Welcome and the Jetpack Facebook widget. In the order of my widgets these are #1 and #3, widget #2 (Google Translate) is always showing for some weird reason…

    https://www.dropbox.com/s/dc43nq102o2tr1p/widgets.JPG?dl=0

    Question: above somebody suggested that setting colours to ‘Default’, instead of my custom colours, might rescue my custom css. Will this work with the bottom border of the top navigation?

    Nicolas, I was ready to wind back to the previous version 3.3.7, which luckily I have sitting on my local harddisk. But then: where would it leave me should there be an urgent security update of the theme?

    [Sorry about my ranting. I’m still stressed by this and angry! So unnecessary this trouble – and at the wrong time all together…]

    Thread Starter webbeetle

    (@webbeetle)

    Oh God – the longer I look the more problems I discover!

    Now I just found an issue with the body font!!

    In our latest post most of the text is in ‘Roboto’ – the standard version which I use since day 1 of our WordPress blog! Yet the last paragraph changed to ‘Roboto Condensed’ – one of the ones in your drop-down list. To make it clear: this text is still part of the same post, all created in the WordPress editor.

    See capture:
    https://www.dropbox.com/s/z4xno30r0k6wlwg/font-change-within-post.jpg?dl=0

    I also noticed that ‘Roboto Condensed’ is now appearing in some text widgets and other areas of my pages. I want the standard ‘Roboto’ for all! More than 2 fonts on any page is ugly.

    I had no choice but chose that one – but I don’t want it! There’s no option to set ‘default’!

    I had spent considerable time to pick the right font for our blog. I wanted something which is easy to read on Mobile, doesn’t create long lines of text on desktop screen (runs reasonably wide), and, most importantly, is sans-serif and without the curly hooks on the underlength of the g, like so many sans-serif fonts have (eg Open Sans, the font used on this page).

    I have no idea how to fix this!
    Other than you giving an option for ‘default’ font or no font in the WordPress Customizer.

    ps: this is a capture from SWIron (Chrome browser) – do you notice once again the dark menu background (instead of white)?

    And you can (not) see the missing 2 widgets – mentioned above! Please compare with the other captures of the ‘home’ page.

    • This reply was modified 7 years, 7 months ago by webbeetle.

    Set the font in Customizer to the Trillium self-hosted font or whatever it’s called, that’s the default. That’s how I fixed my font. You set it to that and it won’t load any google fonts for you.

    Thread Starter webbeetle

    (@webbeetle)

    @sho-down: but I use Google Fonts, only that mine are specified in the css.

    But I’ll give it a try. ??

    EDIT: yes, this fixed one problem! Thank you!

    Now only TWO MAJOR ones remain:
    1. navigation not sticky (and wrong colour)
    2. missing sidebar widgets

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Tons of problems after I updated Theme to 3.3.9’ is closed to new replies.