HOME › WordPress Support › Mikmag WordPress theme › Pixelated Featured Image on Blog Post.

This topic contains 4 replies, has 3 voices, and was last updated by  David Jamieson 4 days, 8 hours ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • 01/11/2012 at 9:27 PM #8902

    David Jamieson
    Subscriber

    Hi,

    I like the way the blog post displays the featured image in a banner across the top of the post. There’s just one problem… It consistently displays a low-resolution, pixelated version. The image I upload is plenty large and shouldn’t display like this. Is there something wrong with the resizing script?

    Here’s a screen shot:

    https://dl.dropbox.com/u/44561567/Screen%20Shot%202012-11-01%20at%204.22.07%20PM.png

    Any ideas?

    05/11/2012 at 3:45 PM #8933

    kevin(Staff)
    Key Master

    Hi David,

    Could you perhaps supply me with a link towards that post? Judging from this screenshot I can’t accurately tell what’s happening, I hope to be able to get some more information from the post itself and its source code.

    Kevin

    05/11/2012 at 5:29 PM #8939

    David Jamieson
    Subscriber

    Hi Kevin,

    Here’s a link to a sample post with the pixelated featured image. Let me know what you think… I appreciate the help.

    David

    06/11/2012 at 8:31 AM #8940

    Helen (staff)
    Key Master

    Hello David,

    The link to your image shows a lot of signs like %

    https://dl.dropbox.com/u/44561567/Screen%20Shot%202012-11-01%20at%204.22.07%20PM.png

    Also make sure the image is large enough

    This is an appropriate link to an featured image of a blogpost in the Mikmag theme

    http://www.responsive-wp-theme.com/wp-content/uploads/2012/06/312.jpg

    06/11/2012 at 5:04 PM #8943

    David Jamieson
    Subscriber

    Ah, I see. The image needs to be cropped to scale first. I was confused because the original image was easily large enough that it shouldn’t be pixelated at that size. Now that I’ve cropped it down, though, it looks better.

    This is reasonable, although it’s something you might want to make clearer in the documentation… It will save your users some headaches :)

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.