Logo image sizing issue after updating to 4.8.6.4 and 4.8.6.5

Hi Yigit, thanks for following up on this thread. I assume you mean this change will be included in a version subsequent to the newly released 4.8.6.5? Do you have any idea when this is going to occur? It is somewhat disappointing needing to go through over 20 web site updates only to need to do it again in under a week.

Considering most web traffic is at almost 90% nowadays, mobile rending is mission critical for a lot of us and I think many Enfold users have chosen custom header heights.

Hi, do we know when 4.8.6.6 is coming out? I would prefer to wait for that update to update my theme vs. working with interim code.

Thanks!
Rob

I’ll follow up too on asking when 4.8.6.6 is expected. Kindly supply a date.

As long as none of the other bugs have negatively affected your site – Instead of rolling back, just add the following to quick CSS. Its quicker.

I have upgraded a few sites to 4.8.6.5 and have not noticed any problems other than this so it depends which Enfold functions you use.

@media only screen and (min-width: 768px) and (max-width: 989px) {
.responsive .logo a {
height:90px !important;
}
}

@media only screen and (max-width: 767px) {
.responsive .logo a {
height:80px !important;
}
}

Take a look at the release schedule. I dont think the team have plans for a 4.8.6.6.

Looks like we are going straight to 4.8.7
https://kriesi.at/support/topic/enfold-upcoming-fixes/

There are a number of fixes being implelemented I assume that in the background the rest of the fixes and tweaks are almost complete – Hence no 4.8.6.6

I just hope that in the meantime people who have just purchased Enfold are not upset by the current bugs.

Hi Yigit, I am not using the SVG support plugin. I’m wondering if some of the css files were minified and somehow cached. Also there’s some custom programming on my header… see header.php in private content. I also have some custom in functions.php:

* Rob adding custom code from Enfold support to add widget area to header.
*/
add_action( ‘ava_main_header’, ‘enfold_customization_header_widget_area’ );
function enfold_customization_header_widget_area() {
dynamic_sidebar( ‘header’ );
}

I also included style.css as there’s a lot of header customization there. I was thinking if the next release breaks my header then I would open a support ticket and provide login credentials. It would be great however if you can scan the code I have uploaded to see if there’s a problem with the code vs. where Enfold is going with the header.

Thanks!!
Rob

Yes @Yigit of course. However, what is the harm in pushing an update with the one change to address the mistake immediately to solve everyone’s problem instantly? Perhaps it cost Kriesi more money for every update you push to Themeforest? DO they charge per update?