Footer do not show on Google Chrome

Could you post some part of code? I’ll try to help you

It’s seems working for me:

<?php
/**
 *      (c) www.devn.co
 */
?>

        </div><!-- #main -->
        <?php wp_footer(); ?>
</body>
</html>
~                                                                                                                                                                                                  
~                      

It was not that I did that part, because I take care of the hosting that the site stays, but I end up being responsible for some bugs that appear HAHA.

The site uses Theme aaika and this code I took from the “footer.php” file, which is in wp-content / themes / aaika / is that right?

Thanks!

I see the same issue in Chrome. It appears this CSS rule is the cause:

.effHidden {
    visibility: hidden; 
}

Line 202 of the theme’s style.css. I believe it’s supposed to transition to visible after page load, but the transition trigger fails to execute. Transitions below the fold are kind of useless IMO. You could disable it by placing the same rule in the Additional CSS area of the customizer, setting visibility to visible. It’s inadvisable to change the file itself because theme updates will wipe out any such changes.

The proper fix would be to solve why the transition trigger is failing. The only error in console is a Google font failed to load. I think some of Google’s servers are currently experiencing difficulty, so it’s likely a temporary problem. All the same, verify the font is correctly specified, or rely on the local client having the font in question (Arial). It’s not unreasonable in this case. It can fallback to generic sans-serif in the few cases where Arial is not available. I’m not sure font failure would cause the trigger to fail anyway. I’ve no idea otherwise why it’s not being triggered.

Thanks for the answer.

So I did what you said, but it did not work. As you mentioned it may be the version of Chrome that is in trouble because the user lai32290 said he succeeded.

I’m using a Chromebook, which is using version 63 of Google Chrome, a Beta. I ran a test on a Windows machine using Google Chrome 62 and it appeared normally.

It really seems like a temporary problem with Chrome.

Thank you guys.