Thanks guys. It appears using URLField is the best answer here.
It automatically prepends http:// if the url doesn't include that.
On Feb 27, 7:27 pm, Prabhu wrote:
> If you use URLField it should do the trick. Just prefix http:// if it
> doesn't exist already using
If you use URLField it should do the trick. Just prefix http:// if it
doesn't exist already using javascript.
On Feb 26, 9:37 pm, russianbandit wrote:
> This is a fairly general question, but what is the best way to handle
> and verify user entry of external urls? For
On 27 February 2010 02:17, russianbandit wrote:
> Sorry for being sort of a newb when it comes to regex. But what
> exactly does that line do?
>
> On Feb 26, 3:59 pm, "ge...@aquarianhouse.com"
> wrote:
>> Check it with regex?
>>
>>
Sorry for being sort of a newb when it comes to regex. But what
exactly does that line do?
On Feb 26, 3:59 pm, "ge...@aquarianhouse.com"
wrote:
> Check it with regex?
>
> re.compile("[a-z0-9]\.[a-z]{2,6}$", re.I)
--
You received this message because you are subscribed
Check it with regex?
re.compile("[a-z0-9]\.[a-z]{2,6}$", re.I)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
This is a fairly general question, but what is the best way to handle
and verify user entry of external urls? For example, if the user types
in "google.com", django will try to render "http://localhost:8000/
users/google.com". That is obviously not what I want. I know that if
the user types in
6 matches
Mail list logo