some easy way to trap the iterations of this loop so that I can see what is
trying to redirect to where?
Ian,
I don't know if this applies, but when I have confusing and unplanned
page-to-page routing, I add a dummy URL variable to suspect statements that
do the routing. That allows me to see whether that statement is in fact the
one doing the redirecting, since the page it arrives at will have the
variable in the URL. Since you have a loop, I would both add this dummy
variable and cut the loop somewhere, so that it stops in its tracks. By
trial-and-error, you should be able to test each of the redirects.
I'm afraid that it's not the easiest way in the world. Still, it shouldn't
take more than a few minutes to find the problem.
HTH,
Matthieu
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
