Hey agenturwendt,

Thank you for the inquiry.

I tried targeting .category-kundenstimmen time.slide-meta-time.updated with CSS, but it didn’t work.

Try to use this css code instead:

.page-id-167 .slide-meta-time.updated {
    display: none;
}

Best regards,
Ismael

Hi,

Thank you for the inquiry.

As mentioned by @Guenni007 above, the preview image should be clickable by default. Could you provide a link to the page with the post slider element?

Best regards,
Ismael

Hi,

Thank you for the inquiry.

We added this css code to reduce the default padding of the main container and the color section below the image.

#top #main .avia-section .template-page {
    padding-top: 0;
}

.template-page.content.av-content-full.alpha.units.av-enable-shadow {
    padding-top: 0;
}

Please note that this modification will be applied globally and will impact all color sections.

Best regards,
Ismael

Hi,

Thank you for the info.

Unfortunately, we won’t be able to provide an appropriate solution without inspecting the elements. You may need to adjust the z-index of the parent container where the datepicker is located. Even if the z-index is set to 10,000, it won’t have the desired effect if the element is within a container that has a lower z-index relative to its siblings.

Best regards,
Ismael

Hi,

Thank you for the clarification.

To remove the highlight or focus outlines, try to add this css code:

#top .av-control-minimal .avia-slideshow-arrows a, #top .av-control-minimal .avia-slideshow-arrows a:before {
    user-select: none;
    outline: none;
    -webkit-tap-highlight-color: transparent;
}

Best regards,
Ismael

Hi,

Thank you for the update.

The builder also requires these meta fields.

_aviaLayoutBuilder_active
_aviaLayoutBuilderCleanData
_avia_builder_shortcode_tree
_alb_shortcode_status_content
_alb_shortcode_status_clean_data
_alb_shortcode_status_preview
_avia_sc_parser_state
_av_alb_posts_elements_state
_av_el_mgr_version

You may need to directly edit the posts and activate the ALB manually in order to properly create these fields.

Best regards,
Ismael

Hi,

Sorry for the delay. We are still not sure what is causing the issue, but it seems to be related to the tab section on the page and its contents, which are quite extensive. As mentioned above, when we copied the template to our local installation, we were able to reproduce the “exceeded quota” error but were still able to update the page. In the meantime, please try to reduce or separate the contents of the tab section and create dedicated pages for them instead.

Best regards,
Ismael

Hi,

Thank you for the login.

The issue doesn’t occur on a test page (see private field), so it seems to be something specific to the page above. Did you add any htm or custom scripts to the page? Have you tried recreating the page from scratch?

Best regards,
Ismael

Hey M-Graphics24,

Thank you for the inquiry.

There is no option for this out of the box but we might be able to modify it with css. Could you provide screenshots of the changes that you’d like to implement? You can use platforms like Savvyify, Imgur or Dropbox.

Best regards,
Ismael

Hi,

Thank you for the inquiry.

Hi NO HTML or custom scripts,

There are tons of HTML in the page and this particular html is causing the issue because it’s not closed properly.

< strong >ANY Platform

Please review the html and make sure that they are all valid.

Best regards,
Ismael

Hey Michael F,

Thank you for the inquiry.

Did you toggle the Enfold > Layout Builder > Custom Layout And Dynamic Content and the Lock Advanced Layout Builder settings? Please make sure that the builder is not locked.

Best regards,
Ismael

Hey James,

Thank you for the inquiry.

Please try to add this css code and let us know of the result.

@media (max-width: 768px) {
    :target {
        scroll-margin-top: 200px;
    }
}

Make sure to toggle or temporarily disable the Enfold > Performance > File Compression settings and purge the cache after adding the modification.

Best regards,
Ismael

Hey Antonio,

Thank you for the inquiry.

We updated the script and the style modifications a bit so that they only apply on desktop view:

Script:

function next_slide_on_image_click() { 
?>
<script type="text/javascript">
window.addEventListener("DOMContentLoaded", function () { 
    if (window.matchMedia("(min-width: 1024px)").matches) { // Apply only for screens wider than 1024px
        (function($){
            $('.avia-slide-wrap img').click(function() {
                $(this).closest('.avia-slideshow').find('.avia-slideshow-arrows a.next-slide').trigger('click');
            });
        })(jQuery);
    }
});
</script>
<?php 
}
add_action('wp_footer', 'next_slide_on_image_click');

CSS:

@media only screen and (min-width: 1024px) {
  .avia-slideshow-arrows.avia-slideshow-controls {
    height: 100% !important;
    width: 100% !important;
    display: block;
    position: absolute;
    top: 0;
    left: 0;
  }

  #top .avia-slideshow-arrows a {
    width: 50% !important;
    height: 100%;
    top: 0;
    margin: 0 !important;
    padding: 0 !important;
    opacity: 0 !important;
  }

  #top .avia-slideshow-arrows a.prev-slide {
    left: 0;
  }

  #top .avia-slideshow-arrows a.next-slide {
    right: 0;
  }
}

Best regards,
Ismael

Hi,

Thank you for the update.

The thickness of the font is different because the text is wrapped in a < b > tag or bold element. Did you add these tags?

<b>Produktivitätsverlust durch veraltete Tools</b>

You can adjust the font weight with this css code:

tr th:first-child b, tr td:first-child b {
    font-weight: normal;
}

Best regards,
Ismael

Hi,

You don’t need to edit the functions.php file because the Custom CSS Class name field is already available in every element. However, if you need to enable the Appearance > Theme File Editor, make sure that the DISALLOW_FILE_EDIT directive in the wp-config.php file is set to true or is not present at all.

I do not understand why the images are scaled even though the screen resolution for both is 1080×2408 pixels.

Please note that the value (max-height: 800px) depends on the browser viewport size, not the screen resolution, which includes calculation for the device pixel ratio (DPR) or pixel density. For example, a phone with a screen resolution of 1024×2048px and a DPR of 3 will have a viewport size of approximately 360×802px.

We recommend leaving the setup as it is since it would require a significant amount of modifications to account for all possible screen sizes. Making sure that the image is fully visible in the viewport might be unnecessary because users can still scroll to view the entire content.

Best regards,
Ismael