Preview
Issue #4
- Sergey Pomogaylenko
- What you called "shenanigans" is RegExp in fact. And you use transformation-link of image.
If you look in sitemap you will see that there is only original images links in it for the articles.
Besides these fit-links sometimes stretch images out (if original is less then 655px, not much but yet).
And sometimes fit-links cut original images from left and right sides (f.e. here you can see images in slideshow only with cut tv-channel logo: http://www.tvblog.it/post/1636089/sanremo-young-ospiti-anticipazioni-risultati-seconda-puntata-22-febbraio-2019)
my (original): http://media.tvblog.it/f/f73/0222_212728_sanremoyoung.jpg
yours (cut): http://th.tvblog.it/b45VJREMMm1UREG5QXG3HWddG8k=/655x437/http://media.tvblog.it/f/f73/0222_212728_sanremoyoung.jpg
I'd rather say that it is preferable to show original images and give IV-engine opportunity to define itself how to show images
- Declined by admin
- Type of issue
- IV page is missing essential content
- Reported
- Feb 23, 2019
The image src is this http://th.tvblog.it/Dn9koqgqOqfHaesFceeDtav1s4k=/fit-in/655xorig/http%3A%2F%2Fmedia.tvblog.it%2F6%2F69f%2Fimmagine.png (try open it in the browser) while your template cuts completely the first part and uses some sort of decoded string from the second part (after /655xorig/).
Don't invent stuff, there is no low/high quality image, there is only one src and no srcset.