Yes now you have to describe more precise what you like to reach.

aha – thats the reason why we ask for link to page. It’s hard to give advice only from a description.

Zunächst wäre der Ort auch im enfold/lang/ Ordner
und dann hängt es natürlich davon ab, welche Ansprache Form Du gewählt hast.
Wenn die Seite auf Formal “Sie” basiert, wäre es schon: de_DE_formal.po / mo
bei dem “Du” als Anrede: de_DE.po / mo

ich würde jedoch empfehlen, ein Child-Theme lang ordner anzulegen, und dort die Files zu bunkern. So gehen diese nicht beim nächsten Update verloren. Und ich empfehle auch die po files dort zu hinterlegen, falls man was ergänzen möchte.

Dann kann man das Laden der Child-Theme lang Files initieren, indem man das hier ins child-theme functions.php setzt:

function overwrite_language_file_child_theme() {
    $lang = get_stylesheet_directory().'/lang';
    return $lang;
}
add_filter('ava_theme_textdomain_path', 'overwrite_language_file_child_theme');

hoffe der Filter ist noch gültig.

Besides the performance problem you have when you put two sliders on the page, and only show one then depending on the screen width –
think a little bit about your request – how should this work?
The height is the starting point for the image.
This height must fill the screen height, so you have automatically cropping with a landscape image ( If the aspect ratio is not the same as the screen dimensions.)
This is also the case with large screens.
Only the Full Width slider shows you (almost) always the whole image without trimming.

and how do the visitors then navigate further on your site?

under my nick or avatar there is my info about webpage.

first i did it with jQuery and used the existing postnavigation
this to functions.php of your child-theme:

function post_nav_to_content(){
?>
<script type="text/javascript">
(function($){
	$('a.avia-post-nav').wrapAll('<div class="container postnavigation"></div>');
	$('.container.postnavigation').wrap('<div class="main_color av_default_container_wrap container_wrap fullsize postnav_new"></div>');
	$('.postnav_new').detach().clone().insertBefore('#footer');
})(jQuery);
</script>
<?php
}
add_action('wp_footer', 'post_nav_to_content');

you see what it does
first : wrap the all post-nav anchors in one surrounding container
second : then it wraps again ( to have all those settings from enfold like a section)
third: it takes that last container from its place and insert it just before footer.

this to quick css:

.postnav_new {
    height: 60px;
    position: relative;
    display: block;
    border: none !important;
}

.responsive .container.postnavigation {
  max-width: 1410px;  /* depends on your general settings container width*/
}

#top .postnavigation .avia-post-nav {
  background: transparent;
  bottom: 0 !important;
  top: 0 !important;
  margin-top: 0;
  position: absolute;
  height: 60px;
  border-radius: 5px;
}

#top .postnavigation .avia-post-nav .entry-info-wrap {
  display: table;
  height: 60px;
}

#top .postnavigation .avia-post-nav:hover .entry-info-wrap {
  width: auto !important;
}

#top .postnavigation .avia-post-nav .label {
  font-size: 36px;
}

#top .postnavigation .avia-post-nav .entry-info {
  margin: 0 10px !important;
  vertical-align: bottom;
  height: 60px;
  width: auto !important;
  display: block;
  white-space: nowrap;
}

.postnav_new .entry-image {
  display: none !important;
}

.avia-post-nav .entry-info-wrap {
  display: inline-flex;
}

just test it
the rest is styling . f.e. gettting a different arrow or having no background-color

on most cases form fields got an extra class on that. On Enfold it is the class: error
so that could help:

.form_element.error {
    outline: 2px solid  red;
}

you can use border aswell – but sometimes it has not effect with border.

if you are not on Enfold older than 4.3 afaik that filter is deprecated : avf_builder_boxes
the new filter is : avf_alb_supported_post_types
and for metabox: avf_metabox_layout_post_types

you can read here how to: https://kriesi.at/documentation/enfold/intro-to-layout-builder/#alb-for-any-post-type

so try this instead:

// For Activation ALB for CPT
function avf_alb_supported_post_types_mod( array $supported_post_types )
{
  $supported_post_types[] = 'projekt';
  return $supported_post_types;
}
add_filter('avf_alb_supported_post_types', 'avf_alb_supported_post_types_mod', 10, 1);

// For layout meta box
function avf_metabox_layout_post_types_mod( array $supported_post_types )
{
 $supported_post_types[] = 'projekt';
 return $supported_post_types;
}
add_filter('avf_metabox_layout_post_types', 'avf_metabox_layout_post_types_mod', 10, 1);

• This reply was modified 6 years, 5 months ago by Guenni007.

by the way vectorcriz – on some pages the heading of “Kontakt” is bold and big on some it is not.

so why don’t you use the full-width slider then?
it shows all of the image always – even on small screens.

on functions-enfold.php on line 734 (Enfold 4.6.2) there is:

$image 	= isset($entry->av_custom_image) ? $entry->av_custom_image : get_the_post_thumbnail( $entry->ID, 'thumbnail' );
// change to
$image 	= isset($entry->av_custom_image) ? $entry->av_custom_image : get_the_post_thumbnail( $entry->ID, 'square' );

then the 180px square image from enfold is taken. Don’t know if there is a filter to influence it via child-theme functions.php (yet).

As you say it – these are featured images.
on default on WordPress these are 80px in dimension – so if you make them bigger – the next image in the srcset is taken – and that could be a large one (this will not be an enfold image size – it will be the one you have setup on settings – media .
mostly it is 300px wide.

Edit: i do not know yet how to influence what image is taken from srcset.

to remove the circular shape of the images you just have to enter the following into the Quick Css.

.avia-post-nav .entry-image img {
    border-radius: 10px;  /* or something different here */
    border: 2px solid #fff;  /* if you like */
}

I’m a participant like you – so I don’t see your private messages.

nobody can post a link to a livepage here?

Dear Mods : this rule seems to be obsolete. It is hard to overwrite a height rule set to auto !important.
unset , initial and inherit does not do the trick.

The rule has no influence on the otherhand – so test it please if it could be deleted.
see fixed but shrinking header here: https://webers-testseite.de/cynthia/fixed-header-on-mobile/