Hey Philipp Nepraunig,

Thank you for the inquiry.

We are aware of the issue, and a fix will be included in the next patch. In the meantime, you can add the code provided in the following thread to the functions.php file:

— https://kriesi.at/support/topic/not-registered-dependencies-for-enfold-css-and-js/#post-1495467

Let us know the result.

Best regards,
Ismael

Hey mattb1169,

Thank you for the inquiry.

We are not seeing the widget in the header, only the submenu on the top header. Did you remove the header widget? Please add it again so we can inspect the elements properly.

Best regards,
Ismael

Hi,

Thank you for the update.

To handle all those URL patterns, you can add the following to your child theme’s functions.php. This covers both cases — empty query results and valid archive/query pages that you don’t want accessible:

add_action( 'template_redirect', function() {
    if (
        ( is_author() || is_attachment() || is_post_type_archive() || is_tax() || is_category() || is_tag() ) &&
        ! have_posts()
    ) {
        global $wp_query;
        $wp_query->set_404();
        status_header( 404 );
        nocache_headers();
        include( get_404_template() );
        exit;
    }
} );

This will redirect all the content listing URLs, category URLs and feed endpoints you listed to your custom 404 page. It covers author, attachment, post type archive, taxonomy, category and tag routes.

Let us know how it goes.

Best regards,
Ismael

Hey Munford,

Thank you for the inquiry.

The code you found is too general and will likely affect other elements on the page, not just the portfolio grid.

A cleaner approach is to add a custom css class to your portfolio element and target that instead. You can do this by opening the portfolio element in the layout builder, go to the “Advanced” tab and add a custom class name there (e.g., av-music-portfolio). Then add your spacing rule to Enfold > General Styling > Quick CSS:

#top .av-music-portfolio .isotope-item {
    margin-bottom: 20px;
}

This way the rule only applies to that specific portfolio and nothing else on the site.

For more details on adding custom css classes in Enfold, please refer to the documentation:

— https://kriesi.at/documentation/enfold/add-custom-css/

Let us know if the issue persists.

Best regards,
Ismael

Hey JannyPolak,

Thank you for the inquiry.

Looks like the Advanced Styling settings may be getting overridden by another css rule, or the styles may be cached. Before anything else, please try to disable the Enfold > Performance > File Compression settings, save, and purge your cache, then check again.

If the styling still doesn’t apply, you can force the font and text-transform for the main nav links with this custom css added on the Enfold > General Styling > Quick CSS field:

#top .av-main-nav > li > a > .avia-menu-text {
    font-family: 'Josefin Sans', sans-serif;
    font-size: 30px;
    font-weight: 400;
    text-transform: uppercase;
}

Make sure Josefin Sans is loaded on your site. If you’re using it via Enfold > Advanced Styling, it should already be enqueued. If not, you may need to select it under Enfold > General Styling > Fonts.

Please make sure to purge the cache before testing.

Let us know if the issue persists.

Best regards,
Ismael

Hi,

Thank you for the login info.

We found some invalid css in the Quick CSS field that was causing the issue. We have gone ahead and fixed that. Please make sure to purge the cache before testing again.

As for the cache plugin, most of them do the same job and it really comes down to personal preference. LiteSpeed Cache is a solid choice, so you can stick with that.

Let us know if the issue persists.

Best regards,
Ismael

Hey bemodesign,

Thank you for the inquiry.

Try to use more specific selectors targeting the content wrapper — try to use this instead:

@media only screen and (max-width: 767px) {
    .template-page .entry-content-wrapper h1,
    .template-page .entry-content-wrapper h2,
    .template-page .entry-content-wrapper h3,
    .template-page .entry-content-wrapper h4,
    .template-page .entry-content-wrapper h5,
    .template-page .entry-content-wrapper h6 {
        text-transform: none !important;
    }
}

Please make sure to purge the cache before testing. Let us know if the issue persists.

Best regards,
Ismael

Hi,

Sorry for the delay. We’re now able to publish a page without issue. We edited the enfold/config-templatebuilder/avia-template-builder/php/class-shortcode-template.php file around line 2502:

$this->config['self_closing'] = is_array( $params ) && array_key_exists( 'content',  $params ) && is_null( $params['content'] )  ? 'yes' : 'no';

Please confirm if the fix is working on your end.

Best regards,
Ismael

Hi,

Sorry for the confusion. We misread your first post and thought that you were intentionally saving html with unclosed tags. Please post the html or content that you’re trying to add to the page and provide the login details in the private field so we can test this further.

Best regards,
Ismael

Hi,

Thank you for the update.

We saved the content of the Welcome page as a template called “welcome temp a”, applied it to another page, and added new elements, but we are unable to reproduce the issue. Please try editing the page in the private field to see if you can reproduce the issue there.

Best regards,
Ismael

Hi,

Glad to know that this has been resolved! Please don’t hesitate to open another thread if you have more questions.

Have a nice day.

Best regards,
Ismael

Hey Advantage09,

Thank you for the inquiry.

After reviewing the page, we can see that there are three Separator/White Space elements placed below the Grid Row element. These are causing the large gap on mobile.

You have two options to fix this:

1. Remove the three Separator/White Space elements entirely if they are not needed.
2. Keep them but set their visibility to desktop only. You can do this by editing each Separator element, going to Advanced > Responsive, and adjusting the Element Visibility setting so they only show on desktop.

Please make sure to purge the cache before testing. Let us know the result.

Best regards,
Ismael

Hey,

Thank you for the update.

Sections disappearing from the page is usually caused by invalid html in one of the layout builder elements. If any Text Block or Code element on the page contains an unclosed html tag or malformed markup, it can break the structure of the entire page and cause sections below it to collapse or disappear entirely.

Could you check if you have added any custom html or script tags inside any of the elements on that page? If so, please make sure all tags are properly opened and closed. For example, a missing closing tag like div or section can silently break everything below it.

A quick way to test this is to temporarily disable elements one by one (starting from the top of the page) until the missing sections reappear. That will help narrow down which element is causing the issue.

If you are not sure where to start, please share your login credentials in the private field below and we will take a look directly.

Let us know the result.

Best regards,
Ismael

Hey Gonmyr,

Thank you for the inquiry.

To get a header that look something closer to the samanthasiffring.com site, try to go to Enfold > Header > Header Layout and set Menu and Logo Position to “Logo center, Menu above”. On the specific page, open the Layout tab and set the header transparency to transparent or glassy. Build the hero section using a fullscreen Color Section or slideshow in the Advance Layout uilder.

For a full overview of the available header options, please check the documentation:

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

Let us know if you have more questions.

Best regards,
Ismael

Hey webzies,

Thank you for the inquiry.

It looks like the critical error is caused by the create_function() in your child theme. This function was deprecated in php 7.2 and completely removed in PHP 8.0, which is why switching to PHP 8.1 triggers a fatal error.

You’ll need to replace any instances of create_function() in your child theme. Since this change is in your child theme and not Enfold core, you’ll need to make those updates yourself. You can search your child theme files for “create_function” to locate all instances.

Let us know if the issue persists after making those changes.

Best regards,
Ismael