did you load your jQuery in the footer?

if so these snippets added to your child-theme functions.php had to be loaded afterwards.
( just add a low ( higher value) priority )
so try with 999 on priority as Ismael does with his snippet :

function open_masonry_entries_in_new_tab(){
?>
<script>
(function($) {
  MutationObserver = window.MutationObserver || window.WebKitMutationObserver;
  var observer = new MutationObserver(function() {
    $("a.av-masonry-entry").attr("target", "_blank");
  });
  observer.observe(document, { subtree: true, childList: true });
})(jQuery);
</script>
<?php
}
add_action('wp_footer', 'open_masonry_entries_in_new_tab', 999);

PS:

$priority (int) (Optional) Used to specify the order in which the functions associated with a particular action are executed. Lower numbers correspond with earlier execution, and functions with the same priority are executed in the order in which they were added to the action. Default value: 10

see here the first row: https://consulting.webers-testseite.de/buttons/

to have different colors than blue there is a custom-class for it: red, green, etc.
to have that effect there is a custom class: btn-12
And: The button color is set to light-transparent

to have two different button lables i put in the Button Label Field: <span>Click!</span><span>Read More</span>

/****** Button 12 ***********/

#top .btn-12 .avia-button {
  position: relative;
  border:none;
  box-shadow: none !important;
}

#top .btn-12 .avia-button .avia_iconbox_title {
  display: block;
  position: absolute;
  height: 60px;
  width: 250px;
  -webkit-perspective: 650px;
  perspective: 650px;
}

#top .btn-12 .avia-button .avia_iconbox_title span {
  background: rgb(0,172,238);
  background: linear-gradient(0deg, rgba(0,172,238,1) 0%, rgba(2,126,251,1) 100%);
  display: block;
  position: absolute;
  width: 250px;
  height: 60px;
  box-shadow:inset 2px 2px 2px 0px rgba(255,255,255,.5),
    7px 7px 20px 0px rgba(0,0,0,.1),
    4px 4px 5px 0px rgba(0,0,0,.1);
  border-radius: 5px;
  margin:0;
  text-align: center;
  -webkit-box-sizing: border-box;
  -moz-box-sizing: border-box;
  box-sizing: border-box;
  -webkit-transition: all .3s;
  transition: all .3s;
}

#top .btn-12.red .avia-button .avia_iconbox_title span {
    background: rgb(156, 39, 176);
    background:-moz-linear-gradient(180deg, rgba(244, 67, 54, 1) 0%, rgba(156, 39, 176, 1) 100%); 
    background:-webkit-linear-gradient(180deg, rgba(244, 67, 54, 1) 0%, rgba(156, 39, 176, 1) 100%);
    background:linear-gradient(180deg, rgba(244, 67, 54, 1) 0%, rgba(156, 39, 176, 1) 100%);
}

#top .btn-12.green .avia-button .avia_iconbox_title span {
    background: #00CF30;
    background: -webkit-linear-gradient(to bottom, #00CF30 0%, #009C24 100%);
    background: -moz-linear-gradient(to bottom, #00CF30 0%, #009C24 100%);
    background: linear-gradient(to bottom, #00CF30 0%, #009C24 100%);
}

#top .btn-12 .avia-button .avia_iconbox_title span:nth-child(1) {
  -webkit-transform: rotateX(90deg);
  -moz-transform: rotateX(90deg);
  transform: rotateX(90deg);
  -webkit-transform-origin: 50% 50% -30px;
  -moz-transform-origin: 50% 50% -30px;
  transform-origin: 50% 50% -30px;
}

#top .btn-12 .avia-button .avia_iconbox_title span:nth-child(2) {
  -webkit-transform: rotateX(0deg);
  -moz-transform: rotateX(0deg);
  transform: rotateX(0deg);
  -webkit-transform-origin: 50% 50% -30px;
  -moz-transform-origin: 50% 50% -30px;
  transform-origin: 50% 50% -30px;
}

#top .btn-12 .avia-button:hover .avia_iconbox_title span:nth-child(1) {
  box-shadow:inset 2px 2px 2px 0px rgba(255,255,255,.5),
    7px 7px 20px 0px rgba(0,0,0,.1),
    4px 4px 5px 0px rgba(0,0,0,.1);
  -webkit-transform: rotateX(0deg);
  -moz-transform: rotateX(0deg);
  transform: rotateX(0deg);
}

#top .btn-12 .avia-button:hover .avia_iconbox_title span:nth-child(2) {
  box-shadow:inset 2px 2px 2px 0px rgba(255,255,255,.5),
    7px 7px 20px 0px rgba(0,0,0,.1),
    4px 4px 5px 0px rgba(0,0,0,.1);
  color: transparent;
  -webkit-transform: rotateX(-90deg);
  -moz-transform: rotateX(-90deg);
  transform: rotateX(-90deg);
}

And for example – you are loading jQuery in both installations on the same place? Or do you load on the one in the header section and the other in footer?
sometimes you don’t think about tiny differences, but they can have a big impact. – What about the php versions of the two installations? Also identical?

snippet is here for your child-theme functions.php:

https://pastebin.com/k0f385TJ

Boardsoft will change the special characters needed for that snippet.

Hast du Ihn unter Enfold Child – Layout Builder abgestellt oder gar deinstalliert?

wenn du die zweite Postiion gewählt hast, versuch Ihn mal wieder zu aktivieren und die Einstellung dann zu setzen und danach kannst du ihn wieder deaktivieren. Nicht das der da trotzdem zwischen funkt.

siehe Nachtrag : zum Layerslider

you can try:

/*** for fullwidth sliders ***/
.avia_transform .av_slideshow_full .active-slide .avia-caption-title,
.avia_transform .av_slideshow_full .active-slide .avia-slideshow-button {
    -webkit-animation: unset !important;
    animation: unset !important;
    opacity: 1 !important;
    transition: none !important;
    visibility: visible !important;
}

if there is a custom-class on that alb – it will be as you can see above on av_slideshow_full

zunächst um deinen Bedenken Rechnung zu tragen: solltest du deine Startseite als Maintenance Mode Seite definieren ( über Theme Options Tab).
Wer nämlich deine Seite über z.B die Google Suche direkt findet ist trotzdem auf deiner Seite. – und hier begrüßt ihn als erstes : Google Analytics – welches unbedingt ein Opt In benötigt.

Ich lade meine Schriften alle local. Heißt: ich lade mir die Google Fonts herunter und binde diese im Theme local ein.
Um Copyright Problemen diesbezüglich zu umgehen kann man sich bei Google einloggen, und dort den Nutzungsbedingungen der Google Fonts zustimmen. Ist schon ne Weile her, dass ich dies tat; daher musst du mal Googlen wo das war. Ist nur einmal nötig – danach kann man alle Google Fonts auch nutzen in dem man sie downloaded und einbindet.

Um die Einbindung via Enfold zu unterdrücken nutze ich immer noch das alte Snippet:
*removed the deprecated snippet*
aber es geht wohl auch so :

function my_output_google_webfonts_script( $activate ){
  return false;
}
add_filter( 'avf_output_google_webfonts_script', 'my_output_google_webfonts_script', 10, 1 );

ich habe mir ein kleines Plugin dafür geschrieben, aber man kann auch ganz einfach mit den Angaben die Google selbst anbietet bzw. der Google Webfont Helper: Link für Raleway bietet die Fonts dann local einbinden.

• This reply was modified 3 years, 3 months ago by Yigit.

ok – now i see the pages . There are elements in it.
to have a color-section with background-image responsive you had to determine the height in that aspect-ratio of the bg image.
for your page (free-session) i would insert the 1500px x 430px image format – and set the background-image to cover.

Then for your page: free-session

#top.page-id-9607 #av_section_1 {
  height: 28.66vw; /***  100x(430px:1500px)  ***/
  min-height: 350px;
  background-size: cover !important; /*** but you can do that on alb settings ***/
}

The min-height rule is to have enough height on small screens to fully surround the content

Same on your home page – let the image be full and set background-size to cover

#top.page-id-143 #av_section_3 {
  height: 26.04vw; /***  100x(500px:1920px)  ***/
  min-height: 500px;
  background-size: cover !important; /*** but you can do that on alb settings ***/
}

You had to know a fundamental thing on WPML: Nearly all of the Enfold Settings are saved separatly by each language.
Quck Css, Color Settings, Advanced Settings etc. pp.
You see an additional Tab on top of the enfold settings:

My advice is: Layout and Style your first default language. After doing that – you can then transfrer your enfold settings to the other languages.
Just export the enfold theme settings file from your default language – change the lang on that tab – and import that theme settings file.
Many claim that this is too complicated, I find it a nice feature. You can choose your own colour schemes and fonts etc. for each language.

yes – different classes on the same element are noted without space. .av-submenu-container.topsubmenu
if you have .av-submenu-container .topsubmenu the av-submenu-container has a child with class: topsubmenu. What is not the fact.
The order is then also important, with parent – child relationships anyway – and here at the same element in particular.

i would do that with an image of houzz and a small snippet in child-theme functions.php:

function avia_add_houzz_social_icon($icons) {
    $icons['Houzz'] = 'houzz';
    return $icons;
}
add_filter('avf_social_icons_options','avia_add_houzz_social_icon', 10, 1);

you find this new entry than on “social profiles” at the end of the list.
for inserting now the new icon just place this to quick css:

#top #wrap_all .av-social-link-houzz a:before{
    content: "";
    width: 20px;
    height: 20px;
    display: inline-block;
    vertical-align: top;
    background: url(/wp-content/uploads/path-to-houzz.svg) no-repeat center center;
    background-size: contain;
}

#top #wrap_all .av-social-link-houzz:hover a {
  /***  optional ***/
}

now the values depends on where you will show your social media icons

the custom class – if you set it directly to the alb element (submenu) itself goes to the submenu container.
so it is the same place – therefore it has to be placed without space in the rule – and because it is after the av-submenu-container class :

@media only screen and (min-width: 1024px) {
	#top .av-submenu-container.topsubmenu { display: none !important; }
}

no i’m participant as you are.
But i guess you are belonging to magazine.php line 1441 and the category for that post.

$cats_html .=		'<span class="av-magazine-text-sep text-sep-cats">In</span>';

but i do not see that this is in translated in any lang file – so it makes me wonder that you have there a “Da”

choose for that button alb element the option to have an icon. place it where you like – even to see only on hovering.
then replace that icon by an image via quick css.
To better select the specific button – give a custom class to the button alb itself – f.e.: imagebutton

.avia-button-wrap.imagebutton {
  overflow: hidden;
}

.imagebutton .avia_button_icon {
  height: 0px;
  overflow:visible;
  display: inline-block;
  vertical-align: top !important;
}

.imagebutton .avia_button_icon::before {
  content: "";
  background-image: url(/wp-content/uploads/IMAGE.svg);  /*** path to your image file ***/
  background-repeat: no-repeat;
  background-size: contain;
  width: 50px;
  height: 50px;
  position: relative;
  display: inline-block;
  top: -11px;
  left: -5px;
}

See here – buttons on the right – green or blue one: https://webers-testseite.de/buttons/