summitsips

Thanks so much for replying with an explanation. I was hoping that was the case. I saw the additional update (already installed it) which took care of this. I suppose depending on timing, many of us might not have run into this the way I did.

In any case, I am a big fan of this plugin for its simplicity, especially for the retina readiness, and now I am even more impressed with the honest and fast support.

Fair enough. Your update seems to have fixed the problems. Thanks!

No. I don’t have that one. I noticed that I can use the client side setting without issue, so this appears to be limited to srcset. Also, when the white screen happens, my page source looks like it only contains header details–no actual blog content. If it’s a library issue that would make sense, as it stops before any of my content appears.

Tonight I also noticed I cannot generate thumbnails while 2.0.4 is enabled. I turned it back on and set it to client side to avoid the white screen problem. Then I tried regenerating the images for one of my earlier posts and it just clocks using regenerate thumbnails button in media library (plugin) even WP Retina 2x media list won’t generate them. It lets me click generate and it looks like it starts but never finishes.

If I disable WP Retina 2x plugin, I can regenerate thumbnails again.

I don’t seem to have access to my php error log.

Changelog says 2.0.6 but all I can see is 2.0.4 available. Had to disable the plugin due to white screen too.

I have a similar problem on a site using the bytesforall Montezuma theme. On images within pages, or on theme elements, we have retina, but within posts (both single and multi-post pages) no retina images appear with picturefill. They work if I set to using the client side js, but I like the performance of picturefill. I can’t see why the JavaScript method works but picturefill doesn’t. This is only on images within posts.

Looks like this happens with double quotes too.

Are you sure you are loading retina.js in the header?

I may have found the source of my problem, but it’s the footer, not the header at fault.

My site wasn’t loading the wp_footer() for some reason. My theme has settings to configure the footer that may have appeared in a recent theme update. I had to enable a theme option to ‘display queries’–a debug option–in my footer settings, and when I did that, my footer started to display. I turned this setting back off again and the footer remains.

Then, I noticed in the source code that with my footer loading, there’s now a call to the retina.js script. It seems that the client side script loads from the footer. Is that right? Would it start replacing images with 2x if it were loading in the header? Should it be in the header as you thought or doesn’t it matter?

That’s right. If I don’t add it manually as a header insert, the plugin won’t add it automatically.

I am using a pretty popular theme: Atahualpa. Everything is up to date with latest releases.

I found wp_head() is called within my theme’s headers.php and I see that in the header there are other plugin scripts present such as Google Analyticator.

I’ve tried removing and reinstalling WP Retina 2x and that hasn’t worked. Any way I can see if somewhere the script is being deregistered?

Thanks for the followup! That makes a lot of sense.

Jordy,

I appreciate the feedback to WPMonkeyATL, but I am afraid those additional comments somewhat distracted from my original post. What about the first load failing? Once I am viewing my site, the retina images kick in perfectly, but the first view never has any. In other words, clear your browser cache and the first page loads without retina.