Currently, when we attempt to render an image that is not present in the filesystem, an exception is raised (ERROR - Couldn't create variation 'original' for image with id ...)
This behavior is the expected one and should not be an issue, since on normal circunstancies there should never exist references in the database to non existing binary files.

But, as a developer, it often happens that we need to update the test environment's database, without wishing to update the storage (for instance, if we just need to perform a simple verification, for which the missing image is not critical).

Ideally this behavior (raising an exception) for missing images should be configurable. By default, the behavior would be the current one, but if the developer override a specific setting, this error could be a silent one (just a warning?)