Wrapping this up: the problem was caused by South, happened in migrate
(found via stack trace). When I upgraded South, the problem went away.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://gr
THank for the config , i do able to run the apache22 with mod_wsgi + python
2.7 in windows server.
On Sun, Dec 2, 2012 at 3:03 PM, Loai Ghoraba wrote:
> Thanks a million for the tip :)
>
>
> On Sun, Dec 2, 2012 at 5:08 AM, Chris Cogdon wrote:
>
>>
>>
>> On Saturday, December 1, 2012 3:47:39 A
Hello,
Does anyone know what I need to do to get my django app to run on my
elastic bean stalk?
I've got the simple voting application from the website running on my local
machine, but it's crashing when i run it from the aws cloud.
I've done the AWS git.push and that works, but then the websit
> A custom authentication backend isn't required; the ModelBackend should
adapt to any well-defined User model.
Thanks Russ, I hadn't realized the ModelBackend tied in nicely with those
changes.
> Have you tried changing USERNAME_FIELD to 'email'?
+1, looks like that's the OP's issue.
On Sun
Awesome. Thanks for the update.
On Sunday, December 16, 2012 3:56:22 AM UTC-8, bobhaugen wrote:
>
> Wrapping this up: the problem was caused by South, happened in migrate
> (found via stack trace). When I upgraded South, the problem went away.
--
You received this message because you are subs
Hello everyone
On my current project I need a mix of builtin Django authentication and
oAuth2 sources. But when writing a custom authentication backend, when does
it get used? The docs say:
"""Once a user has authenticated, Django stores which backend was used to
authenticate the user in the user
You need to enable debug in your settings file and provide the error you
are getting. There is nothing to go by here...
On 17 Dec, 2012 2:30 AM, "Nicholas Sonnenberg" <
nicholas.sonnenb...@gmail.com> wrote:
> Hello,
>
> Does anyone know what I need to do to get my django app to run on my
> elastic
I can send mails using send_mail or mail_admins methods
but django it self doesn't send me any mail on 404 error or 500 error.
I have even added raise Exception('Test') to my view function
I see the 500 error for that but no mail was sent
This is my settings.py: http://dpaste.com/846959/
I use
Oh... there's your problem... you've set the admin email to ... i'm
sure that doesn't exist! :)
Seriously, though... all that looks correct. Can you check your server's
/var/log/maillog to see if the mail is being accepted?
On Sunday, December 16, 2012 1:33:01 PM UTC-8, Ali Vakilzade wrote:
I don't have access to that file on server.
and log from uwsgi doesn't have any error massage about mail sending
can it be a python3 branch related bug?
در دوشنبه 17 دسامبر 2012، ساعت 1:36:05 (UTC+3:30)، Chris Cogdon نوشته:
>
> Oh... there's your problem... you've set the admin email to ...
On Sun, Dec 16, 2012 at 9:12 AM, Ian Foote wrote:
> On 15/12/12 11:18, sebastien.mor...@gmail.com wrote:
>
>> I've a custum user model which looks like :
>>
>> class User(AbstractBaseUser):
>> email = models.EmailField(unique=True)
>> activation_key = models.CharField(max_length=**255)
On Mon, Dec 17, 2012 at 4:53 AM, Michael Anckaert wrote:
> Hello everyone
>
> On my current project I need a mix of builtin Django authentication and
> oAuth2 sources. But when writing a custom authentication backend, when does
> it get used? The docs say:
>
> """Once a user has authenticated, Dj
Just in case someone else stumbles across this old thread.
TLDR: The recipe may be able to be improved - I only needed to close the
connection in the parent Python process, not in the child process.
--
Best guess hypothesis as to what's going on is when you fork a process, the
OS (e.g. OSX Moun
You really don't need a fork I am using the latest dev build of django and
the only thing you need to change is the direct_to_template in the urls.py
to use the new class based views and everything else works as is, I even
have a custom user.
On Wednesday, December 12, 2012 2:44:53 PM UTC-8, mi
Thanks required=False is what I needed :).
"ImageField is not required as expected" Isn't that what you want? :) Yes
that is exactly what I wanted but also wanted to display the actual
setting the required=False allows me to have my cake and eat it too :). Not
sure why required vs blank, null
My best guess is that the mail transport agent on the server is rejecting
the mail because something is different from mail that is send through
other places in your django code. Perhaps the mail "sender" is not correct,
for example?
Unfortunately, looking at the mail log is the best way to see
Checkout Graphite[1]. It seems like it would handle your graphing
requirement.
1. http://graphite.wikidot.com/start
On Mon, Dec 10, 2012 at 08:41:14PM +0100, Marc Aymerich wrote:
> Hi,
> I'm considering to implement a simple monitorization system that
> basically gathers some data from a set of
Hi all,
we're migrating from Django 1.2 to 1.5, and we've fixed all the
compatibility issues except one. It's "Compatibility with old signed data"
https://docs.djangoproject.com/en/dev/releases/1.4/#compatibility-with-old-signed-data.
In short, it drops users sessions and forces them to re-log
Hi Jury,
As the release notes indicate, there was some conversion code in place to
help make this transition; however, that code was removed in the 1.4
release. This means you have two options:
1) Run your site for a while on Django 1.3 before upgrading to 1.5, where
"a while" is the length of S
I'm getting a baffling ValidationError.
Request URL:http://127.0.0.1:8000/admin/assembly/item/4/
Django Version: 1.4.3
Exception Type: ValidationError
Exception Value: [u'Select a valid choice. That choice is not one of
the available choices.']
Exception Location: C:\usr\
20 matches
Mail list logo
