Hal

In case someone else has to have this … hacky workaround: use nextgen 1.9.13, install the above mentioned plugin to use WP media library images (the original images will just get copied to a gallery specific NG folder), turn off the default WP feature that adds year + month to all uploads (this will put all images in /uploads). Then create a template using the provided NG gallery.php as a model. Inside the $images loop, rework the urls like …

$image->imageURL = WP_SITEURL . '/wp-content/uploads/' . basename( $image->imageURL );

Then add the basic picturefillWP code:

`$image_output = ‘<img class=”slideimg” src=”‘ . $image->imageURL . ‘” title=”” alt=”” />’;
echo apply_filters(‘theme_acf_image’, $image_output, ‘image’);`

Seems to work so far. NG will be adding the “use images from media library” feature “soon”, they say.

To ignore jquery, tell bwp to ignore ‘jquery-core’ (works for 3.7.1). Otherwise its not ignored.

OK figured it out! Its a WP gotcha with how images get uploaded and hardcoded with the uploader’s domain.

In our development model we have 3 environments and domains: local developer (eg example.loc), staging and production. Because of the WP practice of hardcoding domains, we typically try to only upload images during development via the staging site, or else they get tagged like example.loc/some.jpg, and thus are only visible to developers working locally. When uploaded to staging, they are visible to both environments. (Then when we go live we have to fix things).

I was able to readily reproduce the “partial output” scenario depending on what domain images are uploaded from. So for us, uploading to staging site works fine if site is then loaded from the staging url. But just get the partial output if the exact same code is viewed locally (example.loc).

I didn’t dig deep enough to see why picturefill.wp starts to build correct looking html, then seems to bails out, but I’m convinced that’s the root cause. FYI.

OK, deleted that image (again), and started over. All seems to work well now! We had done that at least once before so still curious what the difference is now. Thanks.

OK, quick update … tried a different image, with everything else the same, and that seemed to work! That was a dummy image. Tomorrow, I will go through and replace what’s there so far, and see if that gets us where we want to be. I’d still be curious to learn why the existing images aren’t working fully? Strange.

Also, on unrelated note, ACF allows images to be defined 3 ways. I would suggest adding to ACF documentation that images need to be declared as “Image Object”. That has all the size data.

Yea, I’d be glad to. No problem whatsoever. In the meantime, I’ll try the latest release. Thanks.

Thank you sir! If anything I can do, let me know.

Sure thing! I see there is a 1.2.5 now on www.remarpro.com. Sadly, I am still seeing the same output, just one size being echoed:

<section class="entry-content clearfix slide">
  <span data-id="slideimg" data-title="element-home-page-h-14" data-picture="">
      <span data-src="https://test.loc/wp-content/uploads/2013/10/element-home-page-h-14-768x511.jpg">
          <img id="slideimg" title="element-home-page-h-14" src="https://test.loc/wp-content/uploads/2013/10/element-home-page-h-14-768x511.jpg">
       </span>
      <noscript><img id="slideimg" src="https://test.loc/wp-content/uploads/2013/10/element-home-page-h-14-768x511.jpg" title="element-home-page-h-14" alt="" /></noscript>
</span>

Thanks for having nice plugin!

Yes, acf image field type. And the code is as you’ve presented. Sounds good.

Sorry, that error was a setting unrelated to smushit. Back to the “bad response from smush.it” now.

I was able to match one occurrence of this with the server logs. Today it was an ipad that caused it. We have ipads disabled in WPTouch.

This site really has no blog. All pages. No comments.

Pro.

Under Advanced:
– mod_rewrite
– compress
– don’t cache known users
– Cache rebuild ….
– Mobile device support on

Nothing under Preload.

The /mobile-home is a WP “page” created specifically as the front page for the mobile version of the site. WPTouch is configured to used that page and ignore the WP default (in the wptouch configs).

Nope. Does that disable caching, or do something else? I read that in the wptouch docs, but it sounded like it disabled caching altogether, which is not my objective. Thx.