That solves part of the problem:
URLField.verify_exists¶
If True (the default), the URL given will be checked for existence
(i.e., the URL actually loads and doesn't give a 404 response).
But there still appears to be no way to verify the existence of a
directory that is protected, which is
On Sat, Feb 21, 2009 at 11:52 PM, Jlcarroll wrote:
> What is the best way to fix this? What if someone wants to enter a
> broken url in an admin page? What if the url isn't broken, just
> requires a login?
Please read the documentation for URLField, which explains how to
control this validation
when editing a url field in the admin, I entered the url of a page
that used apache to authenticate, and required a valid django user to
log in. The admin, said that hte url was broken, and required me to
"fix" the field before it would save it. There was no "over-ride, I
know what I am doing" opt
3 matches
Mail list logo
