There in the post Mike linked to – it was about bringing the #footer/#socket to full width.
If this is not your intention, but only the reordering of the DOM, then you can correct the css accordingly.

so disregard the css specified there and instead:

@media only screen and (min-width: 990px) {
  #footer, 
  #socket {
    width: calc(100% - 300px);
    left: 300px;
  }
}

@media only screen and (min-width: 768px) and (max-width: 989px) {
  #footer, 
  #socket {
    width: 73vw;
    left: 27%;
  }
}

for the rest of the code i had to see a pure installation of header left.
because i have a loto of settings for header on that installation that disturbs the settings here.
f.e.: the mobile header below 768px is fixed etc.

… see private content

just remove the portfolio from those snippets:

function avf_template_builder_content_postimage_mod($content = ""){
  if(  is_singular('post') && ( '1' != get_post_meta( get_the_ID(), '_avia_hide_featured_image', true ) ) )  {
        $featuredImage = get_the_post_thumbnail( $the_id, 'original' );
        $content = '<header class="entry-content-header"><div class="page-thumb">' .$featuredImage. '</div></header>' . $content ;
      }
  return $content;
}
add_filter('avf_template_builder_content', 'avf_template_builder_content_postimage_mod', 10, 1);

//image-sizes:  widget, square, featured, featured_large, extra_large, portfolio, portfolio_small, gallery, magazine, masonry, entry_with_sidebar, entry_without_sidebar, medium, large

function custom_post_featured_image_link( $image_link, array $current_post, $size ){
  if(  is_singular('post')  && ( '1' != get_post_meta( get_the_ID(), '_avia_hide_featured_image', true ) ) )  {
    $image_link = get_the_post_thumbnail( $current_post['the_id'], 'original' ); /**** or medium, square etc. ***/
  }
  return $image_link;  // echo $image_link;  if you want to get rid of link function
}
add_filter( 'avf_post_featured_image_link', 'custom_post_featured_image_link', 10, 3 );

i got an additional solution – even if you like to hide some special posts :
it limits the results to 5 posts – and excludes the post-id’s 68 and 55 but shows only published posts – and with no password

function avia_filter_ajax_search_results( $search_parameters ){
	$defaults = array('numberposts' => 5, 'post_type' => array( 'post', 'portfolio', 'page' ), 'post__not_in' => array(68,55), 'post_status' => 'publish', 'post_password' => '', 'suppress_filters' => false);
	$_REQUEST['s'] = apply_filters( 'get_search_query', $_REQUEST['s']);
	$search_parameters = array_merge( $defaults, $_REQUEST );
	return $search_parameters;
}
add_filter('avf_ajax_search_query', 'avia_filter_ajax_search_results', 10, 1);

by the way – would it be possible to limit not the whole results to 5 – but for each post_type ?

or you take – mikes snippet to redeclare these formats – but with setting of crop to false!
( but the solution above is more elegant, and also shows the full resolution )

function avf_customization_modify_thumb_size( $size ) {
      $size['entry_without_sidebar'] = array( 'width' => 845, 'height' => 9999 , 'crop' => false );
      $size['entry_with_sidebar'] = array( 'width' => 1210, 'height' => 9999 , 'crop' => false );
      return $size;
}
add_filter( 'avf_modify_thumb_size', 'avf_customization_modify_thumb_size', 10, 1 );

the limitation value is not the width value – so you got smaller images. This is as Mike mentioned for the new images only – but if you recalculate the thumbs even the older posts will have that new size (without cropping)

please do not redefine the images_sizes!
Just wait a little i test my solution first …

see post : https://kriesi.at/support/topic/full-image-on-single-post/#post-1471388

if you are in the edit mode of the page/post you can decide it on the right side inside the layout-box a drop-down:

place that code snippet to your child-theme functions.php:

function register_meta_elements($avf_builder_elements){
$avf_builder_elements[] = array(
  "slug"  => "layout",
  "name"  => __("Menu and Logo Position", 'avia_framework'),
  "desc"  => __("You can choose various different logo and main menu positions here", 'avia_framework'),
  "id"  => "header_layout",
  "type"  => "select",
  "std"   => "",
  "no_first"=>true,
  "subtype" => array( __('Logo left, Menu right', 'avia_framework')   =>'logo_left main_nav_header menu_right',
            __('Logo right, Menu Left', 'avia_framework') =>'logo_right main_nav_header menu_left',
            __('Logo left, Menu below', 'avia_framework')   =>'logo_left bottom_nav_header menu_left',
            __('Logo right, Menu below', 'avia_framework')  =>'logo_right bottom_nav_header menu_center',
            __('Logo center, Menu below', 'avia_framework') =>'logo_center bottom_nav_header menu_right',
            __('Logo center, Menu above', 'avia_framework') =>'logo_center bottom_nav_header top_nav_header menu_center',
            ));
return $avf_builder_elements;
}
add_filter('avf_builder_elements', 'register_meta_elements', 10, 1);

but for some options – there had to be additional header classes added. So there had to follow some Postprocessing.

see for example this based on Enfold Parallax: https://enfold.webers-webdesign.de/
under Main Menu “Front Page” click “Enfold Consulting” ;)

maybe it is just the fact that the new WP 6.7 switches back to block editor as standard.
Goto Enfold – Theme Options – Select your Editor : and switch back to classic Editor.

or is the problem that you want to use the block editor – but had no enfold elements anymore?

By the way. I can see the button at the top to activate the advanced layout editor – but the active click area is only on the half right. (as if only this part of the standard editor button area is active)
It is that field on the left that overlaps the Enfold button.

______________
not necessary:
it starts with ALB editor even in Block Editor Mode if you got this in your child-theme functions.php:

function trigger_alb_on_load(){
?>
<script>
(function($){
    $(window).on('load', function(){
      setTimeout(function() {
        $("#avia-builder-button").trigger('click');
      }, 300);
    });
})(jQuery);
</script>
<?php
}
add_action('admin_head-post-new.php', 'trigger_alb_on_load');

As a participant as you i can not see private content – may we others see the page it concerns?

Which icons are affected? The normal entypo-fontello icons or individually uploaded icon fonts?

First : how about your WordPress Version – does it need an update too?
if there is a big difference – a major Update in WordPress too … make a Backup of your Installation – and maybe prepare your theme allready for that newest WP – see: Unfortunately, the theme is no longer set as sticky regarding the adaptation to newer php versions / WordPress versions. But that is not necessary and can be done afterwards
What php Version you are running on your system – there are a few changes that need to be taken into account. Especially the changes from php7.x to php8.x and the implementation of jQuery 3.x …

I have never had any problems with WPML updates and Enfold updates. However, I agree with you that plugins that interfere with many areas of a theme always carry update risks.
That’s why I already have a good backup plugin installed for most sites for other reasons. Even the free version of Duplicator is a very good program.
This program creates a complete backup in two files. A zip file with the contents, and an installation file for restoring the backup. Btw. this can also be used for migration.
So if major updates are planned, I create a Duplicator backup beforehand and can then make the updates without losing the status quo.

________________

Updating the theme – additionally you can update the theme by ftp upload : https://kriesi.at/support/topic/some-hints-and-advice-to-update-enfold/#post-1056107

Uploading the new theme takes a little time; if all goes well, the page will only be offline for the small amount of time that it will be renamed. You have the old installation as fallback. (there is no overwriting of the old theme)

Update via ftp.

• download installable newest Enfold : unzip the file – you will have an enfold folder now
• Rename that downloaded newest version to enfold-new
• Upload that enfold-new folder to the themes folder
• Rename your (existing) enfold folder to f.e. enfold-old / in your ftp client (f.e. filezilla)
• Rename your enfold-new folder to enfold / again: in your ftp client (f.e. filezilla)
• Go to dashboard – enfold(-child) – and refresh your merged/cached files on performance tab
• Check if all your theme and existing settings work to your full satisfaction.
• Yes – then stop here

• No – delete or rename back the enfold folder back to enfold-new
• rename the enfold-old folder back to enfold

there is a lot of inline code to handle the toggler ? why?

For my part, I find it confusing that the open toggle moves to the top. For example, I have a plugin, pageScroll2ID, which unfortunately wanted to do the same thing. Fortunately, I was able to exclude the toggles from that behavior.

sorry:

function my_text_strings( $translated_text, $text, $domain ){
  switch ( $translated_text ){
    case 'Suchergebnis nicht zufriedenstellend? Versuche es mal mit einem Wort oder einer anderen Schreibweise'   :  $translated_text = __( 'Versuche es mit einem anderen Suchbegriff', $domain ); break;
  }
  return $translated_text;
}
add_filter('gettext', 'my_text_strings', 20, 3);

ja – wenn du dir die Lang Files ansiehst, ist im de_DE_formal.po und im de_DE.po die gleiche Übersetzung dafür vorgesehen.
Entweder bearbeitest du jetzt diese Langfiles und lädst Child-Theme Lang files hoch, oder du nutzt Plugins um solche Dinge verändern zu können.
Wenn es nicht allzuhäufig vorkommt kannst du diese Übersetzung auch via snippet in der child-theme functions.php ändern:

function my_text_strings( $translated_text, $text, $domain ){
  switch ( $translated_text ){
    case 'If you are not happy with the results below please do another search'   :  $translated_text = __( 'Hier jetzt deine neue Übersetzung hinein', $domain ); break;
  }
  return $translated_text;
}
add_filter('gettext', 'my_text_strings', 20, 3);

You have changed the minimum height of #header_meta – haven’t you? You now have to increase the padding-top for #main for non-transparent pages by this amount (difference from the default 30px to the new value).

f.e.: depends on your hamburger break point

@media only screen and (min-width: 990px) {
  .html_header_top.html_header_sticky #top #wrap_all #main {
    padding-top: 220px;   /*** have a look what your default value is on that + difference of new #header_meta ****/
  }
}

PS: just a moment i have to look how it is about for non-sticky headers.
best is to see the page to give better advice.