Dave_S

Also happens with the latest version of the “MCE Table Buttons” plugin. According to the release notes TinyMCE has been updated from 4.1.x to 4.7.11. Maybe that’s what causes the problem.

Hi Cafeine,

if you’re using Hueman 3.3.8 add this code to parts/header-nav-main.php right before </nav><!--/#nav-header-->:

<div class="container">
      <div class="container-inner">
          <div class="toggle-search"><i class="fa fa-search"></i></div>
          <div class="search-expand">
            <div class="search-expand-inner">
              <?php get_search_form(); ?>
           </div>
          </div>
      </div><!--/.container-inner-->
 </div><!--/.container-->

Also make sure you set the option “Topbar and header menus, logo centered” in the Customizer: Header Design > Header design: colors, mobile settings.

Hi plimfec,

Thanks for the hint. I didn’t expect that this option brings back the old-style menu. It more suggests that it shows both menus and centers the logo. It’s a bit misleading title I guess.

Cheers,

Dave

Hi again,

I fixed the problem myself by adding the search-code to header-nav-mobile.php and tweaking a bit with the CSS:

.mobile-title-logo-in-header .site-title {
        left: 65px!important;
}

As this works for me, I mark the topic as fixed.

Ich habe inzwischen den Fix aus GitHub angewandt (autocomplete=”off”), das Problem besteht aber leider weiterhin.

Vgl. https://github.com/pluginkollektiv/antispam-bee/pull/137

This got solved. The problem was with W3TC.

Hi Phil,

Thanks for your fast response. I investigated a bit further and apparently neither Yoast nor Wordfence are the culprit but W3 Total Cache.

Apparently W3TC suddenly started to throw random php warnings when database caching is enabled. As these only appear randomly and not on all AMP pages it looked like the problem was Yoast together with Wordfence (as it randomly worked fine when switching back to Yoast 4.4).

So I mark that as resolved so far. Thanks!

Thanks Nicolas, works fine again!

As this bug has been reported over half a year ago but is still there in the latest release today, here is how I fix it in sharrre-template.php:

Replace

if( ! ( $window.width() > 480) )
          return;

with

if( ! ( $window.width() > 720) )
          return;

Github issues:
https://github.com/presscustomizr/hueman-addons/issues/16
https://github.com/presscustomizr/hueman-addons/issues/15

Because I’m using a customized AMP template. If I keep them enabled i.e. the table styles don’t work as nicely on AMP as on the desktop/mobile version. I’d have to make changes to all my articles again as I can’t override the inline styles with !important in the default CSS for AMP.

@bdbrown: As you said that also makes the desktop share bar sticky. I think it’s a clear bug as it was working fine before (non-sticky for desktop, sticky for mobile).

Hi bdbrown,

the problem is not that it gets converted from vertical to horizontal position (which is fine and as you mentioned that’s how it was before), the problem is that it keeps moving when you scroll the window now.

That shouldn’t happen and the share bar should stay below the content all the time when in horizontal position.

Also there was nothing in the change logs about these changes (especially that the share bar is now hidden by default for < 480).

Update: I just checked and it also happens on the hueman demo site (so it’s nothing that’s only about my site):

https://demo-hueman.presscustomizr.com/2013/10/28/take-a-deep-breath-and-just-be/

Just resize the browser window to < 719 and the share bar will now move up and down when you scroll and cover parts of the content. Happens in Safari and Chrome.

Cheers,

David

I can confirm that the share buttons are also gone from my site when using mobile devices since I upgraded to the latest version of Hueman (3.1.6). Were there some CSS changes maybe?

Actually what’s worse: The share bar is now floating horizontally up and down when resizing the browser window. Happens only for “@media only screen and (max-width: 719px)”.

Ok, just tracked it down after some research.

Apparently spaces or line breaks are not allowed in the boilerplate code. They got inserted to my site by W3 Total Cache plugin when Inline CSS minify was enabled. After disabling it, the code now validates just fine.

Check if you use the same size of the image for example for the featured image and the actual image in the article.

i.e. if you choose image.jpg for the featured image but image-1024-600.jpg for the actual image in the article then the plugin doesn’t sort it out correctly. If you use the same image sizes then it works fine.

Maybe the plugin can be enhanced that different image sizes of the same image can be detected. That way it would be fully compliant to the IA guidelines.