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 strange since Django is doing
the authentication, and since the user that is modifying the admin
page has access to the file... so why is the existence check failing
in the first place? If I had to guess, it would be because I am using
Django to authenticate through apache, instead of in the django view
for the page. But there isn't a view for this content because it is
static and using apache is the right thing to do for static content.
There also appears to be no way to verify, but only warn which might
be nice.
Thanks for your help,
James
On Feb 21, 10:14 pm, James Bennett <ubernost...@gmail.com> wrote:
> On Sat, Feb 21, 2009 at 11:52 PM, Jlcarroll <jlcarr...@gmail.com> 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 step.
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---------~--~----~------------~-------~--~----~
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 unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
