Add an option/setting to catch exception when file to crop/thumbnail cannot be opened about django-versatileimagefield HOT 3 CLOSED

For the record, I ended up with monkey patching the resizing method, catching
exception when a speific setting is toggled.

This is because I wanted to have thumbnails on development when possible,
and nothing when the media files don't exists.

# myproject/apps.py

from versatileimagefield.datastructures import sizedimage
def monkeypatch_versatile_image_field():
    """
    To bypass
    https://github.com/respondcreate/django-versatileimagefield/issues/59
    we monkey patch versatile image field to silent error when
    a specific setting is toggled
    """

    def dec(func):
        def wrapper(self, *args, **kwargs):
            try:
                return func(self, *args, **kwargs)
            except FileNotFoundError:
                if settings.ALLOW_MISSING_MEDIA:
                    return
                raise

        return wrapper

    kls = sizedimage.SizedImage
    kls.create_resized_image = dec(kls.create_resized_image)

class ProjecyConfig(AppConfig):
    name = "myproject"

    def ready(self):
        monkeypatch_versatile_image_field()

This way, the monkey patching is only triggered when apps are fully loaded.

If you set ALLOW_MISSING_MEDIA to True in your settings, you won't have any
error due to FileNotFound. However, you will still have thumbnails when a media file exists.

from django-versatileimagefield.

Hey @EliotBerriot–

This is a common request (your the third person so far to what this kind of functionality)! Though I absolutely understand why you'd want that to be included the IOError-raising that you described is the expected behavior (i.e. VersatileImageField functions identically to how Django's FileField and ImageField would in the same situation). For more info, check out this comment I wrote in response to a similar issue.

from django-versatileimagefield.

Ok, thank you for the explanation, I totally understand why you're reluctant to implement a different behaviour than django's one. I'll explore the alternative you explore with create_on_demand in the issue you linked :)

from django-versatileimagefield.