Hi,

Thank you for the update.

There were two entries for the h3 element in the Advanced Styling panel. We removed both, as they were using the default settings anyway and then adjusted the h3 configuration in General Styling > Typography.

Best regards,
Ismael

Hi,

Thank you for the update.

Have you tried converting the PNG image to an actual ICO file? Please check this tool: https://favicon.io/

Best regards,
Ismael

Hey stevejoneshbs,

Thank you for the inquiry.

This seems to be an issue with custom css — try adding this css rule to override the modification.

.avia-content-slider-active .slide-entry-wrap {
    visibility: hidden;
}

Let us know the result.

Best regards,
Ismael

Hey CESCI,

Thank you for the inquiry.

Is the site hosted on a different server? It’s possible that the server cannot communicate properly with the Envato server for various reasons, such as firewall or security restrictions. You may need to contact your hosting provider or try to update the theme manually via FTP.

— https://kriesi.at/documentation/enfold/theme-update/#update-via-ftp

Best regards,
Ismael

Hey ibuzaev,

Thank you for the inquiry.

Are you using any of the elements on other pages? Please note that the option “load only used elements” only excludes elements that are not used anywhere on the site. Once an element is added to any page, its stylesheets and any related scripts or resources will load across the entire site, regardless of whether they exist on the page or not. Hope this clear things up a bit.

Best regards,
Ismael

Hi,

Thank you for the info.

The site is broken because there is an invalid css rule in the Quick CSS field — a closing curly brace is missing.

/* -- Change font size in Main Menu Bar -- */
#header_main .avia-menu-text {
    font-size: 17px;

We corrected the css code and set the Maximum Container Width to 1310px. The site should be displaying correctly now.

Best regards,
Ismael

Hey Kelly,

Thank you for the inquiry.

Try to add this css to adjust the default top margin of the SVG icons in the header:

#top .social_bookmarks li.avia-svg-icon img[is-svg-img=true], #top .social_bookmarks li.avia-svg-icon svg:first-child {
    height: 1em;
    width: auto;
    margin-top: 3px;
}

Then include the following to realign the SVG icons with the font icons inside the content container:

#top #main .avia-svg-icon.avia-font-svg_entypo-fontello svg:first-child {
    stroke: unset!important;
    top: 8px;
    position: relative;
}

Result:

We recommend uploading a similar custom SVG icon for the instagram icon to fix the alignment issue.

Let us know the result.

Best regards,
Ismael

Hi,

Thank you for the update.

We replaced the shortcode with the Widget Area element displaying the Instagram widget. It’s now rendering, but returning the error: Instagram returned error 429. Are you using the Instagram widget on other sites as well? Please try waiting a few hours or a full day, then check the page again. We have set it to cache the Instagram images on your server.

These threads might be related to the issue:

— https://kriesi.at/support/topic/enfold-theme-instagram-side-bar-widget-not-working/#post-1350365
— https://kriesi.at/support/topic/problem-with-instagram-widget/

Best regards,
Ismael

Hi,

Glad we could help! Feel free to reach out if you have any more questions. Have a nice day.

Best regards,
Ismael

Hi,

Thank you for the update.

Yes, your solution should work. It moves or creates the translation flags after clicking the mobile menu, ensuring they display correctly when the burger overlay is open.

Best regards,
Ismael

Hi,

Thank you for the inquiry.

Looks like the merged stylesheets and scripts are not loading in the Firefox browser. Have you tried temporarily disabling the cache plugin and the Enfold > Performance > File Compression settings?

Best regards,
Ismael

Hi,

Thank you for the info.

Looks like the script is not working as intended so we removed it. Unfortunately, we didn’t find any other solution to prevent the slides’ background images from loading when the slider is not visible. You may need to remove the other sliders and rely on the responsive images if you’re using the Fullwidth Easy Slider, or manually apply different background images to the slides for different screen sizes using css. Example:

/* mobile */
@media (max-width: 767px) {
    .avia-fullscreen-slider .avia-slideshow > ul > li:nth-child(1) {
        background-image: url("/path/to/slide1-mobile.jpg") !important;
    }
    .avia-fullscreen-slider .avia-slideshow > ul > li:nth-child(2) {
        background-image: url("/path/to/slide2-mobile.jpg") !important;
    }
    .avia-fullscreen-slider .avia-slideshow > ul > li:nth-child(3) {
        background-image: url("/path/to/slide3-mobile.jpg") !important;
    }
}

/* tablet */
@media (min-width: 768px) and (max-width: 1023px) {
    .avia-fullscreen-slider .avia-slideshow > ul > li:nth-child(1) {
        background-image: url("/path/to/slide1-tablet.jpg") !important;
    }
    .avia-fullscreen-slider .avia-slideshow > ul > li:nth-child(2) {
        background-image: url("/path/to/slide2-tablet.jpg") !important;
    }
    .avia-fullscreen-slider .avia-slideshow > ul > li:nth-child(3) {
        background-image: url("/path/to/slide3-tablet.jpg") !important;
    }
}

Best regards,
Ismael

Hey placeit53591,

Thank you for the inquiry.

The sizes of the headings can be adjusted in the Enfold > General Styling > Typography panel. You can also define different sizes for different screen widths.

Best regards,
Ismael

Hey jimmiemoreland,

Thank you for the inquiry.

If you have already enabled the compression options in the WP Rocket plugin or through your hosting provider, you need to disable the theme’s compression option found in Enfold > Performance panel. Enabling both options is redundant and could cause caching issues. We recommend disabling the caching and compression options while editing the site, and enable them again once the site is fully configured and ready to go live.

Let us know if you need more info.

Best regards,
Ismael

Hey Angelo,

Thank you for the inquiry.

However, I discovered that if you change anything in a Custom Element that has already been used, the change is not propagated to the pages where the element has been used.

On the Custom Element Templates, you have the option to lock certain element options. When an option is locked, you won’t be able to adjust it on the instance, and when this locked option is updated in the original source, it will be propagated to every instance. However, unlocked options can be changed on every instance of the CET and are unique to each instance, so when this particular option is updated in the original source, every instance will retain its own value. In that case, if you need a global element that can be updated from a single source and doesn’t need to look different or contain different content on certain pages, make sure to lock all the options.

On the other hand, if you need to create a global layout that can be updated from a single source and contains multiple elements, including Custom Element Templates, use the Custom Layout feature.

Let us know if you need more info.

Best regards,
Ismael