#django

it is

just a one time thing

id use the orm

okay, but that wasn't really my question though

pembo13, don't you want to set the password field to '!' in sql ?

zeograd: is that what that function does?

password is usable if set and different from '!'

which is a constant (UNUSABLE_PASSWORD) which can't be a valid hash

zeograd: that's the answer to my question then, thanks

you're welcome

another issue I have is that I am getting "Unknown password hashing algorithm" against the built-in authentication backend if a user's password is wrong

i have a custom auth backend

but if the password is wrong, it seems like the contrib.auth default backend is used, but that is consistently throwing a "Unknown password hashing algorithm"

it's using the password itself as the hash

Hi, I have problem with logout view. I'm using django.contrib.auth.views.logout, I created my own template, set LOGOUT_URL in settings, but still, if I go to address associated with logou view, it shows "django admin" logout.

i see the problem, looks like i missed a step in my read of the docs, I was setting user.password directly instead of using make_password

garretraziel: post some code, urls.py specifically

url(r'^logout/$', 'django.contrib.auth.views.logout')

or http://pastebin.com/3E4Fehju

garretraziel: i use ?next=/ on my logout link

to redirect to thepage

i want

https://github.com/django/django/blob/master/dj... <- you can see you can overide template_name if you'd like

thanks, I'll look at it

garretraziel: can you paste your logout.html too, i assume its in templates/registration/logout.html

hm, I have templates/registration/logged_out.html

tbaxter: what was that seo link i lost it?

right ok

fission6: "SEO for non-dicks"

thnaks

garretraziel: and templates is being loaded, like you can use other templates in that folder?

is templates inside an app you have installed garretraziel

yep, templates folder is inside app folder and I am using login.html to log user in

yea i think its because you are hitting the registration folder for admin first in installed apps https://github.com/django/django/tree/master/dj...

i'd rename it to registraion/logout.html and pass that in your url {'template_name':'registration/logout.html'}

or again use ?next=/logout or whatever

ok, thanks, will try

ok, now it works, thank you

yep

in my views, if I have a "def done", and I do an if statement and call "return", does that return end the "def done" script(ie, no further lines are executed within the def)?

return exits the function.... unless it's within a "finally" clause of a try

sorry, within a try block wityh a finally clause, I mean

FunkyBob: Thanks! that explains a lot:)

basic Python

if it's in a ftry block with a finally... it exectures the finally, _then_ exits the function

FunkyBob: I tried to do the dive into python training, but I never found the time:(

Hi, I'm having a user login successfully and at the next page access request.user points to anonymous user

FunkyBob: but now that you mention "finally", I recall reading about this before, but it hasn't come up in a couple months (since I started with django).

I can confirm that at the end of the login view function the session has the user login info correctly and request.user points to the user

thiagoss: does the next page have request context?

anyone have any experience with django_rq?

tbaxter, the login page returns a redirect (302), should it need to do anything else? This code used to work on another computer.

does someone in here have experience with django-rulez? i can't get it to work with django-admin :/ i want members of a group to be able to edit only their own objects via admin. is that possible?

thiagoss: the login page is almost surely fine. My bet is either the page it's going to doesn't have requestContext, or there's a cookie problem.

This may not be a very well formulated question, so apologies in advance. I have a model which uses a `GenericRelation` to an object - let's call them Likes, for example. I also have a Tastypie endpoint setup to allow POSTing to that resource. I'd like to set up a system where users can only 'Like' an object who's class has a corresponding `likes` GenericRelation. How can something like this be achieved?

ryanisnan: so, you want ti limit what can be Liked?

FunkyBob: Essentially, yes :)

you could use a limit_choices_to on the content-type fkey

FunkyBob: Ah… I would like to do this programatically, if possible.

FunkyBob: I'm envisioning a system where, if a model has a GenericRelation to the Like object, it'd be allowed, for example.

so, not so much "programatically", as declaratively

FunkyBob: Imagine something like this: http://dpaste.com/838648/

FunkyBob: It becomes slightly problematic when I want to open source this app I'm working on - if I have limit_choices_to in my model, that's only as useful to myself.

yeah... basically a "I'll only love you if you love me back" scenario

Basically :)

so... a registration pattern?

Hmm… Perhaps. I'll be honest, I'm not entirely sure what you mean.

like with admin....

things have to register if they want to be "in it"

likes.register(myclass)

Right. http://charlesleifer.com/blog/looking-registrat...