4

After some research I found out that this problem has no simple solution (unfortunately). Check https://github.com/smcyr/Craft-FocusPoint/issues/10. A solution would be not to use eager loading (obvious). Another solution could be using Craft3 (no plugin needed). The solution I used was Focal Point (https://github.com/aelvan/FocalPointField-Craft). Focal ...


3

You’re currently passing in the image model you queried for using first() into the craft.imager.transformImage function, but you actually need to pass in the models that you get when looping through all images added to your block’s field. There’s no reason to do the first() at all, and it would add additional queries. {% if block.image|lenght %} {% for ...


2

I ran into this issue too and had landed on this thread (and another similar one). I was able to piece together a solution using the modify elements query method. I wrote a pull request that got merged, so lazy-loading works with this plugin as of version 1.1.4.


2

The migration script only converts your existing focal points as good as it can (see the repo description) but doesn't convert the fields. Since the settings that were stored in your field are now in the assets you can savely convert those fields to asset fields


1

I ran into this issue too and had landed on this thread. I was able to piece together a solution using the modify elements query method. I wrote a pull request that got merged, so lazy-loading works with this plugin as of version 1.1.4.


1

It has been answered in another thread here: enter link description here, but basically you have to use another focal point plugin called FocalPointField-Craft which then works with eager loading. And I've found also uses a lot less database queries than the other plugin too.


Only top voted, non community-wiki answers of a minimum length are eligible