gmane.comp.python.django.user

Re: Unable to access URL's query string using request.GET['next']

Ariel Calzada — 2013-05-25T05:07:18

You can't see next variable after login because the view that process
"login form" don't return the variable in any form. You can modify this
view.

Regards,

Ariel Calzada
Homepage: http://www.000paradox000.com
Blog: http://blog.000paradox000.com

"If I had asked people what they wanted, they would have said faster
horses."

 -- Henry Ford


2013/5/25 Felipe Coelho <fcoelho.9< at >gmail.com>

Re: Unable to access URL's query string using request.GET['next']

Felipe Coelho — 2013-05-25T05:03:48

2013/5/25 Amber Jain <i.amber.jain< at >gmail.com>



I can't say exactly what you're doing *wrong*, because this is the behavior
I would expect. The ?next query parameter is used by the default login view
to tell Django where it should send the user after the user has been logged
in [1]. The ?next argument is dropped from the query string because it has
already fulfilled its purpose at that point, it wasn't an argument for your
dashboard view. Can you tell us what do you want to achieve with this?

[1]
https://github.com/django/django/blob/master/django/contrib/auth/views.py#L48

Unable to access URL's query string using request.GET['next']

Amber Jain — 2013-05-25T04:23:16

Hello,

I can't seem to access request.GET['next'] (from a URL with a query
string). Here's what I'm doing:
localhost:8000/dashboard/ points to dashboard() view but the dashboard()
view uses < at >login_required decorator. And so, if the user isn't logged in,
localhost:8000/dashboard/ redirects to localhost/login/?next=/dashboard/
(but I can't access request.GET info after login).

Here's my dashboard() view: http://dpaste.org/Z9dZX/ ... i.e. when
dashboard view is loaded after successful login (from
localhost/login/?next=/dashboard/), I see "You submitted an empty query
string.", when in fact I expect to see the request.GET data from the URL
query string.

Can anyone point out the error(s) in my code? I can provide other parts of
my code if you want.

Thanks a lot!

Re: How to stop internal django server

Thomas Brandenburger — 2013-05-24T22:21:44

thanks

Am Sonntag, 28. September 2008 14:44:22 UTC-7 schrieb Hingarajiya,Ravi:

Problem counting names by letters

Brian Millham — 2013-05-24T20:53:55

With this simple database table:

class Artist(models.Model):
    id = models.IntegerField(primary_key=True)
    name = models.CharField(max_length=255L, blank=True)
    prefix = models.CharField(max_length=32L, blank=True)
    class Meta:
        db_table = 'artist'

I want to be able to get a list of the first letter of the names with a
count, for example with these artists in the table:

ABBA, America, Asia, Blondie, Billy Joel, Charo

I want this result

letter=A lcount=3
letter=B lcount=2
letter=C lcount=1

To complicate things, the database is not the default database.

I've tried this raw query

letters = Artist.objects.using('database_name').raw('SELECT id,
UPPER(LEFT(name,1)) AS letter, COUNT(DISTINCT name) AS lcount FROM
artist GROUP BY UPPER(LEFT(name,1)) ORDER BY UPPER(name)')

but I get this error: AttributeError: 'QuerySet' object has no attribute
'raw'

I've been able to do it using a cursor directly. Is that the only way?
Or am I missing something. I'm trying to limit my use of raw and direct

Problem counting names by letter

Brian Millham — 2013-05-24T20:40:47

With this simple database table:

class Artist(models.Model):
    id = models.IntegerField(primary_key=True)
    name = models.CharField(max_length=255L, blank=True)
    prefix = models.CharField(max_length=32L, blank=True)
    class Meta:
        db_table = 'artist'

I want to be able to get a list of the first letter of the names with a
count, for example with these artists in the table:

ABBA, America, Asia, Blondie, Billy Joel, Charo

I want this result

letter=A lcount=3
letter=B lcount=2
letter=C lcount=1

To complicate things, the database is not the default database.

I've tried this raw query

letters = Artist.objects.using('database_name').raw('SELECT id,
UPPER(LEFT(name,1)) AS letter, COUNT(DISTINCT name) AS lcount FROM
artist GROUP BY UPPER(LEFT(name,1)) ORDER BY UPPER(name)')

but I get this error: AttributeError: 'QuerySet' object has no attribute
'raw'

I've been able to do it using a cursor directly. Is that the only way?
Or am I missing something. I'm trying to limit my use of raw and direct

Re: Problem with ~ in url prefix

Michael Radziej — 2013-05-24T18:37:31

Hi Hordur,

it really *does* look like a bug, could you please open a ticket for
this behaviour? Nice would be a minimal test case, like just reversing a
url in this way when a ~ is in the path.


Kind regards

Michael

Re: current transaction is aborted, commands ignored until end of transaction block

Michael Radziej — 2013-05-24T18:30:20

Hi Andreas,


I guess you use postgres. This is a standard error that postgres thows
if you do any database action in a transaction after any other
error. You need to find the previous error that triggers this.

The error is probably in a different part than the one you currently
suspect ...


Kind regards

Michael

Re: upload image with Django

Michael Radziej — 2013-05-24T18:27:55


Does HttpResponseRedirect do what you want to achieve?


Kind regards

Michael

Re: object is not iterable

Michael Radziej — 2013-05-24T18:23:37

Hi Olivier,


It would really help to see a full traceback, could you provide one?


Kind regards

Michael

object is not iterable

Olivier — 2013-05-24T16:43:07

Hello all,

I have an insoluble problem when I try to use the formsets...

*This is my models:*
class Relais(models.Model): 
nom = models.CharField(max_length=100,blank=True)
competition = models.ForeignKey(Competition)
sport = models.ForeignKey(Sport)
ordre = models.IntegerField()

def __unicode__(self):
if self.nom:
return self.nom 
else:
return "%s - %d - %s" % (self.competition.nom,self.ordre,self.sport.nom)

*my forms.py:*
class RelaisForm(ModelForm):
class Meta:
model = Relais

*and the part of my views.py which cause this problem:*
        relaisList = competition.relais_set.all()
RelaisFormSet = formset_factory(RelaisForm)
formset = RelaisFormSet(initial=relaisList) # <== this line


The error is:
Exception Type:TypeErrorException Value:

'Relais' object is not iterable




Have you got an idea on what cause this problem ?
Thank you ;)

Re: Django's cascade delete is executing the DELETE SQL twice

Michael — 2013-05-24T15:11:53

Sure okay, I'll whittle my project down to the bare bones, investigate it 
further, and if I manage to get a simple project that reproduces it I'll 
let you know. Cheers!

Oh, and it's Django 1.5.1 I'm running.


On Friday, 24 May 2013 11:14:03 UTC+1, akaariai wrote:

Re: hi Why the page is showing in this way?

Andre Terra — 2013-05-24T14:23:59

Django itself isn't a simple end-user solution like Wordpress or the like.
It's a framework used by developers to write their own websites. Some
libraries, like django-cms, allow developers to build a CMS solutions
without having to reinvent the wheel. This, however, does not mean that you
can use it without knowing both Python and Django.

As the tagline on the official project page[0] says: "Django CMS - The
easy-to-use and developer-friendly CMS"


Cheers,
AT

[0] https://www.django-cms.org/en/

On Fri, May 24, 2013 at 7:44 AM, lx <lxlenovostar< at >gmail.com> wrote:

Re: Display each language in its own language.

Cody Scott — 2013-05-24T14:18:04

ok I also had to add
# -*- coding: utf-8 -*-
to the top of the file



On Fri, May 24, 2013 at 10:03 AM, Tom Evans <tevans.uk< at >googlemail.com>wrote:

Re: Display each language in its own language.

Tom Evans — 2013-05-24T14:03:44

If you don't want language names to be translated into other
languages, then don't mark them up as translatable strings that will
have their values retrieved from the active message catalogue. IE:

LANGUAGES = (
  ('en', u'English'),
  ('fr', u'Français'),
  ('ja', u'日本人'),
)

Cheers

Tom

Re: Display each language in its own language.

Cody Scott — 2013-05-24T13:54:26

In my settings.py I have

#Used for translations

gettext = lambda s: s

#languages written as they would be displayed in the language selector form

LANGUAGES = (

  ('en', gettext('English')),

  ('fr', gettext('French')),

  ('ja', gettext('Japanese')),

)

and I was thinking of writing each language in its own language

LANGUAGES = (

('en', gettext('English')),

('fr', gettext('Français')),

('ja', gettext('日本人')),

)

But I get an error for having a non ascii character in settings.py




On Thu, May 23, 2013 at 3:26 PM, Cody Scott <cody.j.b.scott< at >gmail.com>wrote:

Re: Help with robots.txt

frocco — 2013-05-24T13:47:30

Thank you

On Friday, May 24, 2013 9:16:35 AM UTC-4, Mike Dewhirst wrote:

Re: Help with robots.txt

Mike Dewhirst — 2013-05-24T13:16:35

I needed this info recently and googled robots.txt. This was the second 
item ... http://www.robotstxt.org/robotstxt.html

Re: View pictures from the template via models.FilePathField

Ronny Villarroel Mendoza — 2013-05-24T12:51:20

Hi Federico,

Maby is better idea you use the models.ImageField(upload_to= path)

ie:
locandina = models.ImageField(upload_to= path)

then in the template you can get the path:

{{ object.locandina.url }}
 
Also, you need to read some about configuration on settings.MEDIA_ROOT and 
settings.MEDIA_URL, for use the imageField.


Regards,
Ronny


El jueves, 23 de mayo de 2013 03:57:02 UTC-4, Federico Erbea escribió:

Re: Integrating NoSQL-persisted custom Models

Alir3z4 — 2013-05-24T12:39:59

how well it works. It's a fork of Django 1.3 ...,

I have an app up & running with django-nonrel 1.5, it's in beta but works 
perfectly with no problem, also mongodb-engine 1.5 beta is also available 
that can be used to support MongoDB database backend.

for getting django 1.5 you just need 3 things.

* [django-nonrel-1.5-beta][1]
* [django-mongodb-engine-1.5-beta][2]
* [djangotoolbox-1.5-beta][3]

They're all in beta but really works with no issue.

I really looking forward to see NoSQL support in django core, That would be 
awesome for such an awesome web framework. 

[1]: https://github.com/django-nonrel/django/tree/nonrel-1.5-beta
[2]: https://github.com/django-nonrel/mongodb-engine/tree/mongodb-engine-1.5-beta
[3]: https://github.com/django-nonrel/djangotoolbox/tree/toolbox-1.5-beta

On Friday, May 24, 2013 10:22:45 AM UTC+4, Russell Keith-Magee wrote:

Re: Django tutorial - change history 24h time format?

Pepsodent Cola — 2013-05-24T12:35:26

Hi,

I changed my settings.py file like so but nothing happened after I 
restarted the server "$ python manage.py runserver".

USE_L10N = False
FORMAT_MODULE_PATH = 'config.locale'

So I then followed this tutorial by creating some extra folders and files.
http://www.epicserve.com/blog/2011/jul/15/change-datefield-format-django-admin/
And copying his formats.py file to *
"~/Django/mysite/mysite/config/locale/en/formats.py"*.

But I still don't see any difference in my admin history page, what else 
can I try?

Because when I add a new Poll then the date and time information is how I 
want it which looked like that by default when following the official 
Django tutorial.

Date: 2013-05-24
Time 14:18:46

But when I click on the History button then Date/time looks american using 
a.m/p.m time format.  I want my history page to use the same Date/Time 
format like on the previous page.

May 24, 2013, 2:18 p.m.

Also all the multiple Time format options in the formats.py file confuses 
me, file was taken from the