Hello,
this is a repost of an mail I sent some days ago. Since no one replied  
and I don't think that noone has an opinion about that I dare to post  
again.

I have some problems about my blog which I would like to hear your  
opinion about.

A user should have the possibility to upload image files in an post  
(which is represented by a Model). Images can be displayed either  
seperately from the text or can be embedded in the text.
If embedded in the text [1] the user does not know the real URL when  
uploading an image (because he does not necessarily know the value of  
MEDIA_ROOT) he can't give the real URL. Therefore I somehow need to  
preprocess the text and replace the relative URL (which could be just  
the name of the image) with the complete URL.
Is this thought correct so far? Or is there a smarter way to achieve  
it? How would you do it?

The place where images are stored is determined by the value of  
MEDIA_ROOT and upload_to of the FileField. If I want to upload the  
pictures to "MEDIA_ROOT/blog/p_id" where p_id is the ID of the blog  
entry containing the FileField. How would I do that?

If I user wants to upload n pictures (n > 1): How can I provide him  
with multiple FileFields. Just creating a dozens of FileField in my  
model just in case does not seem the way to go for me. Is there a  
Django solution for a variable number of fields of the same type?  
Well, I could make just the FileField a seperat model and use a 1:n  
relationship. Any other ways?

Thanks for all your ideas and comments,

Florian


[1] like that:
![Alt text here](Image URL here "Image title here")

--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to