Malcom:
Many thanks for your time and interest in answering and clarifying my
doubts. According to this, it is now a little detail comparing with the
general and nice architecture of Django.
Very best regards.
Vizcayno.
--~--~-~--~~~---~--~~
You received this mess
On 11-Jul-06, at 7:27 AM, Malcolm Tredinnick wrote:
> I could give you the party line about why it is done like this,
> but I'm not going to bother. I don't find it to be a particularly
> defensible design, since it is an enormous hassle without being
> part of
> a uniformly strong security po
On Mon, 2006-07-10 at 18:32 -0700, Vizcayno wrote:
> When I create a new user in the Admin with all privileges, Django asks
> for new user and password; When I type the password I can see what I
> write, I think this field should be protected from seeing password.
Since it doesn't accept a cleart
When I create a new user in the Admin with all privileges, Django asks
for new user and password; When I type the password I can see what I
write, I think this field should be protected from seeing password.
After saving the new user I logout Admin, then I try to login with the
new user, the appli
4 matches
Mail list logo
