I've been looking at creating a registraion view but am not sure on
the best way, although the Zyons style email for registration link
system seems good. But I am not sure whether it is wise to just ask for
a potential users email without giving them any prospect of
registration.
--~--~---
Thanks Don.
That, and some other issues identified by Alain Dazzi have been
resolved in Release 329.
It is recommended that people using these login routines in their own
code should upgrade ASAP.
On 26/08/2006, at 4:37 PM, Don Arbow wrote:
>
> On Aug 25, 2006, at 12:31 PM, Waylan Limberg
On Aug 25, 2006, at 12:31 PM, Waylan Limberg wrote:
>
> On 8/25/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
> [snip]
>>
>> I've gone through and stripped out every extra space I can find,
>> thinking that was the problem, but still that dang trailing slash
>> comes
>> down to the next li
On 26/08/2006, at 8:13 AM, Pedro Lima wrote:
>
> BTW, depending on your application you may want to make the hash with
> the email and something specific from your site to be able to validate
> the link latter. If you only set the email in the hash someone can do
> cryptString('[EMAIL PROTECTED]
BTW, depending on your application you may want to make the hash with
the email and something specific from your site to be able to validate
the link latter. If you only set the email in the hash someone can do
cryptString('[EMAIL PROTECTED]') and register.
--~--~-~--~~~-
Shortening to http://{{ domain }}/account/reg/{{verifyurl}}/
made no difference
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.c
And only some outlooks. The one I'm using right now gets it right, for
example.
Stupid outlook.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-use
On 8/25/06, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> On 8/25/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> [snip]
> >
> > I've gone through and stripped out every extra space I can find,
> > thinking that was the problem, but still that dang trailing slash comes
> > down to the next li
On 8/25/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
[snip]
>
> I've gone through and stripped out every extra space I can find,
> thinking that was the problem, but still that dang trailing slash comes
> down to the next line. Ideas?
>
For what its worth, Gmail does indeed display that on 2
At least for a test, if it doesn't happen with a shorter URL, then it's
clearly an encoding issue. You could try going the other way too and
making it longer, to see if more than the ending slash is bumped off.
Quoted Printable only uses 1 equal sign though, now that I think about
it more, th
Not handy, but maybe I'll try shortening the URL and see if that helps.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To uns
Looks to me like a "quoted-printable" email encoding issue, that's what
the two equal signs on the end probably come from.
The line that the URL is on looks to exceed the allowed character limit,
so the encoding has added the double equal sign, and bumped the text to
the next line.
An email c
OK, the code I'm using came from Jeff Croft's Lost-Theories source,
which in turn cribbed heavily from zyons... so with that background out
of the way...
When the user gets their verification email, the trailing slash isn't
sitting on the same line as the rest of the link.. it looks something
lik
13 matches
Mail list logo
