Viewing 15 replies - 1 through 15 (of 17 total)
  • FYI: Pinged the developer here and waiting for response. I’m moving the discussion to this thread for others to pitch in.

    Plugin Author Jordy Meow

    (@tigroumeow)

    Sorry guys, I was a bit busy but definitely if there is an issue with the new WP version I will push an update ASAP.

    Which method are you both using?

    I’m currently using Retina-Images in this project.

    Thread Starter WillYurman

    (@willyurman)

    Hi Jordy,
    I’m using the HTML srcset

    thanks
    will

    I’m also in the same situation I guess. The plugin doesn’t seem to work on retina devices. I see the normal pixelized images.

    Thread Starter WillYurman

    (@willyurman)

    anyone had any luck figuring this out?
    thanks

    Looks like the author doesn’t bother.. :/

    Plugin Author Jordy Meow

    (@tigroumeow)

    The author actually bothers but if I don’t get an exact bug report and how I can reproduce it I have not idea what to do. If you can set-up a clean install of WordPress with no plugin installed on a server (except the WP Retina 2x plugin) and give me access to the admin, I will definitely look into it.

    Right now I am using WP Retina 2x with all my websites on the latest version of WordPress and it works fine.

    By the way, HTML srcset only works with latest (or beta) versions of Safari. Chrome doesn’t seem to support it yet, nor Firefox.

    After spending several hours digging into this issue, I believe my problem is my content team not uploading corresponding retina assets for the plug-in to work correctly.

    Example:
    /wp-content/uploads/2013/10/logo.png
    would also need
    /wp-content/uploads/2013/10/[email protected]
    I looks like some of these assets that are on my local server are not on production server.

    I would recommend first checking to make sure retina assets are there. Next check Chrome’s web developer tools for any console errors. In our case, it seems web content creator-errors.

    Thread Starter WillYurman

    (@willyurman)

    Great discovery Jassonee.

    Since installing the plugin, I’ve been uploading photos at 1880 pixels wide to display at 940px. And the plugin would generate a 2x version at 1880.

    Now, when I look in my content folder I have 2x images but they are all at the same size as the regular image, for example:
    11.11.2013-940×626.jpg
    11.11.2013-940×[email protected]

    All of my 2x images, even to previous to when the problem started, are now named the same size as the standard image, even though I’m uploading retina-sized versions.

    I do use Chrome. Could this be a Chrome issue? And how would it have resized all my existing retina images?

    Plugin Author Jordy Meow

    (@tigroumeow)

    The @2x file is really twice the size of the other one. Download both of then directly and compare ??

    Thread Starter WillYurman

    (@willyurman)

    You’re right Jordy. The 2x image in the content folder is twice the size. But my website is only loading the standard size. So I’m back to wondering why it won’t load the 2x version? ??

    In my case, I credit the plug-in author, Jordy for pointing me in the right direction. If you’re continuing to have issues that you can’t resolve with these steps, then I would suggest contacting him offline (https://www.totorotimes.com/about/) and get him access to your admin panel for further investigation.

    I’m indeed wondering if this issue is still related to WordPress v3.7.x upgrade or if this issue is related to something else? @thibotus01, are you still having issues, too?

    Plugin Author Jordy Meow

    (@tigroumeow)

    WillYurman > srcset is a beta feature, only Safari supports it. Did you try the HTML Rewriter? Make sure you have no caching plugin enabled at the same time.

    Thread Starter WillYurman

    (@willyurman)

    Hi Jordy,
    I switched to HTML Rewriter when you mentioned that srcset was beta and I don’t have any caching enabled.
    -Will

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Possible 3.7 conflict?’ is closed to new replies.