TinyPNG

Hi @dillonlara115!

Thanks for reporting this. We investigated the issue and found the cause: when images were converted and replaced in html, the page builder could fail to load due to the picture-element replacement feature. We have implemented a fix. When Avada is detected, the plugin now automatically disables picture-element replacement. You can also manually resolve this by turning off Picture Replacement in the plugin settings. This fix is included in version 3.6.5, released yesterday. If you still run into anything, please let us know.

Hi there,

Thanks for reaching out! We haven’t yet tested the compatibility between the latest Bricks update (2.1.4) and TinyPNG 3.6.4. We need to run some tests on our end to replicate this conflict and see exactly what is breaking the builder. We will investigate this thoroughly and provide you with a concrete update next week.

Hi there!

Thanks for getting in touch! If you install the plugin, it will automatically compress newly uploaded images. Since your existing images were already compressed on our website, you should not use the bulk optimization tool, as it would recompress them unnecessarily.

If there are a few older images that still need compression, you can manually select just those. This guide shows how to do that: https://help.tinify.com/help/how-to-compress-existing-images-with-plugin

Hope this helps!

Hi again,

Thanks for checking in! The update you’ve been waiting for has been released as part of version 3.6.3. You can now start using the filter, and here’s some documentation to help you get started:
https://github.com/tinify/wordpress-plugin/blob/master/docs/hooks/tiny_replace_with_picture.md

Let us know how it goes, we’d love to hear your feedback!

Thanks for your input! We’ll be adding a basic filter for picture generation, you can expect it the week after.

Cheers!

Hi @ajaykasam1,

Hi there!

Good point!
If you can run this script (instructions are in the file) from the root of the WordPress installation it should be solved.

<?php
/**
 * Small script that can be passed to wp eval. It will loop over
 * every attachment, read the file size on disk and write the tinify
 * meta data so that it looks compressed. This will ensure the plug-in
 * will not pick it up for compression.
 * 
 * This file should be stored in root directory of the WordPress installation
 * 
 * usage:
 * wp eval-file tinify_mark_compressed.php
 * 
 */

if ( ! defined( 'ABSPATH' ) ) {
    // If running via wp-cli from project root:
    require_once __DIR__ . '/wp-load.php';
}

$all = get_posts([
    'post_type'      => 'attachment',
    'post_mime_type' => ['image/jpeg', 'image/png', 'image/webp'],
    'posts_per_page' => -1,
    'fields'         => 'ids',
]);

$upload = wp_upload_dir();
foreach ($all as $ID) {
    $wp_meta = wp_get_attachment_metadata($ID);
    if (! is_array($wp_meta) || empty($wp_meta['file'])) {
        continue;
    }

    $basedir = trailingslashit($upload['basedir']) . dirname($wp_meta['file']) . '/';

    $tiny_meta = [];

    // Original (size key = 0)
    $orig_file = $basedir . basename($wp_meta['file']);
    if (file_exists($orig_file)) {
        $sz = filesize($orig_file);
        $tiny_meta[0] = [
            'input'  => ['size' => $sz],
            'output' => ['size' => $sz],
        ];
    }

    // All intermediate sizes
    if (! empty($wp_meta['sizes']) && is_array($wp_meta['sizes'])) {
        foreach ($wp_meta['sizes'] as $size_name => $info) {
            $f = $basedir . $info['file'];
            if (! file_exists($f)) {
                continue;
            }
            $sz = filesize($f);
            $tiny_meta[$size_name] = [
                'input'  => ['size' => $sz],
                'output' => ['size' => $sz],
            ];
        }
    }

    if (empty($tiny_meta)) {
        // No files found so skipping
        continue;
    }

    update_post_meta($ID, 'tiny_compress_images', $tiny_meta);
}

Please let us know if you run into any trouble with this.