Facebook, twitter etc all look for an image URL in the og tags. Currently, if you share a page which is using External Images, it does not find the correct featured image.

Update External Images plugin to set the og tags correctly. Specifically, set og:image tag.

Datafeedr and other imports from affiliate feeds frequently have multiple choices of image URLs.

A feature request has been made to modify this plugin to allow admin to choose multiple image URLs in the product meta data and for the plugin to automatically detect which URL for this product has the larger, better quality image.

It will be presumed that ‘larger’ equals better quality.

This image size comparison will occur IF this option is enabled, and IF this product has both (or multiple?) fields populated.

The image size comparison will occur only the first time the product is loaded, and from then on the external image URL will be ‘set’. To override it manually, you will then have to manually edit the external image URL field in the product editing page.

By using the External Images plugin, you forego the ability to ‘crop’ images.

This means, if you have a mix of portrait and landscape images then your product archive pages can end up looking messy.

I want to add some JavaScript and an option to the plugin to detect portrait and landscape images on archive pages, add the relevant CSS class to them and then include CSS which will automatically ensure images use the same amount of space, regardless of whether they are portrait or landscape.

 

One of the feeds we are uploading via datafeedr (Boohoo) has an “image” field but shows a blank coloured box, if you scroll down it shows a “thumbail” field with a massive image.

Is there anyway to get that field for that particular feed, without upsetting the rest of the feeds that upload without a hitch?

Rather than using CSS to control the sizes of images, some providers run timthumb or similar image sizing if parameters are passed to an image.

e.g.

http://hanwanggou.oss-cn-shanghai.aliyuncs.com/2017/07/A201602242271592361090.jpg This is the picture source file address

x-oss-process = image / resize, m_lfit, w_120, limit_1 / auto-orient, 0 This is the function of the host to process pictures, according to different values automatically handle the image size display.

As the following example:

http://hanwanggou.oss-cn-shanghai.aliyuncs.com/2017/07/A201602242271592361090.jpg?x-oss-process=image/resize,m_lfit,w_120,limit_1/auto-orient,0
http://hanwanggou.oss-cn-shanghai.aliyuncs.com/2017/07/A201602242271592361090.jpg?x-oss-process=image/resize,m_lfit,w_200,limit_1/auto-orient,0
http://hanwanggou.oss-cn-shanghai.aliyuncs.com/2017/07/A201602242271592361090.jpg?x-oss-process=image/resize,m_lfit,w_800,limit_1/auto-orient,0

An easy solution for this would be to allow users to specify different images for thumbnails vs full size images.

We already proxy images if they are not HTTP, but:

1) This uses CPU and bandwidth (but no disk space)
2) Some networks, like ASOS, prevent downloading images in this way
3) Some networks, like ASOS, are listed as HTTP images in datafeedr but actually do have HTTPS images

So I’m going to add a new feature that when it spots an HTTP image for the first time from a new domain, it will test if HTTPS works, and if so, all future HTTP image requests will be changed to HTTPS image request rather than attempting to proxy them.

I’ve tried to make External Images work automatically on ALL the themes, but there is just so much variety in theme coding out there that it’s just not possible to make it fully automatic.

Some themes correctly use the wordpress functions to grab the thumb or featured image, and in these cases, it will work perfectly straight out the box.

Other themes grab images directly from the database. In these cases, we have to filter their output and replace it with ours. Different themes place these filters on a variety of different hooks.

Other themes even remove the default actions from the main featured image hooks or thumbnail hooks and move the hooks elsewhere.

In these final two cases, to guarantee compatibility with *every* theme, we need to provide:

1. An action hook selector for where to place the featured image and a checkbox for whether we should remove other actions from this hook
2. Same as above but for thumbnail hooks
3. A filter hook selector to override thumbnail generator – we normally get this right, but this may occasionally be required

Not all themes behave in the same way. Not all of them behave in the WordPress approved way.

This feature request is to ask our users which themes they use the most and would like to see automatic compatibility for.

So – please list your theme below and we’ll get automatic configuration coded up for it.