I think this provides a significant barrier to those trying to adopt
the language. While those that are used to mailing lists are fond of
them I don't think the general development public is nearly as
infatuated. People that might consider switching to Django from, say,
PHP or ASP.NET will
Nevermind - was overcomplicating things as always.
On Nov 12, 1:30 pm, joshuajenkins <[EMAIL PROTECTED]> wrote:
> I'm not sure how I would call it from within the template.
>
> Ideally I'd like to call it from the view so I can manipulate that
> data before passing
to the template.
I'm not sure why you quoted the "append the data" part. When I call
User the profile data isn't there unless I specifically call it,
correct?
On Nov 12, 1:24 pm, bruno desthuilliers
<[EMAIL PROTECTED]> wrote:
> On 12 nov, 22:05, joshuajenkins <[EMAIL PROTECTED]>
So I'm doing basically what Chapter 12 references in the djangobook on
how to add a profile to Users.
All is well in terms of adding users and pulling out the profile with
get_profile() on single users, but when I'm trying to pull out all
Users in my view and append the profile data, I'm lost.
That cleared it up, thanks! Great information which will definitely
help me in the future.
On Nov 6, 3:52 am, Daniel Roseman <[EMAIL PROTECTED]>
wrote:
> On Nov 6, 10:27 am, Håkan Waara <[EMAIL PROTECTED]> wrote:
>
> > 6 nov 2008 kl. 10.05 skrev Daniel Roseman:
>
> > > The problem is not with
= models.DateField() #Needs to be unique
for date on user
def __unicode__(self):
return u'%s: %s (%s)' % (AlphaEvent.project,
AlphaEvent.employee,
self.date)
On Nov 6, 12:10 am, Håkan Waara <[EMAIL PROTECTED]> wrote:
> 6 nov 2008 kl. 08.42 skrev josh
I'm sure I'm doing this wrong but can't really find an answer in the
docs or by searching.
I have two models (relative to this problem). One is called events,
one is called projects
a portion of models.py for projects looks like this:
from django.db import models
class
Sure thought I had. Dumb mistake, thanks!
--~--~-~--~~~---~--~~
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
I'm running into an issue when just starting with Django 1.0 where the
following exception is caught:
Caught an exception while rendering: no such table: django_admin_log
I've done some searching and it appears that this is common if you're
not running Django 1.0, but 0.96 or lower.
I've
Figured out what went wrong. You now have to register your models
with the admin app, which will give you access.
If anyone else that is completely awful at Django is running into the
same problem let me know and I'll go in to more depth.
On Jul 18, 11:16 pm, joshuajenkins <[EMAIL PROTEC
Just upgraded to the new trunk which includes the newforms addition to
the admin app, so obviously I'm very excited to play around with it.
Decided to port over a very very new app, which is basically just a
model definition at this point. However when I create my superuser and
log in the admin
11 matches
Mail list logo
