Re: Recover/Reset password on code.djangoproject.com

[Nuno Mariz]

On Aug 29, 2:23 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> http://www.djangoproject.com/accounts/password/reset/
>
> Jacob

Thanks Jacob,
The http://www.djangoproject.com/password_change/ link sent in the
email is broken.

Nuno

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Recover/Reset password on code.djangoproject.com

[Nuno Mariz]

Hi,
I've lost my password on http://code.djangoproject.com, there is a way
to recover/reset it?

Thanks,
Nuno
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

ImageField and newforms-admin branch problems

[Nuno Mariz]

Hi,
I'm using newforms-admin branch and I'm having some problems with
ImageField(possibly with FileField too).
When saving a form in the admin and not validates some field the
ImageField shows something like:
Currently: {'content': '', 'content-type': 'image/png', 'filename':
'test.png'}

And on update a record in the admin and not validates some field the
ImageField shows empty without the "Currently:" label.

Anyone have this problem?

Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: newforms and encoding problems

[Nuno Mariz]

For me works like:

[...]
form = ProfileForm(request.POST.copy())
if form.is_valid():
data = form.clean_data
 for i in data :
 if isinstance(data[i], unicode):
 data[i] = data[i].encode(settings.DEFAULT_CHARSET)
[...]

No need to create an old_data.
I know is ugly, but until the patch it remains.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

newforms and encoding problems

[Nuno Mariz]

Hi,
Although seems that exists a patch for this problem, the newforms
continues with the same problem.
I have a field that the user fills with: João Ratão
In the database shows: Jo? Rat

This behavior happens only in the latest trunk, in the old an unicode
exception was raised.
In the Admin interface works fine(because uses the oldforms, I guess)
In my settings.py I have: DEFAULT_CHARSET = 'utf-8'

I'm doing something wrong?

Thanks,
Nuno Mariz


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---