DjangoBot: #django

lucasvo: no, I'm saying that's the wrong way to do it

Magus-: would that work w/ the model calls as well

dcramer[]: uh, it'd be useless if it didn't

or do you mean can you decorate a model function

if so, no

Magus-: well your "correct" way does not convince me

nah i just want to wrap a block

ok i gotta go learn how transactions work

adding the project dir to pythonpath tends to give you confusing or unclear references

dcramer[]: what do you mean a block?

dcramer[]: you use model manager then use @commit_unless_managed if i have understand what you want

+can

Magus-: start transactions, stop transactions

like a chunk of code i have

needs to be one

wait, myisam doesnt support transactions does it

fuck

nope

I'm trying to make my Django app as modular as possible. I want to create "breadcrumbs" for a given URL within the application. I don't want to include the URL prefix that the project may use for the app. is there a way to do this w/o hard coding it?

I considered using resolve() to get the view, but wasn't sure how to get the prefix for that view so I can exclude it in my breadcrumbs

I'm having a really strange problem with django and mod_python

if I run django under mod_python, I can't log in - the login page tells me my browser isn't accepting cookies

if I run the app - same app, same directory - using the built-in server, it works just fine

so if the application handles all urls under /foo/bar/, I want to strip that from my list of bread crumbs

gordonjcp: stop your antivirus/firewall/etc and try again

dcode: you can define a tag then from other application call that tag with a prefix url parameter then the tag will return you the complete url

tie: I don't have any antivirus software

gordonjcp: a firewall?

tie: also, if I use Django's built-in server, *even on port 80* it works just fine

tie: a firewall is irrelevant her

here

dcode: no, you can't do that magically

gordonjcp: well firewalls can treat different hosts differently *despite* the same port, you know

the only thing I can think of is that the box is configured to use ISPConfig

you need to hard-code it somewhere

tie: yeah, it's not the firewall, ok?

dcode: after all, there is no concept of a 'url prefix' anywhere

gordon: do you use the site app

tie: other Django sites work perfectly

schnuffle: no

schnuffle: think it could be worth setting?

gordonjcp: ZoneAlarm?

Magus-, yeah, I wasn't sure if there was some way I could figure it out by introspecting the urlpatterns

tie: what's ZoneAlarm?

that might not be the right terminology

a firwall :) that's known to block cookies sometimes

extends cant be dynamic?

tie: it'd be blocking the dev server too...

tie: I don't have that - it looks like a windows thing

I only had some problems with it, resulting in a similar behaviour

Magus-: not necessarily, firewalls can block selectively

$10 says it isn't the issue here

tie: out of about six django sites, *one* specific one isn't working, in very specific ways

tie: I think I can safely rule out firewalls

Magus-: I'm making a point, 90% of the times cookies dont work is a firewall issue

ok, lets rule them out then

with average users sure

not developers

ime

anyway

Magus-: not developers, who develop firewall firmware...

gordonjcp: sanity check - you're logging in from the login view, not from an idnex page or such?

!

aw, don't tell me

hang on, let me check

if you're putting a login box on a non-login view, you must call request.session.set_test_cookie() manually

interesting, page not found

otherwise it won't login the first time

but will if you hit submit on the login view

Magus-: actually even going to http://host/admin/ won't work

good to know

so it probably isn't this issue

you sure your db is synced?

^ fair question

not using relative paths with sqlite either?

tie: I am sure my db is synced

no, I'm using mysql as the DB

have you changed SESSION_ENGINE ?

not knowingly

wouldn't that stop the built-in server working properly too?

Magus-: you asked about sqlite because he mentioned firmware? :)

using caching?

tie: of course not

I asked about it because relative paths can screw up database access

and sessions rely on database access

just to fill you in, this is a Django front-end for a MySQL database that configures virtual mail users

Magus-: bad hostname can also scew db access... but, meh :)

but more noticably

I'm able to run with "python manage.py runserver host:port" and get the whole thing working perfectly

a relative path can work, it'll just make a new file where you didn't intend

so data can disappear

so his users could've been no longer there, for instance

whereas a bad hostname on mysql would just die flat out

ok, ok, I get it lets focus on the problem:)

the devserver is running on the same machine as the production server right?

my gut feeling is it's more related to apache

yup

I'm just setting up a test user account so you can go play

what do the apache logs say about http://host/admin/ not loading?

also, are you using something like suexec/wrapper that could cut off some environment vars?