just as a follow up to this, after debugging it with Malcom,we discovered we weren't copy()'ing the extra context parameter when we passed it into the request.so the previous request was modifying it and we then passed it back into the new one.On 07/08/2006, at 9:57 AM, Ian Holsman wrote:On 07/08/2
On 07/08/2006, at 9:49 AM, Malcolm Tredinnick wrote:Hey Ian,On Mon, 2006-08-07 at 09:28 +1000, Ian Holsman wrote: this problem has me stumped.. and i have no idea why this ishappening. [...] for some reason every once and a while it thinks basepath is anothercompletly different (but valid) URLeg /a
Hey Ian,
On Mon, 2006-08-07 at 09:28 +1000, Ian Holsman wrote:
> this problem has me stumped.. and i have no idea why this is
> happening.
[...]
>
> for some reason every once and a while it thinks basepath is another
> completly different (but valid) URL
> eg /aggy/tag/play/
> which I'm guessin
this problem has me stumped.. and i have no idea why this is happening.i have a function which calculates a context variable based on the request.pathin this example, base is hard-coded to "popular/"and the request.path is "/aggy/popular/" I then calculate basepath ala basepath = request.path[:re
