• Open
• Yuval

  Spectator

  October 19, 2019 at 1:51 pm #44285

  

  Hi,

  I had comments from visitors of my site that my images look fuzzy, both the posts Featured Images and the front page slider images.

  Most of my images are uploaded to the Media Gallery at the resolution of 1200×600. However, after getting the complains I checked and found:

  The image in this post was reduced to 680×330 and upscaled to 950×461.
  The same happened with the Featured Image in this post which was uploaded as 1200×600.
  And so on.

  The same images were reduced in the front page slider to 400×300 and upscaled to 765×574. I’m using the theme’s built in Posts Slider. My site is OzRider.com

  Why is this happening? Why are my images being reduced then being upscaled? How can I stop this from happening? Where do I control the settings for Featured Images and Slider?

  Please advise ASAP as I do not want to lose readers or reputation.

Yuval
Spectator
Posts: 21
October 28, 2019 at 6:20 am #44328

This reply has been marked as private.
Evgeny
Keymaster
Posts: 988
October 28, 2019 at 4:18 pm #44329

There seems to be a problem with private messages – I do not get noticed when they are being sent. The logo has nothing to do with the fix, it shouldn’t be connected anyway. The file that is used for the logo doesn’t exist. Maybe the thumbnails regenerator had something to do with it. I will have a look now.
Evgeny
Keymaster
Posts: 988
October 28, 2019 at 4:45 pm #44330

Yuval, I checked – the logo has nothing to do with the theme or what I did. It does, however, have something to do with your server settings. You see, the logo on the frontend is displayed with a trailing slash. But for some reason (server settings) your images are only displayed when there is no trailing slash. It works like this: https://ozrider.com/wp-content/uploads/2019/10/OzRider_Bk_web1_3500x2100.png, but doesn’t work like this: https://ozrider.com/wp-content/uploads/2019/10/OzRider_Bk_web1_3500x2100.png/. So my solution would be to try and put this into your .htaccess:
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} /$ [NC]
RewriteCond %{REQUEST_FILENAME} .*\.(png|jpg|gif|jpeg)$ [NC]
RewriteRule ^(.*)/$ $1 [R=301,L]
This should work, but I do not want to try this without FTP access. The access you gave me leads to an empty directory instead of your website, so it is of no use, unfortunately. Try the solution I’ve given. Talking to your hosting company’s support is also a good idea. I will stress out again – this thing has absolutely nothing to do with the theme nor my changes.
Evgeny
Keymaster
Posts: 988
October 28, 2019 at 5:14 pm #44331

This reply has been marked as private.
Yuval
Spectator
Posts: 21
October 28, 2019 at 9:33 pm #44332

Thank you Evgeny. The .htaccess code fixed it and the logo now displays properly.
Do you still need the additional access requested in your last message? I get a lot of hacking attempts from that country!
Also: can you please advise what was the fix you applied for the original problem of upscaling the images?
Thanks for all your help.
Evgeny
Keymaster
Posts: 988
October 29, 2019 at 8:08 am #44333

No, if the logo is OK – then I do not need any additional access. The fix (and the only thing I did, actually) is to increase the size in pixels of images used in post thumbnails. Then, after the images are regenerated with the plugin, WordPress starts using better quality versions. It is done in functions.php. I just changed two numbers, that’s it.
Yuval
Spectator
Posts: 21
October 30, 2019 at 12:11 am #44340

Thank you Evgeny.
Are you able to send me in a private message the changes you made? This is for my reference only as I’m trying to learn how finctions.php works in WordPress.
Appreciate all your help with this issue!
Evgeny
Keymaster
Posts: 988
October 30, 2019 at 1:31 pm #44343

This reply has been marked as private.
Yuval
Spectator
Posts: 21
October 30, 2019 at 2:02 pm #44344

Thank you!
Marking this issue as resolved.
Yuval
Spectator
Posts: 21
November 2, 2019 at 12:24 pm #44347

This reply has been marked as private.

You must be logged in to reply to this topic.