[NSFW] The conversion doesn’t work on all images (?) Seems random (?)

Hi @testingmoon,

Thanks for your message.

Please read the plugin FAQ, especially question “Why are some images not in WebP?”. There you will find the answer to your question.

Best,
Mateusz

Mateusz Gbiorczyk I’m sorry I should’ve been more clear and I have read throughout your FAQ :).

As you can see in my settings – I have specifically unchecked “Automatic removal of WebP files larger than original” as I presumed for this to be the issue; however – it is not.

Now allow me to give you a clear example of this; the image below (325kb) is one of the ones not getting converted (even after forcing it): https://leakingirls.com/wp-content/uploads/2021.03.20/marymoody%20masturbating%20000729-640×360.png (for some reason this website is not formatting the link correctly – in order to see the image just replace the “x” with an actual “X” –> https://i.imgur.com/1FwyOwU.png

However if you manually convert this image using some random WebP online converters the size becomes 28kb: https://www.online-convert.com/result#j=92306534-df35-41bf-9bfd-be002b925314 OR check this for direct comparison https://i.imgur.com/BDToSZD.png

• This reply was modified 3 years, 11 months ago by testingmoon.
• This reply was modified 3 years, 11 months ago by testingmoon.
• This reply was modified 3 years, 11 months ago by testingmoon.
• This reply was modified 3 years, 11 months ago by testingmoon.

@testingmoon In my opinion, these are spaces in the URL, eg “part 1 000801-640×360.png”. At this point, the plugin is unable to correct the detection of this URL.

Try to use via .htaccess mode. This solution works best.

Hey thanks for responding again. I’m not so sure if it’s to do with spaces and I am able to see the converted files via FTP (it’s just that for some reason the plugin/server is deciding not to use the converted WebP files):

View post on imgur.com

I’d like to avoid editing the .htaccess file (as you said yourself it’s for advanced users and should try to avoid this route).

• This reply was modified 3 years, 11 months ago by testingmoon.
• This reply was modified 3 years, 11 months ago by testingmoon.

@testingmoon The via .htaccess mode is the basic and recommended solution. You don’t need to edit anything – the plugin will modify .htaccess files by itself.

I tried to but I’m getting:

Error codes: bypassing_apache

View post on imgur.com

@testingmoon Then please contact your server Administrator or eliminate spaces from URLs.

Thanks again – very helpful. I reached out to them but I wasn’t sure if I needed to mention any other important details? I just told them about the plugin name and the error message I was getting.

@testingmoon You have all the relevant information in the error message.

This is what they got back to me with:

htaccess is enabled on the server.
You have Nginx + apache installed.
In this case, htaccess works.
Check your script or contact the developer.

@testingmoon The plugin is working properly. As you know, it is used by over 50,000 users and it works for them.

This error is not that .htaccess is not working. Unfortunately, this answer shows that your server Administrator does not have the appropriate knowledge.

Hey Mateusz,

They got back to me with below and I would be inclined to agree; although some of it (what they said) is a bit silly and quite obvious (them suggesting me to rename .htaccess).

I know it’s not ideal for us to be asking for anything from you since you are literally providing this plugin and your answers free – which is honestly understated how helpful and appreciated it is. I would be more than happy to donate 20$ towards your plugin if you’re able to assist me with this issue. Could you please elaborate at all as to how it may be resolved so I can pass it onto the administrators?

If htaccess rules weren’t working, your website wouldn’t be able to utilize WordPress rewrites. And yet, it does. You can actually check it yourself – rename the .htaccess file to something else, and all website links will yield a 404 error.

That said, we will be quite grateful if the plugin author shares the appropriate knowledge to fix the issue because it’s not related to htaccess.
If you have any questions, please, let me know.

• This reply was modified 3 years, 11 months ago by testingmoon.
• This reply was modified 3 years, 11 months ago by testingmoon.

@testingmoon The problem is not that the rules in .htaccess files do not work. The problem is that the server, when you load static files (you go to the URL of a .jpg or .png file or other media files) loads them directly as Nginx and not as Apache. This is to speed up the loading of static files, but then the rules in the .htaccess file do not work.

In summary, the rules in .htaccess files do not only work when loading static media files directly. And this must be turned off.

Okay so I did everything that you suggested/advised. The server admins were able to take care of the issue. So after this I was getting “rewrites_cached” issue and I implemented a rule in cloudflare to temporarily stop caching. This in return resolved in no more issues being displayed on your plugin page.

So I figured – YAY! FINALLY! I can force a conversion on all those images… Well this process somehow reverted back even those successfully converted random images from .webp back to their original format. So somehow the plugin is completely dead without any error message.

• This reply was modified 3 years, 11 months ago by testingmoon.
• This reply was modified 3 years, 11 months ago by testingmoon.

@testingmoon I am very glad that the problem was solved. Unfortunately, I do not understand the second part of your message. Could you please explain this further to me?