V. 2.5.0 & 2.5.1 kills my Site/Layout!

Hello René,

Exactly the same happened to me, as I explain it here:
https://www.ads-software.com/support/topic/last-version-update/

Hoping that Hestia’s dev will answer asap to say that they fix all the bugs.

And by the way, there is a white space on the top of the site now (you’ve got the same).

Our MayDay need to be considered, hoping that those new last versions of Hestia has not be made by summer’s trainees.

As I had to do again my site with a new child theme, now I’m scared to update any new version that would be proposed online …

Let’s wait and see.

Same problem! I just responded to Scribelle’s post as well with the following:

I’m having problems too. Mostly it seems like the style.css for the parent theme isn’t being enqueued properly. When I add the enqueue code like so:

function hestia_style() {
	wp_enqueue_style( 'hestia-style', get_template_directory_uri() . '/style.css' );
}

add_action( ‘wp_enqueue_scripts’, ‘hestia_style’ );
It seems to fix the site for the most part, however, still a lot of things are weird looking or downright broken (top bar, for example, has sort of… gone missing?). Maybe other styles or theme files are not being enqueued properly either?

What the heck happened? I’ve used this theme on about 5 sites now and they all end up like this when I update, so I have to roll it back to the previous version.

Upon further inspection, I have determined that there’s an additional stylesheet that now needs to be enqueued in the child theme configuration. Here’s what I have:

Here’s the code I had in the child theme, autoconfigured by Child Theme Configurator:

<?php
// Exit if accessed directly
if ( !defined( 'ABSPATH' ) ) exit;

// BEGIN ENQUEUE PARENT ACTION
// AUTO GENERATED - Do not modify or remove comment markers above or below:

if ( !function_exists( 'chld_thm_cfg_parent_css' ) ):
    function chld_thm_cfg_parent_css() {
        wp_enqueue_style( 'chld_thm_cfg_parent', trailingslashit( get_template_directory_uri() ) . 'style.css', array( 'bootstrap','hestia-font-sizes','font-awesome' ) );
    }
endif;
add_action( 'wp_enqueue_scripts', 'chld_thm_cfg_parent_css', 10 );

If I replace this with the Hestia new child theme markup, almost everything is fixed (with exception to the missing Very Top Bar):

<?php
if ( !defined( 'ABSPATH' ) ) exit;

if ( !function_exists( 'hestia_child_parent_css' ) ):
    function hestia_child_parent_css() {
        wp_enqueue_style( 'hestia_child_parent', trailingslashit( get_template_directory_uri() ) . 'style.css', array( 'bootstrap' ) );
  if( is_rtl() ) {
    wp_enqueue_style( 'hestia_child_parent_rtl', trailingslashit( get_template_directory_uri() ) . 'style-rtl.css', array( 'bootstrap' ) );
  }

    }
endif;
add_action( 'wp_enqueue_scripts', 'hestia_child_parent_css', 10 );

/**
 * Import options from the parent theme
 *
 * @since 1.0.0
 */
function hestia_child_get_parent_options() {
  $hestia_mods = get_option( 'theme_mods_hestia' );
  if ( ! empty( $hestia_mods ) ) {
    foreach ( $hestia_mods as $hestia_mod_k => $hestia_mod_v ) {
      set_theme_mod( $hestia_mod_k, $hestia_mod_v );
    }
  }
}
add_action( 'after_switch_theme', 'hestia_child_get_parent_options' );

function accordion() {
  wp_enqueue_script('accordion', get_stylesheet_directory_uri() . '/jquery.accordion.js', array('jquery'));
  wp_enqueue_script('accordion', get_stylesheet_directory_uri() . '/accordion.js', array('jquery'));

}
add_action ('wp_enqueue_scripts', 'accordion');

I have also found that deleting my header.php in my child theme restores the Very Top Bar, so there is likely a conflict between the parent and child theme in this version.

• This reply was modified 5 years, 2 months ago by the9mm.