Hi, I was wondering where I might find some additional documentation on how Kirby 3’s asynchronous thumb generation operates? Right now I’m troubleshooting a project with a Kirby back-end and react frontend, in which thumbs are not properly generated.
after uploading via panel, images are created in the /media folder, however they are the exact same size as the original source image, additionally json files are created in the hidden .jobs folder, but the image sizes suggested in the filename are not being generated.
Any thoughts on what might be going on?
Have you messed about with the thumbdriver settings in the config? i’ve run into the images just being moved to media without being processed when ive set the thumb driver to ImageMagick but didnt have it installed. Basically they we just passing through without getting processed at all.
I was wondering where I might find some additional documentation on how Kirby 3’s asynchronous thumb generation operates?
I’m interested in this topic, too.
Regularly, I see broken images/thumbs on newly created pages. After refreshing they appear. Since the user experience is not very nice I’d like to trigger thumb gneration programmatically (e.g. in hooks).
This might be old, but I’m totally interested in this, too …
That is absolutely true - how could I overlook that (using Janitor on many projects myself) 
Thank you!