Hey Magdalena,
Thank for your question, but the full-width submenu element is not designed to be sticky on mobile, in the element settings, the sticky option says that it is ignored on mobile.
To make the full-width submenu element sticky on mobile please add this custom ID sticky_on_mobile

Then add this css to your Quick CSS:

.sticky-top {
    position:fixed!important;
    top:0!important;
    z-index:1000!important;
}

Then add this code to the end of your child theme functions.php file in Appearance ▸ Editor:

function custom_sticky_submenu_on_mobile_script() { ?>
  <script>
window.addEventListener('DOMContentLoaded', function() {
(function($){
  $(function() { 
  	var width = $(window).width();
     var scroll_start = 0;
     var startchange = $('#sticky_on_mobile');
     var offset = startchange.offset();
      if (startchange.length){
      	if (width <= 989) {
     $(document).scroll(function() { 
        scroll_start = $(this).scrollTop();
        if(scroll_start > offset.top) {
          document.getElementById('sticky_on_mobile').classList.add('sticky-top');
         } else {
          document.getElementById('sticky_on_mobile').classList.remove('sticky-top');
         }
     });
      }
      }
  });
})(jQuery);
});
</script>
  <?php
}
add_action('wp_footer', 'custom_sticky_submenu_on_mobile_script');

Then clear your browser cache and check.

Best regards,
Mike

Hi,
Glad we were able to help, if you have any further questions please create a new thread and we will gladly try to help you. Thank you for using Enfold.

Best regards,
Mike

Hey badoes,
Thanks for your question, the file creating this error is a core WordPress file and not an Enfold file: /public_html/wp-includes/functions.php
the error line 5831 is a part of WordPress Debug notice for developers and your Sitediagnose recommends that you disable the WordPress Debug:

I also see that you are using an old version of Enfold: v4.7.6.4 with no Envato persoonlijk token, please enter a valid token and update to v5.1.1
If you have trouble updating your version of Enfold you may need to download the latest version from your Theme Forest account and upload it to your WordPress ▸ Appearance ▸ Themes ▸ Add Themes ▸ Add New

after you choose the zip file and click install, you will see a This theme is already installed message because you are updating, you can continue

then you will see the Theme updated successfully message.

After you update, you may also need to update your child theme footer.php as it has changed in the latest version and your old one will probably cause errors, I also see that your child theme has quite a lot of custom files.
I believe that the cause for the error is because Enfold v4.7.6.4 didn’t support the Gutenberg Widget interface at that time, so updating should solve.

Best regards,
Mike

Hi,
Ok, we will leave this open while you try in case you have any further questions, once you are successful please let us know that we can close the thread.

Best regards,
Mike

Hey patde22,
Thanks for your question, as I recall there was an update issue with that old version, when I check your site the Debugging Info for Theme support says that Updates are disabled.
To update your version of Enfold you will need to download the latest version from your Theme Forest account and upload it to your WordPress ▸ Appearance ▸ Themes ▸ Add Themes ▸ Add New

after you choose the zip file and click install, you will see a This theme is already installed message because you are updating, you can continue

then you will see the Theme updated successfully message.

Best regards,
Mike

Hi,
Glad Guenni007 could help, thank you Guenni007, unless there is anything else we can assist with on this issue, shall we close this then?
Best regards,
Mike

Hi,
I looked into this a little further and found another solution but please only use this solution on the same domain URLs, as I pointed out above.

I found an ajax request on stack overflow and worked it out by adding this code to a code block section:

<script>
window.addEventListener('DOMContentLoaded', function() {
  (function ($) { 
  $.ajax({
      url:'https://savvyify.com/enfold/' +
          '3x4-buton-grid',
           type:'GET',
   success: function(data) {
       var content = $('<div>').append(data).find('#main');
      $('#av_section_1').html($(data).find('#test').html());
   }
});
  })(jQuery);
  });;
</script>

please note the domain url, the page url, the ID of the page section, and the element ID, of the source page:

Please note that here the color section minimum height is set to 100%:

the result is:

Best regards,
Mike

Hi,
Glad Guenni007 could help, thank you Guenni007, if you have any further questions please create a new thread and we will gladly try to help you. Thank you for using Enfold.

Best regards,
Mike

Hey rixi,
Thanks for your question and the link to your site, typically for mobile the grid should show only a single column, so I’m not sure why your page is not, but this css in your Quick CSS should correct:

@media only screen and (max-width: 767px){
.responsive #top #wrap_all .slide-entry {
    width: 100%;
    margin-left: 0%;
}
}

After applying the css, please clear your browser cache and check.
If this doesn’t correct please include admin login in the Private Content area so we can investigate.

Best regards,
Mike

Hi,
Tha for your question and the link to your page, please try this css:

#header_meta #avia2-menu .av-icon-char {
	color: #ae9b57;
}

After applying the css, please clear your browser cache and check.
the expected results ▸ https://savvyify.com/img/image/JIOc

Best regards,
Mike

Hey Ploti,
Thanks for your question and the link to your site, I see that for mobile your slider is hidden because of this css from the layerslider:

.ls-forcehide {
    display: none !important;
}

typically this is added when the option LayerSlider ▸ Project Settings ▸ Mobile ▸ Hide On Mobile is enabled:

Please check and disable this option and then publish your slider again.
Then clear your browser cache and any cache plugin, and check.

Best regards,
Mike

Hi,
Thanks for the feedback, and the example to /portfolios/gallery/ the space you are seeing from the masonry gallery below the header is because the color section is vertically centering the element, please note in this screenshot the green space is padding, but the masonry element is centered:

So while on a low content page this would be desired, centering the content, if you would rather have the extra white space below the content please try this css:

#av_section_1.avia-section.av-minimum-height.av-minimum-height-100 .container .content {
    vertical-align: top;
}

After applying the css, please clear your browser cache and check.

Please note that typically we would recommend adding a custom class to your color section so this would only affect the certain color sections that you wish, but in this case I believe that I have successfully targeted these low content page color sections in the css rule with the ID #av_section_1 which would only occur on the first section, and with the added class .av-minimum-height-100, which means it must be a color section with a minimum height of 100%
But please test and check your other pages for any conflicts and link to any you find so we can adjust.

Best regards,
Mike

Hi,
Thank you for the login, after much research I found that part of this issue was from the WP Rocket plugin adding the google font preconnect link to the site:

to disable this you have to install a extra plugin from WP Rocket:

I did this for you to ensure that this would work, which it did but you also had a google font link in your header.php so I removed this also:

I also found that WP Rocket was also preloading the fonts at Preload ▸ URLs to prefetch, so I removed these URLs:

//fonts.gstatic.com
//fonts.googleapis.com
//www.google-analytics.com
//www.google.com
//www.googletagmanager.com
//www.gstatic.com

and this solved your issue:

The one last thing that I noticed was a 404 error for the url in the WP Rocket Preload ▸ Fonts to preload
/wp-content/uploads/avia_fonts/type_fonts/open-sans-v34-latin/open-sans-v34-latin-regular.ttf
so I removed this to solve the 404 error:

please clear your browser cache and check.

Best regards,
Mike

Hi,
Glad this helped, if you have 300+ posts your page would still load all of them.
So for best results use the “load more” option and draw attention to the button so your visitors will know to use it.
In order for 300+ posts to be sorted all of them will need to be loaded, either on page load or later when the user clicks “load more”.

Best regards,
Mike

Hi,
Thanks, I see how the image is after the first “p” tag, but on your site the first “p” tag is a single line:

I love a good spritz cocktail. These drinks are light and refreshing and lower in alcohol than the average cocktail.

and not really a “paragraph” so I don’t think this would help in your situation.
For your site, we could count the first two or three “p” tags, but we would need to find a consistent target for your 800+ pages.

Best regards,
Mike