2016-01-16 14:19:05 +01:00
.. _custom_image_model:
2016-10-13 11:55:21 +02:00
===================
2016-01-16 14:19:05 +01:00
Custom image models
===================
The `` Image `` model can be customised, allowing additional fields to be added
to images.
To do this, you need to add two models to your project:
- The image model itself that inherits from
2017-11-17 12:17:58 +01:00
`` wagtail.images.models.AbstractImage `` . This is where you would add
2016-01-16 14:19:05 +01:00
your additional fields
- The renditions model that inherits from
2017-11-17 12:17:58 +01:00
`` wagtail.images.models.AbstractRendition `` . This is used to store
2016-01-16 14:19:05 +01:00
renditions for the new model.
Here's an example:
.. code-block :: python
# models.py
from django.db import models
2016-10-13 11:55:21 +02:00
2017-11-17 12:17:58 +01:00
from wagtail.images.models import Image, AbstractImage, AbstractRendition
2016-01-16 14:19:05 +01:00
class CustomImage(AbstractImage):
# Add any extra fields to image here
# eg. To add a caption field:
2016-01-12 20:35:00 +01:00
# caption = models.CharField(max_length=255, blank=True)
2016-01-16 14:19:05 +01:00
admin_form_fields = Image.admin_form_fields + (
# Then add the field names here to make them appear in the form:
# 'caption',
)
class CustomRendition(AbstractRendition):
image = models.ForeignKey(CustomImage, related_name='renditions')
class Meta:
unique_together = (
2016-11-14 19:28:28 +01:00
('image', 'filter_spec', 'focal_point_key'),
2016-01-16 14:19:05 +01:00
)
2017-02-10 17:29:02 +01:00
.. versionchanged :: 1.10
2016-01-16 14:19:05 +01:00
2017-02-10 17:29:02 +01:00
In previous versions of Wagtail it was necessary to connect signal handlers to handle deletion of image files. As of Wagtail 1.10 this is now handled automatically.
2016-01-16 14:19:05 +01:00
2016-01-12 20:35:00 +01:00
.. note ::
Fields defined on a custom image model must either be set as non-required
(`` blank=True `` ), or specify a default value - this is because uploading
the image and entering custom data happen as two separate actions, and
Wagtail needs to be able to create an image record immediately on upload.
2016-01-16 14:19:05 +01:00
Then set the `` WAGTAILIMAGES_IMAGE_MODEL `` setting to point to it:
.. code-block :: python
WAGTAILIMAGES_IMAGE_MODEL = 'images.CustomImage'
.. topic :: Migrating from the builtin image model
2017-02-16 18:11:37 +01:00
When changing an existing site to use a custom image model, no images will
2016-01-16 14:19:05 +01:00
be copied to the new model automatically. Copying old images to the new
model would need to be done manually with a
`data migration <https://docs.djangoproject.com/en/1.8/topics/migrations/#data-migrations> `_ .
Any templates that reference the builtin image model will still continue to
work as before but would need to be updated in order to see any new images.
2016-10-13 11:55:21 +02:00
2016-10-13 15:54:34 +02:00
.. _custom_image_model_referring_to_image_model:
2016-10-13 11:55:21 +02:00
Referring to the image model
============================
2017-11-17 12:17:58 +01:00
.. module :: wagtail.images
2016-10-13 11:55:21 +02:00
.. autofunction :: get_image_model
.. autofunction :: get_image_model_string