Hal

I guess no way to edit, sorry for the uncloded link.

I was just struggling with this and Woo was arbitrarily adding a ‘Any Size’ variant to my Size variations. I wasn’t wanting this so had it disabled. That was causing the above error. Enabling it AND giving it a price, solved the issue for me (does not display on the front end regardless).

Thanks, yes. Unfortunately, I need to support IE and FF now. I started using this plugin way back when because the support and documentation were both excellent at the time, even though the plugin itself was pretty new. Obviously something has happened to Kyle. That’s a real shame. There are 2 problems I have with this plugin that are unlikely to get fixed now.

What is the browser support for ricg? It looks like it uses srcset which isn’t supported by FF or IE. Does it work with those?

I have the same (or similar) issue, but its a production site for a client, and I can’t break it deliberately. I had to comment out the die() statement so it would work for non-logged in users (so it “works” now). If its helpful, I can probably let you see what’s happening for me in staging environment (probably not today though).

This is a small fraction of what I am getting now daily (and just one image). Older versions didn’t do this, I am pretty sure. What’s really wierd is the same image is getting requested repetitively. I am thinking about a downgrade.

10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1-150×150.jpg HTTP/1.0” 200 2339
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1-150×150.jpg HTTP/1.0” 200 2339
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/MikeHillock-150×150.jpg HTTP/1.0” 200 3
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/MikeHillock.jpg HTTP/1.0” 200 20361
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/MikeHillock.jpg HTTP/1.0” 200 20361
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/MikeHillock.jpg HTTP/1.0” 200 20361
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/MikeHillock.jpg HTTP/1.0” 200 20361
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/MikeHillock.jpg HTTP/1.0” 200 20361
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/MikeHillock.jpg HTTP/1.0” 200 20361
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/MikeHillock.jpg HTTP/1.0” 200 20361
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/MikeHillock.jpg HTTP/1.0” 200 20361
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/MikeHillock.jpg HTTP/1.0” 200 20361
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1-150×150.jpg HTTP/1.0” 200 2339
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706
10.181.160.186 – – [22/Dec/2014:15:16:18 -0500] “GET /wp-content/uploads/Avatar-1.jpg HTTP/1.0” 200 42706

I’ve noticed since the last update, there is a bunch of internal apache connections being made daily. It looks like its maybe part of the rebuilding the transient cache code. If you have lots of images, this can really fill up the logs quickly, as for me its causing 100’s and sometimes 1000s for internal connections at a time. Sounds like maybe its the same thing. You might try an earlier version of the plugin.

re: the next / back buttons and commenting out the die() statement … this is only necessary for non logged in users. For logged in users, it works fine, at least for me (found out the hard way). That’s probably not using the right wp ajax stuff. Tested on 2.1.3.

After upgrading to 2.1.7, instead of a “Request has failed” on back/next, I get a -1 displayed (non-logged in users only). So I reverted, commented out the die() statement (which I am not comfortable doing for security reasons). But buttons work now. There was also a missing js file in 2.1.7, in my download, jquery-qtip.js.

Sorry to say but after upgrading to 1.3.4, I still can’t get anything except all possible sizes.

Sorry to be gone for awhile but been off on other projects.

The image slider works fine. Its the image in the page content that is the problem. They are probably indeed sharing much of the same code. The way the docs read, it seemed like picturefillWP would handle the WP content images without any custom code (and seems to do that, except this situation). So I need to adapt your sample code to handle regular content images, like in page.php content? What I am looking for, is if the client inserts randomly sized images via the editor, then we handle that across varying sizes without having to write exceptions for every situation. In this case, to not include images larger than the editor specified.

Thanks for the help.

OK, I inserted a random image as a thumbnail into this page:

https://staging2.resultsbydesign.com/company/

Its the one with 2 people in hardhats below “Quirky Name”. In the editor, it is clearly the thumbnail at 480×319, but firebug is showing that picturefill grabbed a 1500×998 variant on my desktop browser.

<img alt="Jess_and_Ced_3" class="alignnone size-thumbnail wp-image-8979" width="1500" height="998" src="https://cdn.bigassfans.com/images/Jess_and_Ced_3-1500x998.jpg">

We did a bit of a tap dance to bypass the plugin, to get the layout the way the client wanted it. But this is the page: https://www.bigassfans.com/founder-and-chief-big-ass-carey-smith/. I don’t think that’s going to answer many questions. Let me do a mockup on a staging version tomorrow sometime.

Its pretty image intensive site, and overall the plugin has been great. The client wanted some images up to 2000px for larger screens.

Well, thats certainly fine, the plugin solves many more problems so occasional pothole is not so bad. Actually knowing its designed to not do this, is good news.

Let’s see … the problem surfaced recently with 1.2.6, but just now tried an upgrade to 1.3.1, and same behavior. This site has recently gone live, so there has not been a lot of client or anyone adding new content, which is how this surfaced. He was trying for a small image, with text wrapped around. I don’t think its been an issue previously (not that I am aware of anyway but there are several developers on our end and the client). I just tried creating a new WP page myself (default template), and same issue. The page template is pretty basic WP, nothing unusual there.

As to other scripts …. I don’t think so. But this site has got a lot going on, so I can’t rule that out. Other plugins, a lot going on in functions.php, etc. Thanks.

Good question. The newer gravity forms has broken up their css into at least 4 files, and loading this in the footer for some odd reason. I think they are using something like the wp_footer action, which probably is firing after bwp, so its missed. I haven’t found a way around this yet. I didn’t see the js, but maybe its the same.

If of interest to anyone, we used this code as a model for adding 2 additional image sizes for a project where we are dealing with some large images and wanted a total of 5 breakpoints. https://pastie.org/8468029