Theme issues

Hi @cristian-ungureanu,

Hosting provider:
https://www.nazwa.pl/

Here is a list of plugins that I use:
Contact Form 7
Cookie Notice & Compliance dla RODO / CCPA
Lightbox for Gallery & Image Block
UpdraftPlus
W3 Total Cache
WP-Optimize – Clean, Compress, Cache
XML Sitemap Generator for Google
Yoast SEO

Additional CSS code:
/* Google reCAPTCHA */
.grecaptcha-badge {
visibility: hidden;
}

Here is the code from footer.php:

<?php
/**
 * The template for displaying the footer
 *
 * Contains the closing of the "wrapper" div and all content after.
 *
 * @package Neve
 * @since   1.0.0
 */

/**
 * Executes actions before main tag is closed.
 *
 * @since 1.0.4
 */
do_action( 'neve_before_primary_end' ); ?>

</main><!--/.neve-main-->

<?php

/**
 * Executes actions after main tag is closed.
 *
 * @since 1.0.4
 */
do_action( 'neve_after_primary' );

/**
 * Filters the content parts.
 *
 * @since 1.0.9
 *
 * @param bool   $status Whether the component should be displayed or not.
 * @param string $context The context name.
 */
if ( apply_filters( 'neve_filter_toggle_content_parts', true, 'footer' ) === true ) {

	/**
	 * Executes actions before the footer was rendered.
	 *
	 * @since 1.0.0
	 */
	do_action( 'neve_before_footer_hook' );

	/**
	 * Executes the rendering function for the footer.
	 *
	 * @since 1.0.0
	 */
	do_action( 'neve_do_footer' );

	/**
	 * Executes actions after the footer was rendered.
	 *
	 * @since 1.0.0
	 */
	do_action( 'neve_after_footer_hook' );
}
?>

</div><!--/.wrapper-->
<?php

wp_footer();

/**
 * Executes actions before the body tag is closed.
 *
 * @since 2.11
 */
do_action( 'neve_body_end_before' );

?>
</body>

</html>

Thanks.

• This reply was modified 2 years, 10 months ago by gimmest62.
• This reply was modified 2 years, 10 months ago by Steven Stern (sterndata).

Hi @gimmest62,

Thanks for providing the details we’ve asked for! We have replied to you in the conversation you opened directly on our site, but I’ll leave the explanation for this issue here for other users to see as well.

We did some debugging and we found out that the hosting company has some optimization mechanism that interferes with how the theme is developed. What they are doing is this: any inline-style added is transformed to lowercase. So in Neve we are defining CSS variables like this: –fontSize:30px;. Before the website renders, the –fontSize variable is transformed to –fontsize. According to the web specifications, the CSS variables are case sensitive and that means they can be defined in snake case.
We contacted your hosting company and told them about the issue. We will also do some changes to the theme transforming everything into a lowercase format so things like this will never happen again.

It would be great if you could mark this thread as resolved. Thank you for helping us figure this out!

Hi @luciamarinescu,

Thank you very much for your help.
I hope this will resolve the issue.
I will mark this thread as resolved as soon as the fix is released ??

Thanks.

Hi all,

Stefan (Support Engineer) from ThemeIsle found and provided me a solution to my issue.
Here is the cause and the fix:

This is an issue caused by mod_pagespeed it changing the CSS variables name, therefore the style breaks. The solution is to disable rewrite_css from .htaccess file on servers that use mod_pagespeed. The following line needs to be added to the file.

ModPagespeedDisableFilters rewrite_css

Thanks.