mrboats

On 1), how would I find the plugin that adds the asynch=asynch?

The reason is that the map in the post ends up looking like this: https://www.dropbox.com/s/q8xftg3oloxc1ej/map%20in%20amp.JPG?dl=0

Now it’s back on, only change on site was to activate Autoptimize. And the error is back. Pretty consistent..

But when I disable Autoptimize, the error goes away? As you can see now, and the only change I did was to disable autoptimize?

I contacted the Advanced Ads dev, let’s see if he can resolve the issue!

In mobile, if the mobile display is wider than the actual image, the same problem occurs. So even if the images are responsive, they should not be upsidez automatically. Note that the exact same picture in the main body of the message behaves correctly, it is only the featured image that misbahaves. You should in my view handle the featured image in the same way as regular images.

Cool

Hi, there were some advanced settings, never noted those before ;-). But no, aggregation is not set, the advanced settings are all at default values. Tried the “try-catch” option as well, no effect.

If you want to check it out, here is a test site: demo.site/en/.

H

Great, any examples with pins?

Is there then any way to show a map in AMP except making it into an image (ie without links)?

Sure, you can see it here: https://stagingsailinfinland.demo.site/2016/08/archipelago-ferry-routes-and-schedules/amp/. The Topmost image is the Featured image. The image size is 600×300 and the featured image size in the AMP settings is set to the same 600×300. In my case it has been enlarged to 1000×500 and the quality is poor.

Well, actually your picture shows exactly the problem that I have been reporting, the widget is not responsive and does not fill the width of the widget container (you can see the width of the container from the line under the widget title).

Also, if you now make the browser window a lot smaller, the widget will overflow outside the widget container and if you view the site on a mobile device, the widget will be too narrow.

So still the problem is that your widget in fact is not responsive…

Checked your plugin behavior and it seems that the problem is that your code sets the width for the span and iframe into which the widget is rendered, you can see the problem here: https://www.dropbox.com/s/t4vfymue3zf58nb/width%20problem.JPG?dl=0

• This reply was modified 8 years, 2 months ago by mrboats.

To be more exact, this applied to featured images that are enlarged to a larger size than is set in the AMP settings for AMP. Personally I think that regardless of image size, AMP should never enlage any images?

Brilliant, thanks!