Conversation
supportI am getting this error: Converted image is 0 KB and has been deleted. This usually happens because your AVIF library is not working properly. Please check the AVIF library. The page I need help with: [ log in to see the link]
Hello @harshitmediatrenz The error you are seeing indicates that your server environment is missing the necessary library to process AVIF images. Specifically, the PHP extension for processing AVIF conversion on your server needs to be compiled with AVIF support to function correctly. We recommend contacting your hosting provider and asking them to enable libavif for the PHP extension on your server. You can provide them with this technical documentation for reference. Once the library is properly installed and active, please try the conversion again and see if it works as expected. All the best,
Thanks for your support. One thing I would like to ask that your plugin generates this kind of URL (image_name.png.avif) after converting, so can we change it to this “image_name.avif”. And, if not then please explain why because I don’t want this type of URL (image_name.png.avif).
Hello @harshitmediatrenz Thank you for the question. It is a great point to bring up. CompressX is designed to generate filenames in the image_name.png.avif format. This is a deliberate design choice based on industry standards (often called NextGen rewrite mode) to ensure maximum compatibility and stability within WordPress. Here are the important technical reasons for this naming convention: First, in the original WordPress file system, files are identified by their full name, not just the “basename” without the extension. Using image_name.png.avif allows the plugin and WordPress to clearly distinguish the original source file from the converted version, preventing conflicts or bugs in the Media Library. WordPress always saves image URLs in the database as image_name.png. Themes, plugins, page builders, and media references all rely on that exact URL. If we changed the filename to image_name.avif, WordPress would not automatically recognize it, which would lead to 404 errors or broken images across your site. CompressX uses a rewrite-based delivery approach. When a user visits your site, the browser technically requests the original image_name.png URL, and CompressX’s rewrite rules automatically serve the optimized version from the compressx-nextgen directory. This ensures the best performance without breaking your site’s database structure. Based on the above, we believe that using image_name.png.avif is currently the safest and most compatible approach with WordPress core behavior. All the best,
Hello, Since we haven’t heard back from you regarding this or the libavif server extension requirement we discussed earlier, I am going to mark this thread as resolved. If you have more questions about how the plugin handles file delivery, please feel free to open a new thread or reach back out to us. All the best,
Hello @harshitmediatrenz The error you are seeing indicates that your server environment is missing the necessary library to process AVIF images. Specifically, the PHP extension for processing AVIF conversion on your server needs to be compiled with AVIF support to function correctly. We recommend contacting your hosting provider and asking them to enable libavif for the PHP extension on your server. You can provide them with this technical documentation for reference. Once the library is properly installed and active, please try the conversion again and see if it works as expected. All the best,
Thanks for your support. One thing I would like to ask that your plugin generates this kind of URL (image_name.png.avif) after converting, so can we change it to this “image_name.avif”. And, if not then please explain why because I don’t want this type of URL (image_name.png.avif).
Hello @harshitmediatrenz Thank you for the question. It is a great point to bring up. CompressX is designed to generate filenames in the image_name.png.avif format. This is a deliberate design choice based on industry standards (often called NextGen rewrite mode) to ensure maximum compatibility and stability within WordPress. Here are the important technical reasons for this naming convention: First, in the original WordPress file system, files are identified by their full name, not just the “basename” without the extension. Using image_name.png.avif allows the plugin and WordPress to clearly distinguish the original source file from the converted version, preventing conflicts or bugs in the Media Library. WordPress always saves image URLs in the database as image_name.png. Themes, plugins, page builders, and media references all rely on that exact URL. If we changed the filename to image_name.avif, WordPress would not automatically recognize it, which would lead to 404 errors or broken images across your site. CompressX uses a rewrite-based delivery approach. When a user visits your site, the browser technically requests the original image_name.png URL, and CompressX’s rewrite rules automatically serve the optimized version from the compressx-nextgen directory. This ensures the best performance without breaking your site’s database structure. Based on the above, we believe that using image_name.png.avif is currently the safest and most compatible approach with WordPress core behavior. All the best,
Hello, Since we haven’t heard back from you regarding this or the libavif server extension requirement we discussed earlier, I am going to mark this thread as resolved. If you have more questions about how the plugin handles file delivery, please feel free to open a new thread or reach back out to us. All the best,