On Sat, 2006-03-25 at 01:30 -0800, sparkydeville wrote:
> Hi all
>
> I'm new to Django, and I'm seeing various complaints about the
> ImageField, specifically it's basic inability to work as advertised. I
> think I've tried every permutation of trying to make it accomplish the
> simple task of working as part of an "image gallery" and "image" model,
> although in my case, I need an "article" and "article image" model
> where one article can have more than one image.
>
> The basic strategy seems to be:
>
> Make the "article" class unaware of the "article image" class, and
>
> Make the "article image" class lack the "admin" meta attribute, setting
> a ForeignKey, and edit_inline=meta.TABULAR or some such. My model
> exaple is below in case this didn't make any sense to whoever is
> reading this.
>
> I'd like to know if anyone has solved this type of use-case with a
> different approach.
I am not really clear on what your "use case" is here. It looks like you
are wanting an image related to an article from the code fragment below.
Nothing too complicated and it should work.
[...]
>
> My current, cryptic error (using only default templates):
>
> TemplateSyntaxError: Caught an exception while rendering.
If you are seeing this error, it is often indicating that you a Python
exception is being thrown somewhere whilst trying to work with your
model. Because the error is reporting that the template is being asked
to process some data that is not at all like it expects. This can be the
case when an exception has been raised.
There are,in fact, a number of problems with the model you posted below.
If this is just an extract of a larger system, it will be easier if you
can trim down the example to work correctly do that we can see what you
are *exactly* trying to do, rather than having to guess about what are
typing mistakes in the email and what are mistakes in your model. See
comments below.
One way to debug these sorts of problems (where you might be having
problems with syntax or other basic Python operations at the model
level) is to try and do things at the python prompt. See if you can
create instances of your model at the prompt. Or see if you can grab
every instance from the database and list them, etc.
>
> Model stuff:
>
> class Article(meta.Model):
>
> article_title = meta.CharField(maxlength=512)
>
> def __repr__(self):
> self.article_title
This should be "return self.article_title", since __repr__ must return a
string. Returning None (as it currently does) will cause problems in
many places.
>
> class META:
>
> admin = meta.Admin(
>
> list_display = ('vol_issue', 'category', 'author',
> 'article_title'),
This cannot possible work in your current setup, since you do not have
vol_issue, category or author fields. So I suspect you have trimmed the
model without testing if your example works.
> list_filter = ['vol_issue'],
Same problem. No vol_issue field in the model.
>
> )
>
>
> class ArticleImage(meta.Model):
>
> article = meta.ForeignKey(Article, edit_inline=meta.TABULAR,
> num_in_admin=1)
>
> image_caption = meta.CharField(maxlength=256, blank=True)
> the_image =
> meta.ImageField(upload_to='/home/sparky/django_instances/gbtt/media/editorial_u\
> ploads/', core=True)
Normally, upload_to specifies a subdirectory under the MEDIA_ROOT
setting (MEDIA_ROOT is set in settings.py). A full path like
"/home/sparky/..." is probably not what you want here.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
