Forum Replies Created
-
Posts
-
Hi Ismael, thanks for following up. This is very unnerving and it needs to be solved.
The override css both you and Rikard suggested to use was already entered in the Quick CSS so it should have been there already. Was it there already or not? If not there is a huge problem where quick css is not flowing to the theme. If is was already and you just used developer tools to view the phone screen, we also have a problem – because I do not see what you saw.
In what Enfold file exactly is the following code you said controls visibility? I am going to remove it and see what we get.
.responsive #top .avia-slideshow-controls a {
display: none;
}Who decided it was a good idea to hardcode this in? The user should decide this. A control would have made more sense.
Hi Rikard, as with several of the US-based sites I manage, there is no need whatsoever to to allow non-US based IPs access to the backend. It is my understanding that most of the Kriesi team are located outside the US. Do you have a US-based VPN from which you can connect? Otherwise, Wordfence will immediately block you. I won’t disable WF without client consent and that would take up even more time.
If you were thinking compression/minifying is at fault, I have gone that route already. None of the sites I manage use the built-in Enfold compression for JS or CSS – a general rule for me. We do use SG Optimizer and I have already deactivated minifying and compression, cleared server cache – and it had no effect on mobile. This was even after adding the quick CSS you sent at first.
But I did notice something:
1. https://mommymakeovercenterofny.com/ is using 4.8.6.3 and has a child header based on the 4.8.6.3 header. – no mobile easy slider controls visible.
2. https://swedesboroday.com/ is using 4.8.6.5 and while the child folder has a custom functions.php file, there is no child header present – no mobile easy slider controls visible. I also added your quick css here.
3. https://mommymakeovercenterofny.com/ is using 4.8.6.3 and has a child header still present from a version prior to 4.8.6.3 (I did not make any changes yet) – mobile easy slider controls are visible.
4. https://southerndental.org/ is using 4.8.6.5 and while the child folder has a custom functions.php file, there is no child header present – mobile easy slider controls are visible. Note: we do not us SG Optimizer on this site.This is getting a tad complicated – need to find a solution for the mobile easy slider controls. I have several other client sites which must have the slider controls visible for mobile since that is where ~ 90% of web traffic is coming from. The issue only surfaced after updating to 4.8.6.3 and changing any child header to a 4.8.6.3 version. As I noted above, we have a bunch of sites on 4.8.6.3 but have not yet updated the child header and the mobile slider controls ARE there. Stranger yet is the dental site I mentioned, which is on 4.8.6.5 and no SG Optimizer, looks fine.
I had also deactivated SG Optimizer on https://swedesboroday.com/, cleared server and browser cache and still no controls on mobile easy slider. I think this shows it is not the plugin at issue.
Hi Rikard, thanks for the code but it does not seem to work. I have tried it on 2 separate sites and no luck.
FWIW, on the site in my first post I am running 4.8.6.3 using a child theme and have header.php from 4.8.6.3 modified with some customizations. On another site, https://swedesboroday.com/, I just updated to 4.8.6.5, replaced layout.css with the corrected one and have no header.php in my child theme (no overrides necessary). Same result on both – no minimal white slider controls any longer on anything below 768px.
Seems to me this cropped up on 4.8.6.3. Can’t see why the quick CSS entry would not work.
Any idea how to fix?
FWIW, bkatzdesign I simply closed the php script command and then entered my Google knowledgebase code below it in my child header. The bolded type is what I added. I am not a coder but I had been told in the past in certain circumstances php scripts will run with just an open i.e. <?php and don’t need a close unless a non-php item follows. This was my case. The knowledgegraph code is not php.
<?php
if( isset( $avia_config[‘temp_logo_container’] ) )
{
echo $avia_config[‘temp_logo_container’];
}
do_action( ‘ava_after_main_container’ );
?>If your added code is not php, this should work without issue and not create a 2x header. If it is php, Rikard can likely help.
I never got any answer from anyone on my reply #1323820 from support to confirm so I tried it and it worked.The following is the entire contents of my Quick CSS area as per your directions – it is there. Don’t know why you don’t see it. Try clearing cache.
@media only screen and (max-width: 767px) {
.responsive #top .av_header_transparency.av_alternate_logo_active .logo a>img,
.responsive #top .av_header_transparency.av_alternate_logo_active .logo a>svg {
opacity: 1;
max-height: 80px !important;
}.responsive #top #header_main>.container .main_menu .av-main-nav>li>a {
height: 80px !important;
line-height: 80px !important;
}}
——-
The screenshot you linked is certainly not current, that was from before I added the code.
And my last issue was not whether the code worked – it did from what I can see – it is WHY I see a difference in Chrome mobile between a standard window and incognito – there should be no difference.
Now, in mobile Chrome, standard window, I still don’t see the blue title background under the logo. But, in a mobile Chrome incognito window, it shows up. ==> Why the difference?
In mobile Safari, all is good except for the fact that when you swipe up the logo resizes large again. Yes, it moves out of view during the swipe up but it only stays small in the page loaded position
This issue is STILL present after updating to 4.8.6.5. There should be no difference in viewing this site in a standard window or an incognito window. Also when swiping the page upwards, the logo attempts to resize itself larger for a split second.
Still wiggy.
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 Ismael, thanks for the additional code above. I added the snippet in reply #1323837 to your media query snippet in reply #1323734 and the logo is resized to a reasonable size when the page loads on mobile. BUT, it is still wonky on actual mobile browsers. This is precisely why I included real mobile browser screenshots in my reply #1323784. I am pretty sure you were on a desktop when you checked after the fix you generated – it is not the same on a real phone.
Now, in mobile Chrome, standard window, I still don’t see the blue title background under the logo. But, in a mobile Chrome incognito window, it shows up. ==> Why the difference?
In mobile Safari, all is good except for the fact that when you swipe up the logo resizes large again. Yes, it moves out of view during the swipe up but it only stays small in the page loaded position.
I have also always simply resized a desktop window to see where media queries would make tablet and phone layouts look – but they are not the real thing. Kindly try the site out on a real phone and advise on now to put this issue to bed once and for all. I have numerous sites to update and am not even remotely close to confident in the huge changes made in 4.8.6.3 and 4.8.6.4.
We have some Google Knowledgegraph code to insert in our header.
Pre 4.8.6.3 the header closed with:
<?phpif(isset($avia_config[‘temp_logo_container’])) echo $avia_config[‘temp_logo_container’];
do_action(‘ava_after_main_container’);?>
4.8.6.3 header closes with:
<?phpif( isset( $avia_config[‘temp_logo_container’] ) )
{
echo $avia_config[‘temp_logo_container’];
}do_action( ‘ava_after_main_container’ );
Notice there is no closing php ?> there? Should I just add it before I paste in my code? Or is it going to break php execution due to ?> being elsewhere?
Hi Ismael, the code sent was entered into my Quick CSS and it had no effect whatsoever. Again, I am not using a child and the entry you gave me was the only thing in Quick CSS. Not sure if you’re understanding what I am seeing so here are 2 more screenshots from actual mobile. iPhone SE2 – both Safari and Chrome has exactly the same results. There should not be any difference between viewing the site in a standard window or a private/incognito window – but there is.
Safari/Chrome incognito/private
Safari/Chrome standard
If you view the site on desktop you’ll see the major difference. I have numerous other sites to update so I don’t want this happening everywhere after spending numerous hours getting things to look perfect on mobile and desktop.
Rikard commented in my post on:
Please read it. Is this a known issue and should I revert back to 4.8.6.3?
I’ve already replaced the file:
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_8_6_4/framework/class-svg-images.phpThis dealt with svg images in the header and supposedly fixed non-svg images displaying properly.
Hi Yigit/Rikard. Chiming in here since my issue in https://kriesi.at/support/topic/mobile-layout-oddity/ is the same. Hope you’re okay with this.
I have the same issues and Enfold merge and compression is OFF.
Something must have gotten altered in the way the theme is handling mobile in the header. If you look at my post above, the details I provided will problem help a lot of folks. I cannot figure out how to get things to look right in mobile any longer. My site renders perfectly on desktop – mobile is the issue. And there IS a difference now between checking a site based on browser width (which I always used to do) and it actually being a mobile device. Did your folks put something in that was not there before?
The problem was not fixed with Gunther’s SVG file change. I updated again to 4.8.6.4 and swapped out his replacement php file. I am not sure why you said you could not inspect the site – I use Wordfence but there are no location blocks setup at all.
If you go to https://ready.mobi/ and run my url https://logancoedsoftball.com/ you will see exactly what the site should look like in all modes. BTW, I removed the bg graphic from smaller renderings below 768px since it would not work period. So, if you look at what ready.mobi delivers and the actual content on a real cell phone, they are quite different. On a real phone the logo in mobile is MUCH larger than it should be and pushes the mobile menu to the right so much you don’t even see the Facebook icon any longer. This also has nothing to do with anything child theme related since I am not using a child theme here.
I have numerous sites to manage and this was the first I tested on. There is definitely something wrong with the way logos are being downsized for mobile in the code.
Also, there should be no difference in what I see when I load the site in a standard mobile browser window vs. a private or incognito window. This is NOT the case. Elements are all loading in an incognito window and the logo is oversized. In a standard window, I am missing the blue color section backgrounds.
Hi Rikard, Gunther just chimed in on a similar issue on this matter at https://kriesi.at/support/topic/logo-missing-quick-fix/#post-1323606. Would this be the issue and it was not found until after you replied?
Hi Ismael, Gunther just chimed in on a similar issue on this matter at https://kriesi.at/support/topic/logo-missing-quick-fix/#post-1323606. Would this be the issue and it was not found until after you replied?
I use child thems on most sites but this latest update screwed all up no matter whether child or not. I commonly use a sticky header and the 4.8.6.4 update blurts out a much larger logo. Cleared server and browser cache, same thing.
I sw some reference to some header changes being done on 4.8.6.3 but have not yet looked into the details HOWEVER, it does not explain the logo bothing up on 4.8.6.4.
