Hi,

Thank you for the update.

Since you’re on the latest Safari with no extensions and the video still isn’t loading, it’s worth checking if it’s the actual browser in your device that has the issue.Could you try uninstalling and reinstalling Safari from scratch with default settings? Sometimes a corrupted browser profile or cached data can cause media errors like the one you’re seeing.

Let us know the result.

Best regards,
Ismael

Hey imagestudios,

Thank you for the inquiry.

This looks like a caching issue where old css files are being served instead of the newly generated ones. Please go to Enfold > Performance, disable the File Compression settings, then scroll to the bottom of the same panel and enable the “Delete Old CSS And JS Files?” option. Save the settings and check the frontend again.

If you’re also using a third-party caching plugin, please make sure to purge the cache before testing.

Let us know if the issue persists.

Best regards,
Ismael

Hey Erwin,

Thank you for the inquiry.

It looks like the custom css you have for the .content element is missing a media query reset for smaller screens. The padding and margin values are overriding the responsive styles on mobile. Try adding this below your existing rule:

@media only screen and (max-width: 767px) {
    .content {
        margin-top: 0 !important;
        padding-left: 0 !important;
        padding-right: 0 !important;
    }
}

You can add this to Enfold > General Styling > Quick CSS. Please make sure to purge the cache before testing.

Let us know if the issue persists.

Best regards,
Ismael

Hi,

Thank you for the update.

Good news on the child theme setup –it looks correct. Regarding the Performance settings, the two dropdowns you set to “disabled” are the right ones, so that part is fine.

For the pre-filtering not working yet, the most likely cause is that the masonry js initializes before the sort button click fires, or the category slug in the URL doesn’t exactly match the slug assigned to the sort button. Could you share the site URL and the exact link you’re testing with? Also, please share login details in the private field and let us know the exact category slug you’re using. We’ll take a look directly.

To answer your child theme question — once the child theme is activated, the parent Enfold theme still needs to stay installed and active in the background. Updates to the parent theme will still apply normally, and any modifications you’ve made in the child theme (like the script in functions.php) will be preserved. Please check this documentation for more details:

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

One important note: once the child theme is activated, go to Enfold > Import/Export and use the “Import Settings From Parent Theme” option just once, so all your existing theme options carry over. Do this before making any changes in the child theme options. Also, please make sure to create a full site backup before making any of these changes, and set up a test page to verify things before going live.

Best regards,
Ismael

Hey Erwin,

Thank you for the inquiry.

Unfortunately, there’s no built-in option in Enfold to sort mega menu items alphabetically. The menu items need to be reordered manually by dragging and dropping them in Appearance > Menus. If you’d like this to happen automatically, it would require a custom solution that hooks into the menu rendering, which falls outside the scope of our support.

Let us know if you have more questions.

Best regards,
Ismael

Hey Niky67,

Thank you for the inquiry.

This is a known compatibility issue between Enfold and WordPress 6.9.x, where wp-admin now surfaces notices for styles/scripts enqueued with unregistered dependencies. We have a fix you can add via a code snippets plugin or directly in the child theme’s functions.php file:

add_action( 'admin_enqueue_scripts', function() {

    if ( ! wp_style_is( 'avia-layout', 'registered' ) ) {
        wp_register_style( 'avia-layout', false );
    }

    if ( ! wp_style_is( 'avia-shortcodes', 'registered' ) ) {
        wp_register_style( 'avia-shortcodes', false );
    }

    if ( ! wp_script_is( 'avia-shortcodes', 'registered' ) ) {
        wp_register_script( 'avia-shortcodes', false );
    }

    if ( ! wp_script_is( 'avia_element_js', 'registered' ) ) {
        wp_register_script( 'avia_element_js', false );
    }

}, 1 );

This pre-registers the dependency handles before Enfold’s modules try to enqueue against them, which stops the notices. A proper fix will be included in an upcoming theme update as well.

Let us know if the issue persists.

Best regards,
Ismael

Hey spitsdesign,

Thank you for the inquiry.

The site is loading the opensans_semicondensed font, not the regular opensans. Please make sure to download the regular OpenSans font and upload it, then delete the current semicondensed font. Let us know if the issue persists.

Best regards,
Ismael

Hey Erwin,

Thank you for the inquiry.

The no-scaling option is really meant for cases where you need pixel-perfect originals, so 800kb thumbnails with 100 posts will definitely cause performance issues. The best approach here is to resize your images before uploading them to WordPress. For a masonry gallery, images don’t need to be wider than 1200px or so, and at that size you can usually get them well under 150kb without any visible quality loss.

After resizing, run them through a compression tool like TinyPNG or Squoosh before uploading. If you’ve already uploaded the originals, a plugin like Imagify or ShortPixel can bulk-compress your existing media library.

For the gallery setting itself, you can then switch back to one of the standard cropping options in the masonry element, which will let WordPress serve correctly sized thumbnails automatically.

— https://tinypng.com
— https://squoosh.app

Let us know if you have more questions.

Best regards,
Ismael

Hey tonyiatridis,

Thank you for the inquiry.

It’s very possible that there are invalid html tags in the content. Please review the content and make sure all html tags are closed properly. Let us know if the issue persists.

Best regards,
Ismael

Hi,

Thank you for the update.

The video played fine on Safari when we checked. Have you tried testing it on a different device?

Best regards,
Ismael

Hey Munford,

Thank you for the inquiry.

Only muted videos are allowed to autoplay on most major browsers, including Chrome. You’ll find this information here.

Chrome’s autoplay policies are simple:

Muted autoplay is always allowed.
Autoplay with sound is allowed if:
The user has interacted with the domain (click, tap, etc.).
On desktop, the user’s Media Engagement Index threshold has been crossed, meaning the user has previously played video with sound.
The user has added the site to their home screen on mobile or installed the PWA on desktop.
Top frames can delegate autoplay permission to their iframes to allow autoplay with sound.

— https://developer.chrome.com/blog/autoplay/

Unfortunately, there is no way to override this policy on our end. You’ll have to mute the videos in order for them to play automatically on page load.

Best regards,
Ismael

Hey dnweil,

Thank you for the inquiry.

If you’re using the Advanced Layout Builder, each element, especially Text or Heading elements, has a Styling > Font Sizes option which can be adjusted for different screen sizes.

There is also an Element Visibility setting in the Advanced > Responsive panel which can be used to toggle the visibility of an element for different screen sizes. For cases where element options are not enough, you can always add css modifications.

Best regards,
Ismael

Hey christina495,

Thank you for the inquiry.

Looks like you’re using a third-party plugin for the filter. We recommend reaching out to the plugin developer for additional assistance. In the meantime, you could try this script to set it to automaticall scroll to the product section after clicking any of the category items.

add_action( 'wp_footer', function() {
    if ( ! function_exists( 'is_woocommerce' ) || ! is_woocommerce() ) return;
    ?>
    <script>
    jQuery(document).ready(function($) {
        var $products = $('main.template-shop');

        if (sessionStorage.getItem('av_scroll_products') && $products.length) {
            sessionStorage.removeItem('av_scroll_products');

            setTimeout(function() {
                $('html, body').animate({ scrollTop: $products.offset().top - 20 }, 400);
            }, 200);
        }

        $(document).on('click', '.sidebar .bellows-target', function(e) {
            if (window.innerWidth >= 990) return;
            if ($(e.target).closest('.bellows-subtoggle').length) return;

            sessionStorage.setItem('av_scroll_products', '1');
        });
    });
    </script>
    <?php
}, 20 );

Let us know the result.

Best regards,
Ismael

Hi,

We adjusted the modifications. The first row of the masonry gallery should now be clickable on both desktop and mobile view. The 3-column section should not be covering the masonry gallery on smaller screens. Please make sure to purge the cache before checking.

Best regards,
Ismael

Hey Levi Gahl,

Thank you for the inquiry.

The custom templates don’t support repeater fields at the moment. There is no option to assign a custom layout to an archive page, but you could create a custom page for a specific archive page and do a 301 redirect manually or with the help of a plugin.

Unfortunately, we won’t be able to help you trace back modifications that have been done in the parent theme. These modifications should have been done in the child theme. You’ll need to take note or create a record of the modified files, upload the latest version of the theme, then add the modifications back. We recommend doing all modifications in the child theme in the future.

Best regards,
Ismael