Use different forms for adding, changing, listing a model

Hm... I asked a question similar to this, but no one responded :( But I think I over complicated the problem. Maybe I'll try simpler way. Suppose I have two models: 1) default Django user model 2) a simple custom model like this: class RegistrationQueue(models.Model): user =

Re: Newbie question, I'm having difficulty getting the admin panel to work!

Ah, yes. You may be right. It may be a simple problem with a simple answer. Maybe I just over complicated things with too much words and explanation. Eiji On Fri, Jun 24, 2011 at 6:11 PM, Nan wrote: > > The sporadicness may have to do with the way it's being served -- that

Re: Newbie question, I'm having difficulty getting the admin panel to work!

Hi Rishi, STATIC_ROOT, STATIC_URL, etc. are somewhat new additions to Django. I have troubles with the documentation myself because the new ones describing them are in English :). But I think everything that they considered static - javascript, css, img, and other media were to be inside a

Re: Django password_change

Hi, Maybe you made a mistake, but your url says /account/password/change, but you put the password*.html files to /templates/registration. Shouldn't it be inside your project's templates/account directory? Maybe that is why you're getting a 404? Just a guess Eiji On Thu, Jun 23, 2011 at 11:53

Re: Newbie question, I'm having difficulty getting the admin panel to work!

Hello, I'm not exactly sure about your other problems, but the problem with not getting any styles seem to me like you didn't set your ADMIN_MEDIA_PREFIX correctly in your settings file and/or your web server configuration file. You must let it know how to access all the javascript, css and image

Using multiple forms to manage a model under admin

Hello, I have a question for all you django wizards. I want to use different forms for managing a model in Django's admin. I thought it's common problem, but I cannot find a good solution even after reading through google, stackoverflow and django's source code. (My apologies if this is a often

Re: MEDIA and STATIC in a nutshell?

Shawn, Thank you. For the compliment and your help. I'll try putting the static folder in my apps and try. Yes, the Japanese documentation is still stuck in 1.0, but there are other places to look. But I often use the English docs as last resort, because the language is so difficult for us. I

Re: MEDIA and STATIC in a nutshell?

Thanks Shawn, I didn't read the documentation as thoroughly as I should have. And I know that I should read the English version rather than relying on the outdated, Japanese version. But this is good, as I need to learn English more. I modified the urls.py according to the docs, and the

Re: MEDIA and STATIC in a nutshell?

Exactly. Perhaps we should just ignore MEDIA and STATIC variable setup in the settings file altogether. When I couldn't get the variables to work like how I thought they should work, I just put the following stuff in the Apache vhost config file: Alias /media /Users/eiji/Sites/assets/media Alias

MEDIA and STATIC in a nutshell?

Hi Everyone, This may seem like a very stupid question, but what exactly is the difference between MEDIA and STATIC? I read through the Django doc and it seems like STATIC is for css,js,img... etc., while MEDIA is for user uploaded files? But I'm confused because things do not work exactly like

Re: Instantiate a model using a string (or a dict)??

new_user = User(**params) > new_user.save() > # or > User.objects.create(**params) > > On Sun, May 8, 2011 at 1:44 PM, Eiji Kobayashi <itoshinom...@gmail.com>wrote: > >> Hi! >> >> Sorry. Another question, please. >> >> Is it possible to create a m

Instantiate a model using a string (or a dict)??

Hi! Sorry. Another question, please. Is it possible to create a model instance using a string parameter? Example, I would like to be able to do something like: param = "username='admin', email='x...@xyz.com', password='xyz123'" new_user = User(param) Of course this won't work. But is there a

Re: Using fields from multiple models (connected by foreign key) in the ModelAdmin

On Sun, May 8, 2011 at 12:00 AM, Oleg Lomaka wrote: > You have started from the beginning. Take a look at my very first reply in > this thread. Remove 'areacode' and 'number' fields from your MemberAdmin. > Let them be available from PhoneInline and AddressInline. You will

Re: Using fields from multiple models (connected by foreign key) in the ModelAdmin

class Member(User): >   middle_name = models.CharField(max_length=20) > >   def all_phones(self): >     return ", ".join(["(%s) %s" % (p.areacode, p.number) for p in > self.phone_set.all()]) > > # admin.py > class MemberAdmin(admin.ModelAdmin): >   list_dis

Re: Using fields from multiple models (connected by foreign key) in the ModelAdmin

      'fields': ( 'username', 'first_name', 'middle_name', > 'last_name') >                 }), >         ) > > admin.site.register(Member, MemberAdmin) > > On Sat, May 7, 2011 at 10:44 AM, Eiji Kobayashi <itoshinom...@gmail.com>wrote: > > > > > > > >

Using fields from multiple models (connected by foreign key) in the ModelAdmin

Hi! I'm having trouble figuring out what to do. I have multiple models linked together using foreignkey, like the following: # models.py class Member(User): middle_name = models.CharField(max_length=20) class Phone(models.Model): owner = models.ForeignKey(Member) areacode =