Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #1485887

    Hi Kreisi team,

    I’ve tried everything: perplexity, forums, trial and error: I’m not getting anywhere. I have been embedding annual reports as posts on the homepage of the http://www.kms-kleve.de website for a few years now. This year, the post image of the 2024 annual report is suddenly cut off at the top and bottom.
    I have tried the following so far:

    – Duplicating the 2022 annual report in the backend and simply replacing the images (in the same format and size)
    – Tried various settings in the Enfold blog settings
    – In WordPress, set the image sizes for import in height to ‘0’
    – Deleted image and reloaded
    – Deleted and reloaded the entire post
    – Deleted, deleted, deleted caches
    – Post recreated with Avia
    – Post recreated with the standard editor

    The image of the annual report 2024 is not displayed in the desired size – as with the other annual reports. The image should be displayed in full size like the others. What is the error? Thank you for your help!

    Best regards, Lutz

    #1485930

    Hey ellkam,

    Thanks for reaching out.

    Try to completely remove the image from the Media > Library, then add this code in the functions.php file:

    function avf_customization_modify_thumb_size( $size ) {
          $size['entry_without_sidebar'] = array( 'width' => 9999, 'height' => 9999 );
          $size['entry_with_sidebar'] = array( 'width' => 9999, 'height' => 9999 );
          return $size;
    }
    
    add_filter( 'avf_modify_thumb_size', 'avf_customization_modify_thumb_size', 10, 1 );
    

    This should set the maximum width and height of the thumbnail. Upload the image again afterward.

    Best regards,
    Ismael

    #1485942

    Hi Ismael – Great! It worked straight away. The cover image is visible again in full format. Many thanks for your quick support! (But: do I have to assume that I might have to use this snippet on my other Enfold websites as well? – Or will it be patched in the next update? Or is it perhaps not a bug at all?). Best regards, Lutz

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.