Latest update has broken my header

How the banner is supposed to look - Version: 6.1.5

How it looks with the update - Version: 6.1.6

My live site now has version 6.1.5 and my staging site has the broken update 6.1.6 - see secure note for details

Hi @etah,

In your staging site, HTTP Authentication has been implemented and the given credentials do not work with that. I would suggest you share the credentials to access the site.

Thanks

The credentials are for the front end of the staging site. User name and password is correct, force https is on so you may have to enter the credentials twice. I have tested and these credentials work.
If you need backend access to the site let me know. But I was hoping you could identify the problem without it as nothing changed from my end.

Hi @etah,

This time the credentials worked to pass the HTTP authentication, but we need to check the settings made in the Header through the WordPress admin dashboard. Can you please provide login credentials for your site in a secure note to examine it further, including:

– WordPress Site URL & Login URL
– WordPress Admin username/password

To create a secure note, click the key icon underneath any of your posts.
secure-note

NOTE: I have already tried to access the common URL for the WordPress admin, but that shows 404.

Thanks

@etah

Same thing is happening to me. Have you figured it out?

I noticed another thing happening to the header after latest update. On mobile device the menu toggle triggers the links that are in the menu modal “underneath it”. Please check this behaviour here: https://gok.goleszow.pl/kultura

I’m looking into this and will hotfix with other sticky bar issues. Pretty sure it’s because it’s height is set to auto and the space is not registered correctly. We’ve had some other issues with auto so hopefully we can just fix them all now.

There’s a hotfix for sticky bars out now (6.1.7). The auto problem was a problem for a while, you’ll notice on your sites before 6.1.6, if you moved the scroll bar a hair this exact problem would happen if you were using auto. Since the position determines itself at the top properly now this issue is more apparent. So you shouldn’t have this issue anymore, let me know if you do though and have a great weekend.

Yes, that has fixed it for me. Thanks

Hey @Etah,

You are most welcome. We are glad the latest version Pro 6.1.7 has fixed the issue. We really appreciate for letting us know.

Cheers.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.