Django admin custom filter: ProgrammingError: more than one row returned by a subquery used as an expression

Hi, I'm trying this custom filter query for django admin return queryset.extra(select = {'val': "select id from web_quote WHERE character_length(quote_text) < 30"}) and I got something like this: Programming error: more than one row returned by a subquery used as an expression Basically I'm

Django 1.11 release candidate 1 released

We've made the final (hopefully) release on the way to Django's next major release, Django 1.11! Check out the blog post: https://www.djangoproject.com/weblog/2017/mar/21/django-111-rc-1-released/ -- You received this message because you are subscribed to the Google Groups "Django users"

Re: Testing a Django library

What are the different approaches you found? I created a simple minimal project inside the tests folder On Mar 21, 2017 9:59 PM, "bobhaugen" wrote: > Very interesting topic. We will be facing the same problem soon, and will > hope to learn from your experience. Got a

Re: Testing a Django library

Very interesting topic. We will be facing the same problem soon, and will hope to learn from your experience. Got a code repository yet? We're at https://github.com/django-rea If and when we have some good answers, I'll report back here. -- You received this message because you are subscribed

Re: After machine reboot "unix:/socket/uwsgi.sock failed (13: Permission denied) while connecting to upstream"

Hi and thanx for ur reply. The solution is "sudo setenforce Permissive " thanx and regards On Tuesday, March 21, 2017 at 2:21:29 PM UTC+1, Jan Miszura wrote: > > I was having the same issue and it was solved with "sudo chmod 777 > /socket". It's not necessary manually create uwsgi.sock. > >

WebSocket CONNECT WebSocket DISCONNECT WebSocket CONNECT WebSocket DISCONNECT

Hi, I'm setting up a web site using Django group. Websocket are working correctly in local host, i'm got three variable working and displayed in real time on the web page. When i'm trying to connect from a remote host, everything is working except the websocket. It 's constantly connecting and

Re: After machine reboot "unix:/socket/uwsgi.sock failed (13: Permission denied) while connecting to upstream"

I was having the same issue and it was solved with "sudo chmod 777 /socket". It's not necessary manually create uwsgi.sock. Good luck! Jan On Tue, Mar 21, 2017 at 9:16 AM, valerio orfano wrote: > BTW i ve created the uwsgi.sock manually gave permission 777 and changes >

Re: After machine reboot "unix:/socket/uwsgi.sock failed (13: Permission denied) while connecting to upstream"

BTW i ve created the uwsgi.sock manually gave permission 777 and changes the owner from root to nginx:nginx On Tuesday, March 21, 2017 at 1:10:22 PM UTC+1, valerio orfano wrote: > > Hi folks i have django 1.9 application integrated to nginx via uwsgi > application on Centos7. > It was working

After machine reboot "unix:/socket/uwsgi.sock failed (13: Permission denied) while connecting to upstream"

Hi folks i have django 1.9 application integrated to nginx via uwsgi application on Centos7. It was working fine, but then i had to reboot my machine. Now i am having the follwoing issue: unix:/socket/uwsgi.sock failed (13: Permission denied) while connecting to upstream, client:

Re: Tweaking the admin title to display the model name

No, sorry, we haven't written anything about it. It was another guy who wrote the code as well, so I'm really not the right person to ask :-) Regards, Andréas 2017-03-21 8:53 GMT+01:00 Derek : > Interesting to hear, Andréas. Have you written up any of your experience >

Re: Tweaking the admin title to display the model name

Interesting to hear, Andréas. Have you written up any of your experience with the implementation of nested formsets? On Monday, 20 March 2017 10:57:20 UTC+2, Andréas Kühne wrote: > > Yes, > > I actually have written an application where we use the django admin > interface as the primary work