jdriscoll/django-imagekit — Issue #58: ProcessedImageField does not process 'default' kwarg
Author: ptone
Created: 2011-11-09 06:20:13+00:00
State: open

While poorly documented, Django's ImageField supports the 'default' option for field value.

on a related note, while the value of the default is made available as the path to the ProcessedImageField, any imagespec that references will run into trouble like this:

```
Traceback (most recent call last):
File "", line 1, in
File "/Users/preston/Projects/code/forks/django-imagekit/imagekit/models.py", line 178, in url
self.generate()
File "/Users/preston/Projects/code/forks/django-imagekit/imagekit/models.py", line 191, in generate
if lazy and (getattr(self, '_file', None) or self.storage.exists(self.name)):
File "/Users/preston/UNIX/src/django-trunk-svn/django/core/files/storage.py", line 230, in exists
return os.path.exists(self.path(name))
File "/Users/preston/UNIX/src/django-trunk-svn/django/core/files/storage.py", line 246, in path
raise SuspiciousOperation("Attempted access to '%s' denied." % name)
SuspiciousOperation: Attempted access to '/Users/preston/Projects/code/fotw/project/fotw_project/static/image/missing_thumbnail.jpg' denied.
```