DjangoBot: #django

Magus-: hmmm, but am i loosing anything by not using the default form that comes with django-registration?

why would you start fresh?

subclass it...

x.x

Magus-: right, I just wasn't sure if it was intended to be subclassed ... and how the profile form would fit in, cause there would really be two forms since both registration and profile have their own forms ...

Magus-: would I be inheriting from both form?

the profile form doesn't fit

at all

you inherit from the registration form

add your fields

add your validation

all done

Magus-: ok, so essentially no need to use django-profile, correct?

has anyone used photologue?

grigora: for signup

you'd use it later

Magus-: ah ... then I would just inherit from their form to let users change their info, makes sense

Magus-: thank you

If I'm using my Django models in another non-Django application, I should be able to just define DJANGO_SETTINGS_MODULE somewhere and it should work?

Yep.

if i get this where can i see what goes wrong? NewsletterUser matching query does not exist.

i don;t understand, the class is defined in the models.py

how do we do validators now, they seem completely removed

they are removed

you validate in forms, as the forms docs show you

ok, and would this work in admin as well?

of course

Well, since the admin is just a set of forms and processing rules...

as the admin docs show, you can give a form to a ModelAdmin class

And has hooks for letting you customize those...

Even the old admin wasn't some special non-form-based system.

ok

The old validator_list attribute just set a list of validation methods which were used by the old forms system.

quick question, i'm using django.contrib.auth.views.login, and user.is_authenticated is true on the /accounts/login page, but not in the other apps (/quotes)

It was forms all the way down before. It's forms all the way down now.

what could i be doing wrong?

another thing, since my last svn update a fem models won't validate anymore, something to do with m2m fields

having to add a related name

fem/few

robvdl: related_name behavior hasn't changed at all

so if they die due to that, its been bad forever

you're only just now seeing it

hehe

when doing a query on a value, it apparently fails when the value is not found, how can i check it without failing (need to know if a user already exists or not)

anders: you likely forgot RequestContext

no RequestContext = no context processors = context is 100% empty at start

so no magic addition of 'user'

SeJo: you can catch the exception when it does fail. Im assuming you're using Model.objects.get( field=someval) and you're getting a Model.DoesNotExist exception

SeJo: or you can use .filter( field=someval) and then test for an empty set

ok thanks shadfc

Magus-, ahh, that's probably it :) thanks

SeJo: if you will only ever have 1 or 0 results, use get (it complains if > 1 returned). If you'll have more than one result at some point, then use filter

well, i guess get complains on zero as well, but itll throw a diff exception when more than 1 are returned

Jacolyte: It appears that your code is trying to use a named URL pattern, which doesn't exist.

hello

i followed all documentation

and I don't know what is the whole difference between project and app

_azeth_: A project is a collection of apps.

in exmplae i have a site that consists of login system and stats system

how should i divide it into apps

?

_azeth_: You could have a login "app" and a "stats" app..but you really don't need a "login" app, as Django provides authentication/authorization for you.

but even site with only login system must contain one app to work

each app is a logical unit

i know

_azeth_: a site that does nothing but accept a login isn't a site...

what would you view? nothing?

i had only example

has anyone used photologue

with success...

Looking at photologue, it appears that it IS defining a named URL for 'pl-gallery'...odd.

is that after you create a gallery or what

Because

I created a gallery, uploaded a photo.. put the photo in the gallery (all within the admin interface)

url(r'^gallery/(?P<slug>[\-\d\w]+)/$', 'object_detail', {'slug_field': 'title_slug', 'queryset': Gallery.objects.filter(is_public=True), 'extra_context':{'sample_size':SAMPLE_SIZE}}, name='pl-gallery'),

That's just looking at the SVN copy

i have a site where on the same page is menubar with login panel and content from user profile

Jacolyte: It shouldn't be dependent on whether or not a gallery is added..it's just a named URL, that's all.

well where does it lead to? a gallery right?

HttpResponseRedirect should redirect me to a page right? (after submitting my form?)

right

oh, i understand my mistaken understanding

so it should depend on a gallery being made...

Jacolyte: not necessarily.

sorry for spam and wasted bandwidth

Well...the function call that is generating the error (and the URL) IS defined in the model for a gallery.

Jacolyte: And you ARE including the urls.py for photologue, right?

If i still get the original page, HttpResponseRedirect('/v2/newsletter/exists/')

then that one isn't called?

does autodiscover() take care of that?

Jacolyte: No.

Jacolyte: That's for admin

It's in my installed apps

that's nice

are you including the urls or not?

which is all the readme says to do

no

then the readme is stupid

you always have to include urls