#django

hi everyone

I'm in a very silly situation that can be summed up like this: I pushed everything across from staging to production and now I can't login to django admin - I'm using django 1.6.5

I read, searched and so on and no solution worked

webus: imho it's worth using django if you are keeping most of the default components. If you want to swap in templating engine/orm you are better of with something like flask

any help would be much appreciated thinking that this is very close to the actual launch

any ideas welcome

thank you ever so much

Any one use fcgi?

The error message is "Please correct the errors below."

thevibe, can you reset the password and/or create a new superuser with the manage command on production?

and there's no session created in the django_session table

I did that and I can't login with the new one either

:/

that's what I can't really understand

is there a user record in the database?

yes

all of them including the new one

apart from my app I use grappelli, tinymce, south and filebrowser

as I said is not creating any sessions in the django_sessions table

sounds a bit creepy

:) unfortunately it does

I don't know where to look anymore

I have the allowed hosts, I changed the domain in the shell and the app actually works

is just that I can't login

anything in the logs?

syncdb and igrate done?

*migrate

Debug enabled?

sorry to paste it here

[Wed Oct 01 08:26:03.489308 2014] [authz_core:error] [pid 25929] [client 5.148.143.101:8760] AH01630: client denied by server configuration: /srv/apps/shorecap/media, referer: http://sc.bpwdev.net/

this was this morning

since then I tried all kind of things and nothing

that was when I first pushed everything across

what DB are you using?

with debug true or false is the same thing - silence

:)

I am using the "good old" MySQL

no connection error to the database?

no

I can login from the command line

with this u = authenticate(username="user", password="pass")

from this - from django.contrib.auth import authenticate

are you sure the prod-url IS the prod system?

yes, very

is not the first time I do this :)

the thing is this I did a mysqldump and then pulled the data in

if I start from scratch with syncdb adn then migrate --all I can login

but then if I export my data is not happy at all

I can't do it

I tried this and no luck: python manage.py dumpdata --exclude=contenttypes --exclude=auth.Permission > initial_data.json

i’m not very informed about the security stuff in the database.. but maybe it has some footprint of the installation

I have pages for viewing specific orders, and I only want users to be able to see ordes that they own, is there a way of doing this with a decorator?

the interesting thing is that this happened before and everything was fine

this is the first time when I see this behaviour

and is quite an unfortunate moment

as I said this is prepared for launch

in that case, i might not help you

i would try to dump all tables used for data and setup a new database, import the data that i have in my own models

Hello

Gaah, I wish this company had HelpDesk or similar. I'm drowning in a sea of minor tasks instead of programming.

What's the best way to do a ListView with search?

Azelphur: use the django filter app (https://django-filter.readthedocs.org/en/latest...)

Azelphur: If you want paginated search results, you might find http://schinckel.net/2014/08/17/leveraging-html... useful

ok thank you

thanks folks :)

I think I've linked that article 4 times this week ;)

schinckel: haha it's a good article, exactly what I was after too, I figured there would be a way to abuse listview to get it to do what I wanted

MarkusH / schinckel: so it turns out, things break before the migrations are even run. They break during the connection, in register_hstore_handler: https://github.com/djangonauts/django-hstore/bl...

I need to get in there before that even runs :/

aidan: traceback please or never happened ;)

aidan: can you point me to the django_hstore repository?

aidan: tbh, this is a thing django-hstore needs to fix

I'm wondering if I can get in there before from django.db.backends.signals import connection_created

schinckel: hmm, wat does self.get_form do in your example? it seems to be undefined in my code

I also notice you've imported FormMixIn but never use it

aidan: for now I'd override the app config for django-hstore, catch the exception and rely on a migration being run before

MarkusH: yeah, lots of issues on the tracker about similar issues, but not quite "how to create the extension beforehand"

alrighty easy let me give that a shot.

hi

aidan: I'd probably raise a warning (django.core.checks)

from the docs: All messages reaching the django catch-all logger when DEBUG is True are sent to the console. -- but when I try to use e.g. logger.debug('test') in a view, I simply get: No handlers could be found for logger "myapp.views"

schinckel: think it's a problem in your example, should it nod be class FilteredListView(FormMixin, ListView): ?