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

Hi,

Thank you for the update.

Please look for this css rule:

.html_header_top #top .av_logo_right .logo {
  right: calc(50% + -35.5px);
}

Replace it with:

.html_header_top #top .av_logo_right .logo {
    right: 50%;
    transform: translateX(50%);
}

Best regards,
Ismael

Hi,

4) Save the changes. The CSS files should not be deleted, correct? Now check the folder again: https://i.imgur.com/NTTBKLb.png

This is normal since the theme actually deletes all css files when the theme options are saved, regardless of whether they’re expired or not. This ensures that the custom styles or post css reflect any changes made in the theme options. When we mentioned the css files are actually “not deleted”, we meant that they still exist in the database and will be regenerated on the frontend once the site or page is revisited.

5) The link now redirects to a 404: https://app.site.com/wp-content/uploads/dynamic_avia/avia_posts_css/post-25947.css

This is true, but only because you haven’t visited the page or post yet or utilize the updated timestamp as mentioned above. Once the page or post is revisited, the theme automatically generates the post css files again with the updated changes before displaying the page.

6) On a live site, the CSS does not get regenerated because caching systems serve a cached page and prevent the request from reaching Enfold so it can regenerate the CSS. This is problematic because the CSS should not have been deleted in the first place.

When we tested this in the staging site, we didn’t see any styling issues, even when the cache plugin was activated. As long as the styles of the site are preserved, we don’t see any issues here. If you can provide access to the live site, we’ll check it further.

Best regards,
Ismael

Hey Carla Garrett,

Thank you for the inquiry.

Are you trying to log in to your Themeforest account? Please check the documentation for more info on how to download your items.

— https://help.market.envato.com/hc/en-us/articles/202501014-How-to-download-your-items

If you need to generate a private token for the theme, please check this documentation.

— https://kriesi.at/documentation/enfold/theme-registration/

For any account-related inquiries, we recommend reaching out to the Themeforest or Envato team.

— https://www.envato.com/contact/

Let us know if you more questions.

Best regards,
Ismael

Hi,

You’re welcome! To help you get started with the theme, please check out the documentation.

— https://kriesi.at/documentation/enfold/

Let us know if you any further questions.

Have a nice day.

Best regards,
Ismael

Hi,

Thank you for the inquiry.

You need to extract the enfold.zip file from the initial package and upload that file to your WordPress installation. Please check this documentation for more information.

— https://kriesi.at/documentation/enfold/install-enfold-theme/

We also recommend activating a child theme.

— https://kriesi.at/documentation/enfold/child-theme/

If you have any further questions, please let us know.

Best regards,
Ismael

Hi,

The post css files are not actually deleted; the timestamp of the post css file is just updated, so you won’t be able to access the same file without updating or using the correct timestamp. We tested this again on the test page and didn’t find any changes to the element with the custom styling. Do you see any styling issues on the page after resaving the theme options? We posted the post css file of the test page in the private field, with and without its timestamp.

We did notice that the post css file has a “ver” prefix on the query parameter in its timestamp. This is not the case on our installation. Do you have any idea why it’s prefixed? Is this a custom modification?

— https://app.site.com/wp-content/uploads/dynamic_avia/avia_posts_css/post-25947.css?ver=ver-1763353330

Best regards,
Ismael

Hi,

Please feel free to open another thread if you have additional questions. Thank you for your patience.

Best regards,
Ismael

Hi,

Please feel free to open another thread if you need additional assistance. We’ll close this one for now. Thank you for your patience.

Best regards,
Ismael

Hi,

Thank you for the update.

You can add the code using plugins like Code Snippets so it will not get removed after a theme update, or activate a child theme.

— https://kriesi.at/documentation/enfold/child-theme/

Best regards,
Ismael

Hey Gianluca,

Thank you for the inquiry.

There’s no built-in option for this, but you can try editing the enfold/config-templatebuilder/avia-shortcodes/slideshow_feature_image/slideshow_feature_image.php file, and look for the slide_html function. Let us know if you need more info.

Best regards,
Ismael