Viewing 30 results - 31 through 60 (of 141,772 total)
  • Author
    Search Results
  • #1486133

    Hi,

    Try to edit the Contact Form element and set the Styling > Form Color Scheme to Dark Transparent. You can also replace the previous css with this:

    #top #wrap_all .main_color .button, .main_color #submit, #top #wrap_all .contact-form :is([type=submit], button:not([type=reset])) {
        align-items: center;
        display: inline-flex;
        gap: .5em;
        justify-content: center;
        border-radius: 100px;
        color: rgba(0, 0, 0, 0.6);
        border: 1px solid rgba(0, 0, 0, 0.6);
        background: 0 0;
        font-size: 14px;
        border-style: solid;
        border-width: 1px;
        transition: all 0.4s ease-in-out;
        padding: 9px 10px 7px;
        width: 80px;
    }

    Best regards,
    Ismael

    Hi,

    Thank you for the update.

    We edited the Horizontal Gallery element and set Stil > Galerie > Bildgröße to “No scaling” to display the original size, then added this css code to adjust the minimum height of the gallery.

    @media only screen and (max-width: 768px) {
    
      /* Add your Mobile Styles here */
      .responsive .av-horizontal-gallery-inner {
         min-height: 500px !important;
      }
    
       .responsive .av-horizontal-gallery-img {
          transform: none;
          top: 0;
       }
    }
    

    View post on imgur.com

    Best regards,
    Ismael

    #1486129

    as i understood him it is the column not the section – so my way was to give the ID to the column.
    The column has the parallax attribute. And i think he is talking about the parallax effect on element itself – not the background-image of the column. there is no option for that on columns.

    I tested it on an existing testpage of mine ( so the codes there have nothing to do with the solution here ). but see the right column with that image.

    https://webers-testseite.de/8col-flex/
    see what happens when hamburger is active – the direction is then the other way round (+50)

    my fault is that i do not preserve the rest of the existing settings – here a corrected code:

    function my_custom_all_parallax_settings_preserving_others() {
    ?>
    <script>
    window.addEventListener("DOMContentLoaded", function () {
        const container = document.getElementById('myID1');
    
        if (container) {
            // 1. Get the current value of the data-parallax attribute
            const currentParallaxData = container.getAttribute('data-parallax');
    
            // 2. Parse the string into a JavaScript object
            let parallaxObject = {};
            try {
                // Attempt to parse existing data. If it's empty or invalid, start with an empty object.
                parallaxObject = JSON.parse(currentParallaxData || '{}');
            } catch (e) {
                console.error('Error parsing existing data-parallax attribute:', e);
                // If parsing fails, ensure parallaxObject is an empty object to avoid errors
                parallaxObject = {};
            }
    
            // 3. Define the changes you want to apply.
            //    Only the properties listed here will be updated or added.
            //    Existing properties not listed here will be preserved.
            const changesToApply = {
                "parallax": "bottom_top",       // Standard Parallax 
                "parallax_speed": "-150",       // Standard Parallax Speed
    
                "av-desktop-parallax": "bottom_top", // Desktop 
                "av-desktop-parallax_speed": "-100",  // Desktop: Speed
    
                "av-medium-parallax": "bottom_top",  // Medium Tablet
                "av-medium-parallax_speed": "50",   // Medium Tablet Speed
    
                "av-small-parallax": "no_parallax", // Parallax off
                "av-small-parallax_speed": "no_parallax", // no speed needed
    
                "av-mini-parallax": "no_parallax", // Mobil Parallax 
                "av-mini-parallax_speed": "no_parallax" // No Speed needed
                // Do NOT include "parallax-container" here, as we want to preserve its original value
            };
    
            // 4. Merge the changes into the existing parallaxObject.
            //    Object.assign() overwrites existing properties and adds new ones.
            //    Properties in 'parallaxObject' that are NOT in 'changesToApply' will remain untouched.
            Object.assign(parallaxObject, changesToApply);
    
            // 5. Convert the modified object back into a JSON string
            const newParallaxData = JSON.stringify(parallaxObject);
    
            // 6. Set the new value of the data-parallax attribute
            container.setAttribute('data-parallax', newParallaxData);
    
            console.log('Data attribute for parallax settings updated successfully!');
            console.log('New data-parallax value:', container.getAttribute('data-parallax'));
        } else {
            console.error('Container with ID "myID1" not found.');
        }
    });
    </script>
    <?php
    }
    add_action('wp_footer', 'my_custom_all_parallax_settings_preserving_others');

    btw: on 3. read that comment:

            // 3. Define the changes you want to apply.
            //    Only the properties listed here will be updated or added.
            //    Existing properties not listed here will be preserved.

    so if you only want to influence the desktop parallax speed then only change it in the code above and do not mention the other settings there

    #1486127

    Hi Ismael,

    Thanks so much, that worked perfectly!

    While we’re on the topic of buttons, I have another page where I’d like to keep the existing Form Color Scheme but change the button to a dark transparent style, like on the other pages. However, I can’t see an option for this in the Contact Form settings, could you please advise?

    #1486123

    Hi,

    Please remove the previous modification and replace it with the following css code, then make sure to purge the cache or clear your browser history afterward.

    #top #wrap_all .contact-form :is([type=submit], button:not([type=reset])) {
        align-items: center;
        display: inline-flex;
        gap: .5em;
        justify-content: center;
        border-radius: 100px;
        color: rgba(0, 0, 0, 0.6);
        border: 1px solid rgba(0, 0, 0, 0.6);
        background: 0 0;
        font-size: 14px;
        border-style: solid;
        border-width: 1px;
        transition: all 0.4s ease-in-out;
        padding: 9px 10px 7px;
        width: 80px;
    }

    Best regards,
    Ismael

    kurson
    Participant

    HI.

    I have a layout for the home page that looks perfect in Desktop mode but compressed in Tablet mode and looks terrible in mobile mode. The Margins or padding left and right for the rows that begin with: Working With Us is Easy and Hi. I’m Robert are the rows in question.

    Note: The row beginning with: Do Your Outdoor Areas Need a Makeover? looks very nice in all modes. I worked with Chat GPT in Appearance…Customize…CSS to resolve the layout issues for this row. Chat GPT seems unable to resolve the other two rows,

    Please review this screenshot video: https://www.awesomescreenshot.com/video/41493405?key=78aeb216a83b4cc7d4c8017d672fef92

    It presents the problem at hand.

    I would appreciate it if you could please advise me on how to fix the problems with the layout with these columns on the home page.

    #1486115
    kalla77
    Participant

    Hi
    here is a severe issue: “Taxonomy tags of masonry element incomplete”

    1: Open gwup.org
    2: Scroll down until “Vollständige Artikel”
    3: Find this list of filterable tags (taxonomy) – it is NOT COMPLETE
    4: Click on the button” “Mehr laden”
    5: NOW you see the complete list.

    See video here:
    [video src="https://www.gwup.org/temporaer/taxonomy-issue.mp4" /]

    This is a severe issue.
    Please tell us how to fix it!

    Here is the code:

    [av_masonry_entries link='category,2780,2781,2779,2782,2793,2797,2783,2784,2798,2799,2800,2801,2785,2786,2787,2788,2802,2792,2789,2803,2804,2805,2790' term_rel='' wc_prod_visible='' wc_prod_hidden='hide' wc_prod_featured='' prod_order_by='' prod_order='' date_filter='' date_filter_start='' date_filter_end='' date_filter_format='yy/mm/dd' period_filter_unit_1='1' period_filter_unit_2='year' page_element_filter='skip_current' sort='yes-tax' query_orderby='date' query_order='DESC' caption_elements='title excerpt' caption_styling='' caption_display='on-hover' img_copyright='' size='fixed masonry' orientation='' image_size='masonry' gap='large' columns='4' av-desktop-columns='' av-medium-columns='' av-small-columns='' av-mini-columns='' items='12' paginate='load_more' color='custom' custom_bg='' img_copyright_font='' av-desktop-font-img_copyright_font='' av-medium-font-img_copyright_font='' av-small-font-img_copyright_font='' av-mini-font-img_copyright_font='' img_copyright_color='' img_copyright_bg='' animation='active' animation_duration='' animation_custom_bg_color='' animation_custom_bg_color_multi_list='' animation_z_index_curtain='100' overlay_fx='active' img_scrset='' lazy_loading='disabled' av-small-hide='aviaTBav-small-hide' av-mini-hide='aviaTBav-mini-hide' alb_description='' id='' custom_class='' template_class='' av_uid='av-m7i3btdw' sc_version='1.0']

    [av_masonry_entries link='category,2780,2781,2779,2782,2793,2797,2783,2784,2798,2799,2800,2801,2785,2786,2787,2788,2802,2792,2789,2803,2804,2805,2790' term_rel='' wc_prod_visible='' wc_prod_hidden='hide' wc_prod_featured='' prod_order_by='' prod_order='' date_filter='' date_filter_start='' date_filter_end='' date_filter_format='yy/mm/dd' period_filter_unit_1='1' period_filter_unit_2='year' page_element_filter='skip_current' sort='yes-tax' query_orderby='date' query_order='DESC' caption_elements='title excerpt' caption_styling='' caption_display='on-hover' img_copyright='' size='fixed masonry' orientation='' image_size='masonry' gap='large' columns='4' av-desktop-columns='' av-medium-columns='' av-small-columns='' av-mini-columns='' items='3' paginate='load_more' color='custom' custom_bg='' img_copyright_font='' av-desktop-font-img_copyright_font='' av-medium-font-img_copyright_font='' av-small-font-img_copyright_font='' av-mini-font-img_copyright_font='' img_copyright_color='' img_copyright_bg='' animation='active' animation_duration='' animation_custom_bg_color='' animation_custom_bg_color_multi_list='' animation_z_index_curtain='100' overlay_fx='active' img_scrset='' lazy_loading='disabled' av-desktop-hide='aviaTBav-desktop-hide' av-medium-hide='aviaTBav-medium-hide' alb_description='' id='' custom_class='' template_class='' av_uid='av-m7rio00o' sc_version='1.0']

    mfg
    Andrè

    Hi,
    The plugin Header Footer Code Manager is limited and only allows HTML & JS, where WPCode allows these and PHP & CSS, in the past I tested both and found WPCode, the free version, to be much better considering that most snippets are PHP. I would recommend replacing Header Footer Code Manager with WPCode, or use a child theme.
    But since your AXE & WAVE is not reporting the change to aria-hidden correctly I don’t think that we can create a solution that will help. If you watch the DOM in the browser you will see that the aria-hidden does change on scroll. We could set the aria-hidden to false always, but then on page load you would see an error, instead of after scroll. I would hope that a real screen reader would report this correctly and recognize changes to the DOM in real time, unlike the testing tools, otherwise you may need to disable this Scroll-to-Top feature.
    To request the Dev Team to review this, please open a new Github Feature Request to place a request and follow it as the Dev Team reviews it.

    Best regards,
    Mike

    Dear Mike,

    Thank you so much for your quick help and solution suggestion. I wanted to let you know that AXE is actually a free browser extension (available for Chrome) and very easy to install and use. I tested your code after clearing the cache and restarting everything, but unfortunately, AXE still reports the same error (see screenshot at https://restaurant-weichandhof.de/support/axe.png).

    Also, this seems to be a global issue. I am currently working on making seven websites accessible, all built with Enfold, and this Scroll-to-Top-Button problem appears across all of them. It would be great to have a solution that I could apply universally or ideally have this fixed directly in the theme itself.

    I would also prefer not to use an additional plugin (like WPCode) or keep this code in the functions.php file, as I would lose the changes with the next theme update. Could you perhaps suggest a solution that works via the existing Header Footer Code Manager plugin, or maybe there is another way to solve this via theme settings or CSS/JS?

    Thank you so much again for your support!

    Best regards,
    Diana

    #1486105

    Hi,
    Thanks for your help Guenni007, but in my test it seems that only targeting the ID “#av_section_1” didn’t help, I tried adjusting to const container = document.querySelector('#av_section_1 .av-parallax-object'); to target the text in the parallax but as you pointed out it was jerky for the speed needed.
    With trial and error and AI I found that this javascript & css works well for desktop & mobile and smooths out most all the jerk from the text and background image.
    Try adding this code to the end of your child theme functions.php file in Appearance ▸ Editor:

    function move_text_in_parallax_down_on_scroll() { ?>
      <script>
      document.addEventListener("DOMContentLoaded", function () {
      const el = document.querySelector("#av_section_1 .av-parallax-object");
      const bg = document.querySelector("#av_section_1 .av-parallax");
    
      if (!el || !bg) return;
    
      const isMobile = window.innerWidth < 768;
    
      const textSpeed = isMobile ? 0.9 : 0.7;
      const bgSpeed = isMobile ? 0.3 : 0.2;
    
      let currentYText = 0;
      let currentYBg = 0;
    
      const updateParallax = () => {
        const scrollY = window.scrollY || window.pageYOffset;
    
        // Text transform
        const targetYText = scrollY * textSpeed;
        currentYText += (targetYText - currentYText) * 0.05;
        el.style.transform = translateY(${currentYText}px);
    
        // Background transform
        const targetYBg = scrollY * bgSpeed;
        currentYBg += (targetYBg - currentYBg) * 0.05;
        bg.style.transform = translateY(${currentYBg}px); // GPU accelerated
    
        requestAnimationFrame(updateParallax);
      };
    
      requestAnimationFrame(updateParallax);
    });
      </script>
      <style>
      #av_section_1 .av-parallax-object {
      position: relative;
      top: 0;
      left: 0;
      will-change: transform;
      backface-visibility: hidden;
      transform: translateZ(0);
    }
    #av_section_1 {
      position: relative;
      overflow: hidden;
    }
    #av_section_1 .av-parallax {
      background-attachment: scroll !important; /* disables fixed scroll handling */
      background-position: center center !important;
      transform: none !important;
      will-change: auto !important;
    }  
      </style>
      <?php
    }
    add_action( 'wp_footer', 'move_text_in_parallax_down_on_scroll', 99 );

    If you are not using a child theme you could use the WP Code plugin then add a new snippet, in the top right corner use the PHP snippet as the code type:
    use wpcode php snippet and activate
    and ensure that it is activated, then add the above code and save.

    Best regards,
    Mike

    #1486098

    and the parallax speed of -30% is not enough?
    only values less than -100% have that effect you described – but this option does not exist …

    (by the way – a value of -100 means that the column is quasi in fixed position )

    give a unique ID to that Column. Set all your parallax options ( -30% is not enough for you ) and set these setting by child-theme functions.php for that ID:

    function my_custom_all_parallax_settings() {
    ?>
    <script>
    window.addEventListener("DOMContentLoaded", function () {
        const container = document.getElementById('myID1');
    
        if (container) {
            // Create a new JavaScript object with ALL the desired parallax settings
            // You can customize any value here as you need it.
            const newParallaxSettings = {
                "parallax": "bottom_top",       // Standard Parallax
                "parallax_speed": "-150",       // Standard Parallax Speed
    
                "av-desktop-parallax": "bottom_top", // Desktop
                "av-desktop-parallax_speed": "-100",  // Desktop Speed
    
                "av-medium-parallax": "bottom_top",  // Medium Tablet
                "av-medium-parallax_speed": "-50",   // Medium Tablet Speed
    
                // only change those values that you can not set by Enfold Options Dialog
    
                // "av-small-parallax": "no_parallax", 
                // "av-small-parallax_speed": "no_parallax", 
    
                // "av-mini-parallax": "no_parallax", 
                // "av-mini-parallax_speed": "no_parallax" 
            };
    
            // Convert the new object into a JSON string
            const newParallaxData = JSON.stringify(newParallaxSettings);
    
            // Set the new data-parallax attribute
            container.setAttribute('data-parallax', newParallaxData);
    
            console.log('Data attribute for all parallax settings changed successfully!');
            console.log('New data-parallax value:', container.getAttribute('data-parallax'));
        } else {
            console.error('Container with ID "myID1" not found.');
        }
    });
    </script>
    <?php
    }
    add_action('wp_footer', 'my_custom_all_parallax_settings');

    However, be aware that high parallax speed values may cause the element to “jerk” while scrolling.

    Hi,

    Thanks for that. Please try the following in Quick CSS under Enfold->General Styling:

    @media only screen and (min-width: 991px) {
    .html_header_transparency #main {
      padding-top: 118px !important;
    }
    }

    Best regards,
    Rikard

    Hi,
    Please note that the Fluent Forms month field is a select div with options using this css:

    #top select {
        -webkit-appearance: none;
        border-radius: 0;
        background-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAB4AAAANCAYAAAC+ct6XAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAyJpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMC1jMDYwIDYxLjEzNDc3NywgMjAxMC8wMi8xMi0xNzozMjowMCAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvIiB4bWxuczp4bXBNTT0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtcDpDcmVhdG9yVG9vbD0iQWRvYmUgUGhvdG9zaG9wIENTNSBNYWNpbnRvc2giIHhtcE1NOkluc3RhbmNlSUQ9InhtcC5paWQ6RjBBRUQ1QTQ1QzkxMTFFMDlDNDdEQzgyNUE1RjI4MTEiIHhtcE1NOkRvY3VtZW50SUQ9InhtcC5kaWQ6RjBBRUQ1QTU1QzkxMTFFMDlDNDdEQzgyNUE1RjI4MTEiPiA8eG1wTU06RGVyaXZlZEZyb20gc3RSZWY6aW5zdGFuY2VJRD0ieG1wLmlpZDpGMEFFRDVBMjVDOTExMUUwOUM0N0RDODI1QTVGMjgxMSIgc3RSZWY6ZG9jdW1lbnRJRD0ieG1wLmRpZDpGMEFFRDVBMzVDOTExMUUwOUM0N0RDODI1QTVGMjgxMSIvPiA8L3JkZjpEZXNjcmlwdGlvbj4gPC9yZGY6UkRGPiA8L3g6eG1wbWV0YT4gPD94cGFja2V0IGVuZD0iciI/Pk5mU4QAAACUSURBVHjaYmRgYJD6////MwY6AyaGAQIspCieM2cOjKkIxCFA3A0TSElJoZ3FUCANxAeAWA6IOYG4iR5BjWwpCDQCcSnNgxoIVJCDFwnwA/FHWlp8EIpHSKoGgiggLkITewrEcbQO6mVAbAbE+VD+a3IsJTc7FQAxDxD7AbEzEF+jR1DDywtoCr9DbhwzDlRZDRBgACYqHJO9bkklAAAAAElFTkSuQmCC);
        background-position: center right;
        background-repeat: no-repeat;
        border-radius: 2px;
    }

    showing a image for the drop down giving you this:
    Screen Shot 2025 06 28 at 1.00.51 PM
    and when you click on it shows the options:
    Screen Shot 2025 06 28 at 1.02.36 PM
    since the year is not a select div with options, but a input with spans you will not see this or the same image.
    I wrote this css to override the plugin css:

    #top .numInputWrapper .arrowUp,
    #top .numInputWrapper .arrowDown {
        opacity: 1;
        display: flex;
        align-content: center;
        align-items: center;
        flex-wrap: wrap;
        margin-top: -5px;
    }
    .numInputWrapper span.arrowUp:after,
    .numInputWrapper span.arrowDown:after {
        top: 0;
        height: 14px;
    }
    #top .numInputWrapper .cur-year {
    	margin-bottom: 14px;
    }

    Screen Shot 2025 06 28 at 1.58.19 PM
    but this is about as close as we can get it, since we can not support third party plugins, if you need more help with this please ask the plugin author to examine. I don’t see any theme css causing this issue.

    Best regards,
    Mike

    #1486078

    Hi,
    Thank you for sharing your solution, but when I test our demo there are no IDs added to the mobile menu items, unless you mean a menu link with an ID to an anchor on the page. I tested in WAVE and found no errors for IDs.
    If you mean the link IDs to anchors on the page, note that the mobile menu is not created until the menu is clicked, nonetheless since most people use the same link IDs on their page for mobile and desktop, this would break their links.
    Since I can not reproduce your issue and this is beyond what we can do here, you are welcome to open a Github Feature Request to place a request and follow it as the Dev Team reviews it.

    Best regards,
    Mike

    Hey Diana,
    Thanks for the login, I added this code to your theme functions.php file:

    function change_aria_hidden_for_scroll_top_link_when_it_shows() { ?>
      <script>
    window.addEventListener('scroll', function() {
      const scrollTopLink = document.getElementById('scroll-top-link');
    
      if (!scrollTopLink) return;
    
      const style = window.getComputedStyle(scrollTopLink);
      const rect = scrollTopLink.getBoundingClientRect();
      const inViewport = rect.width > 0 && rect.height > 0;
    
      const ariaValue = (style.display !== 'none' && style.visibility !== 'hidden' && inViewport) ? 'false' : 'true';
    
      scrollTopLink.setAttribute('aria-hidden', ariaValue);
    
      const childSVGs = scrollTopLink.querySelectorAll('svg');
      childSVGs.forEach(svg => {
        svg.setAttribute('aria-hidden', ariaValue);
      });
    });
      </script>
      <?php
    }
    add_action( 'wp_footer', 'change_aria_hidden_for_scroll_top_link_when_it_shows', 99 );

    It changes the aria-hidden for the scroll-top-link and the SVG icon when it shows, from false to true.
    I tested in the browser DOM and it works. Unfortunately we don’t have access to the AXE tool as it looks like a paid tool, but I did check in WAVE. Unfortunately, while in the live browser the code works, the WAVE tool doesn’t update the DOM so it doesn’t look like it is working, perhaps this is a limitation of the free version, I don’t know.
    I tried to add this to your snippet Header Footer Code Manager plugin but it didn’t work there, the plugin seems limited, if you find this workshop for you and If you are not using a child theme you could use the WP Code plugin then add a new snippet, in the top right corner use the PHP snippet as the code type:
    use wpcode php snippet and activate
    and ensure that it is activated, then add the above code and save, after you remove it from the theme functions.php file so it will not be lost when you update.

    PS for testing this is the snippet with console log comments that I tested with that will show that the aria-hidden changes while the page is scrolled:

    function change_aria_hidden_for_scroll_top_link_when_it_shows_log() { ?>
      <script>
    window.addEventListener('scroll', function() {
      const scrollTopLink = document.getElementById('scroll-top-link');
    
      if (!scrollTopLink) {
        console.log('Element #scroll-top-link not found.');
        return;
      }
    
      const style = window.getComputedStyle(scrollTopLink);
      const rect = scrollTopLink.getBoundingClientRect();
      const inViewport = rect.width > 0 && rect.height > 0;
    
      console.log('Scroll event triggered.');
      console.log('Display:', style.display);
      console.log('Visibility:', style.visibility);
      console.log('BoundingClientRect:', rect);
      console.log('In viewport:', inViewport);
    
      const ariaValue = (style.display !== 'none' && style.visibility !== 'hidden' && inViewport) ? 'false' : 'true';
    
      console.log(#scroll-top-link is ${ariaValue === 'false' ? 'visible' : 'hidden'}. Setting aria-hidden to ${ariaValue}.);
    
      // Set on the main link
      scrollTopLink.setAttribute('aria-hidden', ariaValue);
    
      // Set on any child SVGs
      const childSVGs = scrollTopLink.querySelectorAll('svg');
      childSVGs.forEach(svg => {
        svg.setAttribute('aria-hidden', ariaValue);
        console.log('Updated child SVG aria-hidden to', ariaValue);
      });
    });
    
      </script>
      <?php
    }
    add_action( 'wp_footer', 'change_aria_hidden_for_scroll_top_link_when_it_shows_log', 99 );

    don’t use both snippets at the same time, this is just for proof of work.

    Best regards,
    Mike

    DianaLoola73
    Participant

    Dear Enfold Team,
    During accessibility testing of our website (https://restaurant-weichandhof.de) built with the Enfold theme, the AXE tool reported an issue concerning the built-in Scroll-to-Top button.
    Specifically, the tool flags an error indicating that an element with aria-hidden=”true” is focusable. This error appears when the page is scrolled before starting the test (so the Scroll-to-Top button is visible). If the page is not scrolled prior to testing, the button is not visible and the error does not appear. This suggests the issue exists on every page but is only flagged depending on test conditions. This error really appears in EVERY SITE. Is there a way to fix it by not changing the ENDOLD-php-Code (> not consistent solutions for updates) ?
    So I kindly ask you to review this ARIA issue and advise on how to ensure the Scroll-to-Top button meets WCAG 2.1 AA requirements.
    Thank you in advance for your support.
    Best regards, Diana

    Sorry for the slow response back for I have been out of the office. I’m proofing this on three browser environments all on a Mac. Safari, Chrome and Firefox. In each instance the yellow banner shows up for smartphone and tablet, but not on my desktop. I have also proofed this on a PC desktop environment using Chrome and still have the same results. I have a screenshot that I placed as a private link to show you what I’m seeing on my end. I look forward to your reply.

    Thank you.

    #1486059

    Hi,
    Try this thread.

    Best regards,
    Mike

    #1486042

    In reply to: lightbox issues

    the code snippet will work on your page for all images. Even on that graphics page.
    But if you create these images in a different way – and i see some Enfold Lightbox on paintings page we had to find then a different solution.
    But if you use the same way like on mixed media and graphics page – the code will work there too.

    But as mentioned – it would be nice to have a fallback for the bottom-bar title on lightbox. my advise – and not only for seo purpose – give an alt tag to your images via media library.

    and use that snippet with fallback alt -tag as title inside bottom-bar:

    Edit
    this checks if original image is present and if widget-text or alt is present :

    function mixed_media_lightbox() {
    ?>
    <script type="text/javascript">
    window.addEventListener("DOMContentLoaded", function () { 
    (function($){
        $('.widget_media_image').magnificPopup({
          delegate: 'img',
          type: 'image',
          removalDelay: 500,  // to allow animated closing in ms
          mainClass: 'avia-popup mfp-zoom-in mfp-image-loaded mixed-media',  
          midClick: true,
          gallery: { 
            enabled:true,
            preload: [1, 1] ,
          },
          image: {
            titleSrc: false,
            markup: '<div class="mfp-figure">'+
                      '<div class="mfp-close"></div>'+
                      '<div class="mfp-img"></div>'+
                        '<div class="mfp-bottom-bar">'+
                          '<div class="mfp-title"></div>'+
                      //  '<div class="mfp-counter"></div>'+
                        '</div>'+
                    '</div>',
            },  
            callbacks: {
              elementParse: function(item) {
                var originalSrc = item.el.attr('src');
                var fullSizeSrc = originalSrc.replace(/-\d+x\d+\./, '.');
    
                // Create a temporary image object to check whether the full resolution exists
                var img = new Image();
                img.onload = function() {
                  item.src = fullSizeSrc;
                };
                img.onerror = function() {
                  item.src = originalSrc;
                };
                img.src = fullSizeSrc;
                item.src = originalSrc;
              },
    
              markupParse: function (template, values, item) {
                var title = ''; // Initialize title as an empty string. This is our default fallback.
    
                // 1. Highest Priority: Check for content from a nearby .widget_text element
                var textWidget = item.el.closest('.panel-grid-cell').find('.widget_text');
                if (textWidget.length && textWidget.html().trim() !== '') {
                  title = textWidget.html();
                } else {
                  // 2. Second Priority: If no text widget, check the image's alt attribute
                  var altAttribute = item.el.attr('alt');
                  if (altAttribute && altAttribute.trim() !== '') { // Checks if exists AND has non-empty content
                    title = altAttribute;
                  } else {
                    // 3. Third Priority: If no alt, check the image's title attribute
                    var titleAttribute = item.el.attr('title');
                    if (titleAttribute && titleAttribute.trim() !== '') { // Checks if exists AND has non-empty content
                      title = titleAttribute;
                    }
                  }
                }
    
                // Finally, assign the title to values.title, wrapping it in <h3> ONLY if there's content
                if (title) {
                  values.title = '<h3 class="heading">' + title + '</h3>';
                } else {
                  values.title = ''; // If no title was found at all, ensure nothing is displayed
                }
              },
            },
        });
    })(jQuery);
    });
    </script>
    <?php
    }
    add_action('wp_footer', 'mixed_media_lightbox', 9999);

    And

    #top .mixed-media .mfp-image-holder .mfp-content {
      max-width: 1200px; 
      box-sizing: border-box; 
      padding-bottom: 90px; 
      vertical-align: middle; 
    }
    
    #top .mixed-media .mfp-bottom-bar {
      margin-top: -36px;
      position: absolute;
      top: 100%;
      left: 0;
      width: 100%;
      cursor: auto;
      background-color: rgba(0,0,0,0.3);
      backdrop-filter: blur(4px);
      padding: 5px 10px;
    }
    
    #top .mixed-media .mfp-bottom-bar .mfp-counter {
      right: 5px
    }
    
    #top .mixed-media .mfp-content img.mfp-img {
      width: auto;
      max-width: 100%;
      max-height: 90vh !important;
      height: auto;
      display: block;
      line-height: 0;
      box-sizing: border-box;
      padding: 40px 0 40px;
      margin: 0 auto;
    }
    
    #top .mixed-media .mfp-content .mfp-title .heading * {
      font-weight: 400 !important;
    }
    
    #top .mixed-media .mfp-content .mfp-title .heading p {
      margin: 0.3em 0;
    }
    
    #top .widget_media_image img {
      cursor: pointer;
    }
    #1486039

    Hey minhndq,
    Duplicate thread for https://kriesi.at/support/topic/flatpickr-date-picker-year-dropdown-not-displaying-in-fluent-forms/#post-1485947
    We will close this one.

    Best regards,
    Mike

    #1486036

    In reply to: lightbox issues

    this is the main crux:

    elementParse: function(item) {
              item.src = item.el.attr('src').replace( /-\d*x\d*\./, '.' );
    },

    in the callback function. The image link comes now from the src attribute.

    because of that extra class on mainClass you can individually set :
    see final solution at: https://kriesi.at/support/topic/lightbox-issues-2/#post-1486042

    #1486035

    In reply to: lightbox issues

    not familiar with site origin – but with the magnificPopup script ;)

    but you can have your own lightbox script for those pages – using the magnificPopup :

    Edit: see final solution at: https://kriesi.at/support/topic/lightbox-issues-2/#post-1486042

    your img tags have no title nor alt attributes – but we can use the following description.

    #1486027

    Hello, Yes I have desactivated the mega menu and still have the same problem. I cannot set a different menu for desktop and mobile. This is really driving me crazy, we’re considering abandoning this theme because of this major issue. From what I see on the Internet, it seems super easy and we’ve been trying to work this out for months now! I’m getting tired of this issue. Can you help please? Thx Alexandra

    #1486007

    Hi,

    This is how the site looks on an actual mobile device, identical to the desktop view:

    View post on imgur.com

    Best regards,
    Ismael

    Hey Bpelzer,

    Thank you for the inquiry.

    Adding this css code should help move the copyright text below the image, but it will create a bit of extra space below the slider.

    #presse .av-horizontal-gallery {
        padding-bottom: 120px;
    }
    
    #presse .presse-galerie .av-image-copyright {
        bottom: 0;
        left: 50%;
        transform: translateX(-50%);
        position: absolute;
        padding-top: 0;
    }
    
    #presse .presse-galerie .av-horizontal-gallery-wrap {
        overflow: visible;
        padding-bottom: 50px;
    }

    View post on imgur.com

    Best regards,
    Ismael

    #1486002

    Hi,

    Thank you for the update.

    We already set the width to 80px, but it seems to be overridden by the default styles. Try to replace the selector “.contact-form :is([type=submit], button:not([type=reset]))” with “#top #wrap_all .contact-form :is([type=submit], button:not([type=reset]))”.

    Let us know the result.

    Best regards,
    Ismael

    #1485981

    Hey faroestudio,
    Try adding this code to the end of your child theme functions.php file in Appearance ▸ Editor:

    function change_posts_titles_from_h3_to_h2_in_grid_view() { ?>
      <script>
    (function($) {
      $(function() {
        function replaceElementTag(targetSelector, newTagString) {
          $(targetSelector).each(function(){
            var newElem = $(newTagString, {html: $(this).html()});
            $.each(this.attributes, function() {
              newElem.attr(this.name, this.value);
            });
            $(this).replaceWith(newElem);
          });
        }
        replaceElementTag('.slide-entry-wrap h3.slide-entry-title.entry-title ', '<h2></h2>');
      });
    }(jQuery));
    </script>
      <?php
    }
    add_action( 'wp_footer', 'change_posts_titles_from_h3_to_h2_in_grid_view', 99 );

    If you are not using a child theme you could use the WP Code plugin then add a new snippet, in the top right corner use the PHP snippet as the code type:
    use wpcode php snippet and activate
    and ensure that it is activated, then add the above code and save.

    Best regards,
    Mike

    #1485970

    Hi,

    Thanks for the update. Please let us know if you should need any further help on the topic, or if we can close it.

    Best regards,
    Rikard

    #1485962

    Topic: Logo as SVG

    in forum Enfold
Viewing 30 results - 31 through 60 (of 141,772 total)