So, I am trying out the WebP support in 4.6. First, I only got broken images, but I quickly narrowed down the problem: the images are uploaded and processed successfully, but stored without a file suffix in the uploads directory and then blocked by <ipb-protection> in the htaccess file.

So what is going on there? Why is there no file suffix? Is that intentional? Can I change it? Is it a bug? A server configuration?

 

P.S. I tried it here on the site for comparison, but it create a different issue and I couldn’t even upload the images:

 

So, I am trying out the WebP support in 4.6. First, I only got broken images, but I quickly narrowed down the problem: the images are uploaded and processed successfully, but stored without a file suffix in the uploads directory and then blocked by <ipb-protection> in the htaccess file.

So what is going on there? Why is there no file suffix? Is that intentional? Can I change it? Is it a bug? A server configuration?

 

P.S. I tried it here on the site for comparison, but it create a different issue and I couldn’t even upload the images:

I had the same issue attachments webp.
I found a reason - open your uploads directory, find a .htaccess file and remove it (or make comment definitions) - this solves the display of attached webp

regards

This is content file htaccess

#<ipb-protection>
#<Files ~ "^.*\.(php|cgi|pl|php3|php4|php5|php6|phtml|shtml|([a-z0-9]{32}))$">
#    Order allow,deny
#    Deny from all
#</Files>
#</ipb-protection>

 

Edited June 24, 20213 yr by Adlago

 

 I found a reason - open your uploads directory, find a .htaccess file and remove it (or make comment definitions)

Yes, I already said that I narrowed it down to this. But I am not going to remove a valid security feature just to show webP pictures. This is not the right solution.