urls.py changes ignored

Rock wrote:
> Yes I did. No help.
>
> Then I forced the creation of a new urls.pyc by
importing urls.py in
> "python manage.py shell" and importing
urls.py and explicitly checking
> that the correct number of urlpatterns were defined.
Still no joy in
> the browser though.
>
> Note that the access_log shows my request but the
error_log logs no
> associated errors.

If you are using Apache with mod_python you will need to
restart the
webserver.

-- 
Medhat Assaad


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

On my development machine I do not have to restart the
webserver to
have the changes enforced.

In any event, I have tried restarting the webserver and also
dumping
the cache in my browsers without effect.

There is no reason to suspect an error with the cloned
urls.py file as
it is an exact copy of the version on the development
machine.

Another thing that I have checked is the timezone and tod
settings on
the two machines and the timezone setting in the settings.py
file.

I am going to take a deeper dive into the http
configurations now.

Rock


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

I found a tiny difference in the http.conf files
(AllowOveride was set
to "FileInfo" instead of "None".) I
made that change, even though I
seriously doubted that it would make a difference. Then I
bounced
apache and amazingly enough the new urls.py showed up.

I set the AllowOverride setting back to FileInfo and changed
the
urls.py again and so forth and proved to myself that the
AllowOveride
setting had nothing to do with anythng. It was all about the
bounce.
(Apparently I thought I had bounced the server previously,
but had not.
Perhaps I was not su when I did the previous bounces.)

So now I can force the urls.py changes to be respected by
bouncing the
server. (Whew!) But that still begs the question -- why is
my
development server picking up urls.py changes right away
while my clone
machine requires a server bounce. Hmmm.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---