if you are styling the post with the classic editor you have the opportunity to choose – that the featured image is shown on the post:

Allthough you can set this even if you style your post with the advanced layout builder (alb) – this setting has no influence and the featured image isn’t shown on the single post!

The code for your child-theme functions.php sets this as default behavior.

sorry i was sure that on former enfold versions this is a menu-item that stays visible in this manner.

In addition to the above add to the quick css:

.html_burger_menu_active .menu-item-avia-special {
    display: block !important;
}

and if you like to change the positions:

.av-main-nav li {
    float: right;
}

maybe here is an important too needed – but test it first without

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

Actually I didn’t want to give any more advice when the right click is blocked. Why are you making it hard on the one who wants to help?

Anyway: for the lightbox image size there are some snippets depending on what is shown :

in your child-theme functions.php you can try this:

function avia_change_masonry_thumbnail_link($size){
  return "full";
}
add_filter('avf_avia_builder_masonry_lightbox_img_size', 'avia_change_masonry_thumbnail_link', 10, 1);

or that:

function avia_change_gallery_thumbnail_link($link, $attachment, $atts, $meta){
    $link = wp_get_attachment_image_src($attachment->ID, "full");
    return $link;
}
add_filter('avf_avia_builder_gallery_image_link', 'avia_change_gallery_thumbnail_link', 10, 4);

then the full image is taken instead of the large one!
if you like to enlarge the lightbox window – we will see when the above is done.

do you know how to give a custom class to your menu items?

On Dashboard – Appearance – Menus
you can see on the top right postion of your browser window a slide-out button : “Screen Options”
Click that button.

On “Show advanced menu properties” mark “CSS Classes”

Then you will have on each menu item an input field for class!

Enter for your “What sets up appart” a class: menu-item-avia-special
and see where it is shown on your menu.

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

Das hat schon seinen Grund weshalb der andere Weg besser wäre. Denn jQuery ist Clientseitig. Dadurch sehen die Bots immernoch die alten tags!
Wenn man es vor der Entstehung also regeln könnte wäre es denke ich besser.

________

There is a reason why the other way would be better. Because jQuery is client-side. So the bots still see the old tags!
So if you could fix it before it is created I think it would be better.

Bei der Seite gehe ich jetzt mal davon aus, dass ich die Antwort in deutsch geben kann.
ich hatte da mal ein kleines script geschrieben, welches unter beibehaltung aller Attribute und Klassen das Tag ändert.
Je spezifischer die Quelle gesetzt ist um so selektiver arbeitet das auch.

Kleiner Denkanstoß: auch wenn es eventuell oldfashioned ist – vermeide ich persönlich das vorhandensein von mehr als einer h1 pro Seite.
Nun zu der Umsetzung – dies in die child-theme functions.php:

function replace_tags_with_tags(){
?>
<script>
  (function($) {       
      function replaceElementTag(targetSelector, newTagString) {
        $(targetSelector).each(function(){
          var newElem = $(newTagString, {html: $(this).html()});
          $.each(this.attributes, function() {
            newElem.attr(this.name, this.value);
          });
          $(this).replaceWith(newElem);
        });
      }
      replaceElementTag('.entry-content-header h2.entry-title', '<h1></h1>'); // weitere Zeilen anfügen durch semicolon getrennt 
      replaceElementTag('.category-term-description p', '<h6></h6>');
  }(jQuery)); 
</script>
<?php
}
add_action('wp_footer', 'replace_tags_with_tags');

Durch den Kommentar siehst du wie du weitere Tag Ersetzungen erreichen kannst.

But you do know that in the first line there is a toggler to have the second line?

Is there a page where we can see the intention?
If you can’t make the page public, can we see it on the Enfold demo pages?

hm strange because on woocommerce the aside is on default in the container.

Don’t know where the mismatch comes from ?
But your “aside” is outside that container:

Have you used some hooks to influence some woocommerce settings in your functions.php?

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

The reason why i ask for block editor ( Gutenberg ) is that some other users here got troubles in using both Enfold ALB and Gutenberg.
It seems that some users got the same behavior on having a scroll down when dragging the element down to the place where they want to go.
https://kriesi.at/support/topic/how-to-hide-shortcode-section-above-avia-layout-builder/#post-1209040

If you are having problems with scrolling down below the fold when dragging an element and the Block Editor is active, then please try adding this to your functions.php file:

They have extra shortcodes visible in the frontend and they could not scroll down in editor.
So again : did you use the block-editor too on your enfold options dialog?

zunächst ist dein Header ja fixiert – er shrinkt halt nur. Ausserdem hast du ja wohl dieses Headerlayout in der Seite gewählt:
transparent oder ich schätze – eher glassy style. Das geht auf der Seite wo du im Editor Modus bist – rechte Leiste : dort steht irgendwo diese Option zur Verfügung.
Wenn das aber so gewollt ist, und du nach dem shrinken allerdings nur einen voll weißen Header haben möchtest musst du ein wenig Quick css dazu setzen um den Header HIntergrund zu setzen.

.header-scrolled .header_bg {
    opacity: 1 !important;
}

is it that you can not drag them or not drop them.

The reason for my question is that if you can’t drag, then it’s probably a deeper problem.
If you can’t place it everywhere, there can be several reasons for that.
One of them is that not all elements can be placed in every other element. There are elements that are pronounced drag and drop elements – others are not. For example, you cannot place 1/2 column into a 1/1 column.

For example, I can’t think of any element in the “Content Elements” tab that allows you to place other elements in there.