Regenerating thumbnails result in 0 bytes avif file

Thanks for reaching out @hendrik57. While we’re unable to test out commercial plugins, when you mention the AVIF image sizes generated appear with a file size of NUL bytes, can you view a preview of these images, with an associated file size present when checking via FTP? I ask as it may be an issue with how file sizes appear within your Media Library Folders view.

I also checked their support forums, and it may be possible to sync your images after regenerating, as per this support topic.

What am I missing in the expected behavior?

After regenerating, you media library should contain images using the format type you have active. From your standard WordPress media library, is all working as expected?

I did just what you suggested, and looked through FTPs to all files. There it says 0-bytes after regenerating the thumbnails. It did with other regeratings thumnaails the same. The other formats are generated. I will look what happens if i set .webp as output. But it looks as if the regenerate routines only generate the .jpg and .png files in various formats. When uploading a new file, .avif or .webp are correct.
I will also try the ‘replace image’ function in Media Library Files Pro.

So regenerating with webp enabled generates files. After that enabling avif instead just creates zero byte files and leaves the webp version.

The WordPress debog.log does not show any errors in the log.

• This reply was modified 3 months ago by Hendrik57.

Webp files are also served as expected by WordPress (inspector, network shows that).

But avif is not shown although WPO supports that and those files exist. They can be manualy created on the linux termial, but are also created when uploading a file. Just serving them and regenerating and displaying those avif files fail.

I found it out myself.
One can generate webp and avif outside WordPress manualy. That works.
But to have the WordPress plugin do that while (re)generarting the lib-heif-dev labirary has to be compiled with Imagick and after that the PHP versions to.

So the actions on Debian server with DirectAdmin PROI should be:
With PUTTY on admin level:

sudo apt install libheif-dev libde265-dev libaom-dev libavif-dev

Then go to the browser window of DirectAdmin to the option: Compilation scripts.

There you add in the script for Imagick this line:

imagemagick_build_options=”–with-jpeg –with-png –with-tiff –with-webp –with-avif”

Then you add to the scripts of the relevant PHP versions:

–with-avif

And then you start rebuilding with the Build options of DA, first Imagick and after completion the PHP editions you want to have AVIF support.

After that it works.

The — shown before ‘with’ should be – space –

• This reply was modified 3 months ago by Hendrik57.
• This reply was modified 3 months ago by Hendrik57.
• This reply was modified 3 months ago by Hendrik57.

Appreciate you sharing your findings @hendrik57, and nice troubleshooting. This may be of particular use should other users report the same. I did perform some checks although what you experienced sounds environment specific. We’ll keep this in mind for additional reports of the same while I’ll also make the team aware of this use case.