You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of my clients had the problem, that images often did not show up correctly, when a link was shared on social media and messaging apps. It seems like that it related to the way how Kirby processes images. When a template generates a thumbnail, Kirby just creates a job-file in the media folder. The actual thumbnail is only generated, once the first HTTP request is made. This is great, because it prevents a server from crashing if a page contains a lot of thumbnails. On the flip side, this first request will take quite long and the response headers are different from when the server serves the static image. We tried to circumvent this issue by forcing Kirby into generating the thumbnail right-away. This can easily be done by querying and property, that can only be retrieved from the final image, such as the file size:
The fix has only happened a few days ago, so we need to see if it really works. Just wanted to open this issue already in case, that anyone else came across this problem. Will add a comment, if the issue persists on our end.
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up and providing such a thorough explanation @fabianmichael. I'd love to hear if the workaround you came up with fixes the issue reliably. If that is the case I'll try to add it to the plugin as quickly as possible.
One of my clients had the problem, that images often did not show up correctly, when a link was shared on social media and messaging apps. It seems like that it related to the way how Kirby processes images. When a template generates a thumbnail, Kirby just creates a job-file in the media folder. The actual thumbnail is only generated, once the first HTTP request is made. This is great, because it prevents a server from crashing if a page contains a lot of thumbnails. On the flip side, this first request will take quite long and the response headers are different from when the server serves the static image. We tried to circumvent this issue by forcing Kirby into generating the thumbnail right-away. This can easily be done by querying and property, that can only be retrieved from the final image, such as the file size:
The fix has only happened a few days ago, so we need to see if it really works. Just wanted to open this issue already in case, that anyone else came across this problem. Will add a comment, if the issue persists on our end.
The text was updated successfully, but these errors were encountered: