Matthew Dapena-Tretter

It'll persist. Define a spec and use it in the field, with the spec kwarg.

Or the id kwarg like in the docs example.

Hi @hadan! This issue was actually already raised in #252 and #253. You can check out my comments there but, in short: the "compat" module is just meant to be...

I can't think of any issues off the top of my head, but we'd have to add tests to make sure that serialization wasn't messed up at all. I guess...

There shouldn't be any problem with keeping the `original` field an `ImageField`. If you want to control _when_ the image spec file is generated, you can do that [with cache...

Does the warning actually have those `%s`s in it? You should see a message [with those replaced](https://github.com/matthewwithanm/django-imagekit/blob/b398c2cee489388b0b9471b1e94ed8f21fda0f71/imagekit/cachefiles/__init__.py#L112-L120) with the actual storage and filenames. As for that warning, it's telling you...

> Could you describe what can cause the possible situation with multiple simultaneous attempts to generate the same image? Doing anything that generates the image (`{% generateimage %}`, `file.generate()`, `file.url`,...

Sorry, haven't gotten to it yet!

I can't seem to reproduce this. What versions of Django are you using? Also, can you share any relevant configuration? Thanks!

Can you show me where `foto2_thumbnail` is being accessed? (Template, etc.)