Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter Scardelant

    (@jtiebel)

    @adamdunnage sorry, please allow me one more question. Does this actually mean that WordPress in general is not yet able to handle the delivery of WebP images in its basic functions? Which means that other plugins also don’t work or only work partially?

    Or is it a specific problem with how your plugin interacts with the basic functions of WordPress? This is not totally clear to me and has impact on how to further act in my projects…

    If the former is the case, then I wouldn’t need to worry about alternatives for the time being if the problem is rotting in the core of WordPress and not on the plugin side…

    Thread Starter Scardelant

    (@jtiebel)

    fair. let’s see, what future brings..

    Thread Starter Scardelant

    (@jtiebel)

    hmm, very sad. Any recommendations for an alternative plugin that I can use until this is fixed? I saw the conversation about the issue startet in mid ’22. My gut feeling tells me that this won’t be solved in a few weeks, will it?

    Thread Starter Scardelant

    (@jtiebel)

    Hello Adam

    Thank you very much. As unfortunate as it is that it doesn’t work optimally, I’m delighted that the error has now been found.

    It’s so sad, because I think the plugin is totally brilliant. It does exactly what it should, no more and no less. Just as I expect from a good and lean plugin.

    Please let me ask a few more questions about this:

    1. Is there a workaround to get the webP images at least temporarily out of a featured_image post loop? What other function can I use to achieve what I want?
    2. You also tried to reproduce the error on your site yesterday. To my astonishment, it worked! Can you tell me how you did that?


    Please excuse me if I’ve been a bit long-winded here and there. I’ve been working on this issue on the side and had lost my nerve a bit in the meantime… ;-/ Sorry for that! I’m a miserable end user who just expects things to work. Shame on me! πŸ˜€ Hahaha

    Thread Starter Scardelant

    (@jtiebel)

    Yes, I encounter the same here: https://uglyarch.s1-tastewp.com/sample-page/

    I followed exactly the seps already described in the pdf.

    • This reply was modified 2 years, 2 months ago by Scardelant.
    Thread Starter Scardelant

    (@jtiebel)

    Hi Adam

    Please find attached a step by step guide, reproducing 100% how I install and configure wp and how I create the example.

    https://test.h44633.web157.dogado.net/webP/wp-content/uploads/stepguide-webP.pdf

    Hope you can find what I am doing wrong.

    Many thanks in advance! Jakob

    Thread Starter Scardelant

    (@jtiebel)

    Hi Adam

    first of all thank you for your great support and the effort you put into it to help me fix this issue.

    To be honest, this is the “black accident” that it works on your side. πŸ˜€ On the other hand, there is hope that the error can be fixed. πŸ˜€


    I have absolutely no idea how to proceed. I have now tried it on two different servers/hosting platforms. I always get the same result/error. It’s kind of strange.

    Do you see any errors/ potential conflicts or what ever in the report? And/ or do you have any tips for me on how best to proceed in order to find the error?

    Many thanks. Jakob

    PS: I save the images by default, as wordpress does, in the common folder structure with months and years.
    In the test I sent you on Friday, I didn’t change anything in the _blank theme. I installed the wordpress with one click via the webhosting panel, activated the plugin via the wp admin panel and then installed the snippets I sent.

    Thread Starter Scardelant

    (@jtiebel)

    ah, sorry, here you go:

    ` wp-core
    
    version: 6.4.3
    site_language: en_US
    user_language: en_US
    timezone: +00:00
    permalink: undefined
    https_status: true
    multisite: false
    user_registration: 0
    blog_public: 1
    default_comment_status: open
    environment_type: production
    user_count: 1
    dotorg_communication: true wp-paths-sizes wordpress_path: /var/www/vhosts/h44633.web157.dogado.net/httpdocs/wordpress
    wordpress_size: 127.76 MB (133963610 bytes)
    uploads_path: /var/www/vhosts/h44633.web157.dogado.net/httpdocs/wordpress/wp-content/uploads
    uploads_size: 3.39 MB (3554363 bytes)
    themes_path: /var/www/vhosts/h44633.web157.dogado.net/httpdocs/wordpress/wp-content/themes
    themes_size: 12.23 MB (12828879 bytes)
    plugins_path: /var/www/vhosts/h44633.web157.dogado.net/httpdocs/wordpress/wp-content/plugins
    plugins_size: 1.15 MB (1207124 bytes)
    database_size: 1.09 MB (1146880 bytes)
    total_size: 145.63 MB (152700856 bytes) wp-active-theme name: BlankSlate (blankslate)
    version: 2024.1
    author: Bryan Hadaway
    author_website: https://opencollective.com/blankslate#section-contributors
    parent_theme: none
    theme_features: core-block-patterns, widgets-block-editor, title-tag, post-thumbnails, responsive-embeds, automatic-feed-links, html5, woocommerce, menus, widgets
    theme_path: /var/www/vhosts/h44633.web157.dogado.net/httpdocs/wordpress/wp-content/themes/blankslate
    auto_update: Disabled wp-themes-inactive (3) Twenty Twenty-Four: version: 1.0, author: the WordPress team, Auto-updates disabled
    Twenty Twenty-Three: version: 1.3, author: the WordPress team, Auto-updates disabled
    Twenty Twenty-Two: version: 1.6, author: the WordPress team, Auto-updates disabled wp-mu-plugins (1) Health Check Troubleshooting Mode: author: (undefined), version: 1.9.1 wp-plugins-active (2) Health Check & Troubleshooting: version: 1.7.0, author: The WordPress.org community, Auto-updates disabled
    WebP Uploads: version: 1.0.5, author: WordPress Performance Team, Auto-updates disabled wp-plugins-inactive (2) Akismet Anti-spam: Spam Protection: version: 5.3.1, author: Automattic - Anti-spam Team, Auto-updates disabled
    Hello Dolly: version: 1.7.2, author: Matt Mullenweg, Auto-updates disabled wp-media image_editor: WP_Image_Editor_Imagick
    imagick_module_version: 1690
    imagemagick_version: ImageMagick 6.9.10-68 Q16 x86_64 2021-10-13 https://imagemagick.org
    imagick_version: 3.7.0
    file_uploads: 1
    post_max_size: 128M
    upload_max_filesize: 128M
    max_effective_size: 128 MB
    max_file_uploads: 20
    imagick_limits:
    imagick::RESOURCETYPE_AREA: 78 GB
    imagick::RESOURCETYPE_DISK: 9.2233720368548E+18
    imagick::RESOURCETYPE_FILE: 49152
    imagick::RESOURCETYPE_MAP: 78 GB
    imagick::RESOURCETYPE_MEMORY: 39 GB
    imagick::RESOURCETYPE_THREAD: 1
    imagick::RESOURCETYPE_TIME: 9.2233720368548E+18
    imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, ART, ARW, AVI, AVS, BGR, BGRA, BGRO, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CRW, CUR, CUT, DATA, DCM, DCR, DCX, DDS, DFONT, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FAX, FILE, FITS, FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, H, HALD, HDR, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JNG, JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, LABEL, M2V, M4V, MAC, MAGICK, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPEG, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, PPM, PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIFF, VIPS, VST, WBMP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV
    gd_version: bundled (2.1.0 compatible)
    gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
    ghostscript_version: 9.25 wp-server server_architecture: Linux 4.18.0-477.13.1.lve.el7h.x86_64 x86_64
    httpd_software: Apache
    php_version: 8.2.6 64bit
    php_sapi: fpm-fcgi
    max_input_variables: 8192
    time_limit: 900
    memory_limit: 512M
    max_input_time: 900
    upload_max_filesize: 128M
    php_post_max_size: 128M
    curl_version: 7.29.0 NSS/3.53.1
    suhosin: false
    imagick_availability: true
    pretty_permalinks: true
    current: 2024-03-15T16:56:23+00:00
    utc-time: Friday, 15-Mar-24 16:56:23 UTC
    server-time: 2024-03-15T16:56:21+00:00 wp-database extension: mysqli
    server_version: 5.7.41
    client_version: mysqlnd 8.2.6
    max_allowed_packet: 67108864
    max_connections: 500 wp-constants WP_HOME: undefined
    WP_SITEURL: undefined
    WP_CONTENT_DIR: /var/www/vhosts/h44633.web157.dogado.net/httpdocs/wordpress/wp-content
    WP_PLUGIN_DIR: /var/www/vhosts/h44633.web157.dogado.net/httpdocs/wordpress/wp-content/plugins
    WP_MEMORY_LIMIT: 40M
    WP_MAX_MEMORY_LIMIT: 512M
    WP_DEBUG: false
    WP_DEBUG_DISPLAY: true
    WP_DEBUG_LOG: false
    SCRIPT_DEBUG: false
    WP_CACHE: false
    CONCATENATE_SCRIPTS: undefined
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_ENVIRONMENT_TYPE: Undefined
    WP_DEVELOPMENT_MODE: undefined
    DB_CHARSET: utf8
    DB_COLLATE: undefined wp-filesystem wordpress: writable
    wp-content: writable
    uploads: writable
    plugins: writable
    themes: writable
    mu-plugins: writable
    Thread Starter Scardelant

    (@jtiebel)

    doing this, first of all I receive a message: When enabling the plugin, webp-uploads, a site failure occurred. Because of this the change was automatically reverted.

    I can force activation and get the message: The webp-uploads plugin was forcefully enabled.

    I upload a jpg and can see it in the media folder…

    all steps done. Is there a report or something like this?

    • This reply was modified 2 years, 2 months ago by Scardelant.
    Thread Starter Scardelant

    (@jtiebel)

    Here a complete blank WordPress installation.

    See example with code and result: https://h44633.web157.dogado.net/wordpress/?page_id=2

    Issue as described.. If you want I can give you access to the admin panel.

    Thread Starter Scardelant

    (@jtiebel)

    Hi Adam

    I use the example given in the guide on responsive images. I use for example image id 81, a .jpg upload with both, jpg and webP image versions available on the server (checked it before, webP are smaller than jpg etc.).

    $img_src = wp_get_attachment_image_url( 81, 'medium' );
    $img_srcset = wp_get_attachment_image_srcset( 81, 'medium' );
    ?>
    <img src="<?php echo esc_url( $img_src ); ?>"
         srcset="<?php echo esc_attr( $img_srcset ); ?>"
         sizes="(max-width: 50em) 87vw, 680px" alt="Foo Bar">

    This is what I see in the browser:

    <img src="/uploads/2024/03/f79242252abc335ecd16-800x800.jpg" srcset="/uploads/2024/03/f79242252abc335ecd16-800x800.jpg 800w, /uploads/2024/03/f79242252abc335ecd16-1100x1100.jpg 1100w, /uploads/2024/03/f79242252abc335ecd16-500x500.jpg 500w" sizes="(max-width: 50em) 87vw, 680px" alt="Foo Bar">

    Let me ask a different question. Should this code normally return webP images if they are available on the server alongside jpg versions and the browser supports webP? As I understand it, yes. In the end, however, this is not the case.

    Apart from acf, I have not installed any plugins. The WP instance is completely blank.

    Can you confirm from your experience that this should normally work? Or can you give me an example where the output works accordingly via wp_get_attachment_image()?

    Update: Loading the same image not as an attachment, but inside the post loop with the_post_thumbnail() webP images are included.

    <img width="800" height="800" src="/uploads/2024/03/f79242252abc335ecd16-800x800-jpg.webp" class="attachment-medium size-medium not-transparent wp-post-image" alt="" itemprop="image" sizes="(max-width: 768px) 1500px, (max-width: 2000px) 1500px, 1500px" decoding="async" srcset="/uploads/2024/03/f79242252abc335ecd16-800x800-jpg.webp 800w, /uploads/2024/03/f79242252abc335ecd16-1100x1100-jpg.webp 1100w, /uploads/2024/03/f79242252abc335ecd16-500x500-jpg.webp 500w" data-has-transparency="false" data-dominant-color="828282" style="--dominant-color: #828282;">

    • This reply was modified 2 years, 2 months ago by Scardelant.
    Thread Starter Scardelant

    (@jtiebel)

    Hi Adam,

    I need to come back. I further tested and have to conclude that wp_get_attachment_image() and wp_get_attachment_image_srcset() is not working as expected on my side.

    Prerequisites:
    – The plugin is installed.
    – In settings both, .jpg and .webP is activated before image upload
    – All images uploaded after Plugin Installation
    – Tested with different themes, including twentytwentythree (std. theme)

    When uploading a new .webP image, webP versions are generated in all defined sizes and wp_get_attachment_image() and wp_get_attachment_image_srcset() include the .webP versions of the images in the srcset => (check, as expected).

    When uploading a new .jpg image, both versions .jpg and webP versions are generated in all defined sizes. But both functions: wp_get_attachment_image() and wp_get_attachment_image_srcset() only include the .jpg versions of the images in the srcset! When I use the_post_thumbnail() it’s working as I expect: then both jpg. and webP versions are in the srcset.

    Why webP versions are not included in the srcset when using wp_get_attachment_image() and wp_get_attachment_image_srcset() if the original image was a .jpg and both jpg. and webP versions are available?

    Best, Jakob

    • This reply was modified 2 years, 2 months ago by Scardelant.
    • This reply was modified 2 years, 2 months ago by Scardelant.
    Thread Starter Scardelant

    (@jtiebel)

    One additional question in this context. Adding an image to a post with the std. Gutenberg block “Image”, I get no srcset and src is always set to “large”. Based on which rule this is happening? And can I influence this?

    Thread Starter Scardelant

    (@jtiebel)

    Hi Adam. Thanks much. All webP images from my test above are significantly smaller than the corresponding .jpg versions.

    Playing around with the issue to solve it myself I found out, that for example the below code is working. I get all images including the webP in the src set.

    <?php the_post_thumbnail( 'medium', array( 'itemprop' => 'image', 'sizes' => '(max-width: 768px) 800px, 1500px') ); ?>

    Further I switched back from my custom theme to a WP Std. theme to make sure that the problem is not coming from this. Here we go. Using twentytwentyfour for example, the issue is solved. Something seems to be wrong with my template… I have to dive into it…

    As far as I see the plugin is working properly as expected.

    Thread Starter Scardelant

    (@jtiebel)

    Hi together

    fist of all thank you for your quick replies.

    I tried, but failed. I see only .jpg in the image srcset, but not the .webP files.

    <?php
    if ( have_posts() ) :
        while ( have_posts() ) : 
            the_post();
    
            $featured_image = wp_get_attachment_image(
                get_post_thumbnail_id(),
                'full', 'medium', 'thumbnail', 
                false,
                array(
                    'class' => 'post-image', 
                    'srcset' => true,
                )
            );
    
            echo $featured_image;
    
        endwhile;
    endif;
    ?>
    

    the plugin is doing a good job and creates webP files when uploading new images. I see them in the upload folder.

    However, they do not show up in the srcset on frontend:

    <img 
        width="2560" 
        height="1707" 
        src="/wp-content/uploads/2024/03/dackel-postcard-scaled.jpg" 
        class="attachment-full size-full not-transparent" 
        alt="" 
        thumbnail="" 
        decoding="async" 
        fetchpriority="high" 
        srcset="
            /wp-content/uploads/2024/03/dackel-postcard-scaled.jpg 2560w, 
            /wp-content/uploads/2024/03/dackel-postcard-800x533.jpg 800w, 
            /wp-content/uploads/2024/03/dackel-postcard-1100x733.jpg 1100w, 
            /wp-content/uploads/2024/03/dackel-postcard-500x333.jpg 500w, 
            /wp-content/uploads/2024/03/dackel-postcard-768x512.jpg 768w" 
        sizes="(max-width: 2560px) 100vw, 2560px" 
        data-has-transparency="false" 
        data-dominant-color="e0ddb9" 
        style="--dominant-color: #e0ddb9;"
    >

    Sorry, hope you can further assist on this. I am not a wp professional – I do my very best.

Viewing 15 replies - 1 through 15 (of 15 total)