0Logo WordpressGenere y sirva automáticamente imágenes avif con wordpress

I have spent quite a lot of time optim­ising the per­form­ance of this site, and as part of ongo­ing work I mon­it­or new tech­no­lo­gies that could help improve the speed for vis­it­ors. I’ve been track­ing the adop­tion of next-gen­er­a­tion image formats for a while and with sup­port by web browsers now fairly wide­spread it was time to fig­ure out how to make use of these new formats in wordpress.

There are mul­tiple steps required which I have broken down into head­ings below

Habilitar el soporte en nginx

The first step is to enable your web serv­er (en mi caso nginx) to recog­nise the mime types of the new formats. Para hacer esto, necesita editar mime.types que probablemente se encuentre en /etc/nginx/mime.types. I added the fol­low­ing section

/ contenido viola las reglas viola las reglas;
imagen / heif heif;
imagen / heic-secuencia heics;
imagen / vaquillas de secuencia de heif;
imagen / avif avif;
revisión de imagen / secuencia avif;
imagen / jxl jxl;

Sirva automáticamente archivos donde estén disponibles

The next step is to tell nginx to serve files auto­mat­ic­ally whenev­er they exist (and to fall back to older formats where a new format file does­n’t exist)
To do this first edit the main nginx con­fig file (usu­ally /etc/nginx/nginx.conf) and add the fol­low­ing sec­tion inside the http{} sec­tion of the config

mapa $ http_accept $ img_ext
{
   ~ imagen / jxl '.jxl';
   ~ imagen / avif '.avif';
   ~ imagen / webp '.webp';
   defecto      '';
}

Note that I am only try­ing to serve jxl (JPEG-SG) o archivos avif, podrías agregar más opciones (in order of pref­er­ence!) si lo desea.
Próximo, you need to add the fol­low­ing under the serv­er{} sec­tion of the nginx con­fig (which may be in the main con­fig file or may be in a sep­ar­ate con­fig file depend­ing how you’ve set up your nginx con­fig structure)

ubicación ~ * ^. + .(png|jpg|jpeg)$
{
   add_header Variar Aceptar;
   try_files $ uri $ img_ext $ uri = 404;
}

Now nginx will look for image.jpg.jxl and then image.jpg.avif and then image.jpg.webp and finally image.jpg when it is asked for image.jpg by any browsers that sup­port the new­er formats. A continuación, debemos habilitarlos en wordpress.

habilitar formatos de próxima generación en wordpress

Add the fol­low­ing code to your functions.php (idealmente, haga esto en un tema hijo para que cuando actualice su tema, sus cambios no se sobrescriban)

/***************************************************\
* Permitir SVG soporte y otros formatos de imagen modernos *
\***************************************************/
función cc_mime_types( $mimos )
{
   $mimos['svg'] = 'imagen / svg + xml';
   $mimos['webp'] = 'imagen / webp';
   $mimos["Violar"] = "Imagen / inexperto ';
   $mimos['heif'] = 'imagen / heif';
   $mimos['maleficio'] = "Imagen / violar la secuencia de reglas ';
   $mimos['vaquillas'] = 'imagen / secuencia de heif';
   $mimos['avif'] = 'imagen / avif';
   $mimos['darse cuenta'] = 'imagen / secuencia-avif';
   $mimos['jxl'] = 'imagen / jxl';
   volver $ mimos;
}
add_filter( 'upload_mimes', 'cc_mime_types' );

Note that I also enabled sup­port for SVG imágenes al mismo tiempo

Now you can actu­ally upload next gen format images and use them dir­ectly in word­press if you want to, but I don’t recom­mend this as many older browsers don’t sup­port them yet — and we’ve already set up nginx to serve them intel­li­gently so we should make use of that. What we want to do is to auto­mat­ic­ally gen­er­ate the new formats when we upload images (there are plu­gins that do this for webp already, but noth­ing that does it for jxl or avif yet).

Instalar libheif

This step does require access to the com­mand line of your web host, which is straight-for­ward if you run a VPS, but may not be so simple if you’re on shared host­ing in which case you might need to ask your host for support
Run the fol­low­ing bash com­mands (these are selec­ted for centos 8, oth­er dis­tri­bu­tions may be a little different)

dnf -y install --nogpgcheck https://download1.rpmfusion.org/free/el/rpmfusion-free-release-8.noarch.rpm https://download1.rpmfusion.org/nonfree/el/rpmfusion-nonfree-release-8.noarch.rpm
dnf -y install libheif

Agregue una función personalizada a wordpress functions.php para comprimir todas las imágenes cargadas (y sus miniaturas) a formato avif

As with the earli­er functions.php step I recom­mend adding this in a child theme

/*****************************\
* Convertir png y jpg a avif *
\*****************************/
add_filter( 'wp_generate_attachment_metadata', 'jps_compress_img', 10, 2 );
función jps_compress_img( $metadatos, $adjunto_id )
{
   // get filepath from id
   $filepath= get_attached_file($adjunto_id);

   // is the file a png or jpeg
   if(pathinfo($ruta de archivo, PATHINFO_EXTENSION)=="jpg" || pathinfo($ruta de archivo, PATHINFO_EXTENSION)=="jpeg" || pathinfo($ruta de archivo, PATHINFO_EXTENSION)=="png")
   {
      // Si es así, run compression of the main file to avif
      shell_exec("heif-enc $ ruta de archivo -o $ ruta de archivo.avif -q 50 -UN");
      $partes = preg_split('~ /(?=[^ /]*$)~ ', $ruta de archivo);

      // Then run compression of the thumbnails to avif
      $thumbpaths = $metadata['tamaños'];
      para cada ($thumbpaths as $key => $pulgar)
      {
          $thumbpath = $ pulgar['expediente'];
          $thumbfullpath = $ partes[0] . "/" . $pulgar;
          shell_exec("heif-enc $ thumbfullpath -o $ thumbfullpath.avif -q 50 -UN");
      }
   }
   // give back what we got
   return $metadata;
}

//dont forget to delete the avifs if the attachments are deleted
function jps_delete_avif($adjunto_id)
{
   $all_images = get_intermediate_image_sizes($adjunto_id);
   para cada($all_images como $ each_img)
   {
      $each_img_det = wp_get_attachment_image_src($attach_id,$cada_img);
      $each_img_path = ABSPATH.'wp-content'.substr($each_img_det[0],strpos($each_img_det[0],"/cargas /")).'.avif';
      shell_exec("rm -f $ each_img_path");
   }
}
add_action( 'delete_attachment', 'jps_delete_avif' );

At present that is it — all images you upload will be con­ver­ted to avif cop­ies (with the ori­gin­als retained). You can regen­er­ate all of your images to cre­ate the avif files by using a plu­gin. Note — I haven’t yet set up JPEG-XL com­pres­sion as sup­port for it isn’t avail­able in main­stream browsers yet (although it is in prerelease browsers so it is com­ing very soon).

Whilst I’m cov­er­ing next gen formats and optim­isa­tion though I have one final tip — To com­press SVG imágenes con gzip (or even bet­ter zop­fli and brotli). To do that requires anoth­er cus­tom function…

Prima: SVG compresión

/*************************************************\
* Comprimir SVG imagenes mas con brotli y zopfli *
\*************************************************/
add_filter( 'wp_generate_attachment_metadata', 'jps_compress_vectors', 10, 2 );
función jps_compress_vectors( $metadatos, $adjunto_id )
{
    // get filepath from id
    $filepath= get_attached_file($adjunto_id);

    // is the file an svg
    if(pathinfo($ruta de archivo, PATHINFO_EXTENSION)=="svg")
    {
       // Si es así, run compression of it using zopfli and brotli
       shell_exec("zopfli --gzip $ ruta de archivo");
       shell_exec("brotli --best --output = $ filepath.br $ filepath");
    }

    // give back what we got
    return $metadata;
}

Tenga en cuenta que necesitará gzip_static y brotli_static habilitados en su configuración de nginx.

Autocompilar para una versión más nueva

I found that on Cen­tos the latest ver­sion of heif-enc is 1.7 which has quite a few bugs when cre­at­ing avifs. So I opted to com­pile my own new­er (1.12) construir y usar eso en su lugar. Doing so was a little com­plic­ated as it required the aom codec as a shared lib­rary. To do so run the fol­low­ing bash com­mands. Make sure to run them as a nor­mal user, no como el usuario root. Also note some of these com­mands may not be strictly needed, it took me a while to get it work­ing and I just made a note of what worked — I am by no means a linux expert!

dnf install x265 x265-devel svt-av1
export CXXFLAGS="$CXXFLAGS -fPIC"
cd ~

git clone https://aomedia.googlesource.com/aom
mkdir -p aom_build
cd aom_build
cmake ~/aom -DBUILD_SHARED_LIBS=true
make
sudo make install
cp ./libaom.so.3 /usr/bin/local/libaom.so.3

cd ~
export PKG_CONFIG_PATH=~/aom_build/
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:~/aom_build/
export LD_LIBRARY_PATH

git clone --recurse-submodules --recursive https://github.com/strukturag/libheif.git
cd libheif
./autogen.sh
./configure
make
sudo make install

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/bin/
export LD_LIBRARY_PATH

Una vez que hayas hecho eso, make sure it works by run­ning php -a and run­ning the fol­low­ing command

shell_exec("/usr / local / bin / heif-enc -A");

You should get a full out­put, no solo un 1 error de línea. Assum­ing that works ok you can modi­fy your functions.php so that each of the shell-exec ref­er­ences points to /us­r/­loc­al/bin/heif-enc instead of just heif-enc

/*****************************\
* Convertir png y jpg a avif *
\*****************************/
add_filter( 'wp_generate_attachment_metadata', 'jps_compress_img', 10, 2 );
función jps_compress_img( $metadatos, $adjunto_id )
{
   // get filepath from id
   $filepath= get_attached_file($adjunto_id);

   // is the file a png or jpeg
   if(pathinfo($ruta de archivo, PATHINFO_EXTENSION)=="jpg" || pathinfo($ruta de archivo, PATHINFO_EXTENSION)=="jpeg" || pathinfo($ruta de archivo, PATHINFO_EXTENSION)=="png")
   {
      // Si es así, run compression of the main file to avif
      shell_exec("/usr / local / bin / heif-enc $ ruta de archivo -o $ ruta de archivo.avif -q 50 -UN");
      $partes = preg_split('~ /(?=[^ /]*$)~ ', $ruta de archivo);

      // Then run compression of the thumbnails to avif
      $thumbpaths = $metadata['tamaños'];
      para cada ($thumbpaths as $key => $pulgar)
      {
          $thumbpath = $ pulgar['expediente'];
          $thumbfullpath = $ partes[0] . "/" . $pulgar;
          shell_exec("/usr / local / bin / heif-enc $ thumbfullpath -o $ thumbfullpath.avif -q 50 -UN");
      }
   }
   // give back what we got
   return $metadata;
}

Creo que hemos perdido algo? Avísenos comentarios a continuación. Si desea suscribirse por favor utilice el enlace de suscripción en el menú en la parte superior derecha. También puede compartir esto con tus amigos mediante el uso de los enlaces sociales inferiores. Aclamaciones.

Deja una respuesta