Re: swapping out request.user in views

I agree that hacking request.user is a bad idea here. Write a function for your view that returns data for a given user ID, then call it with the owner or visitor's ID. I would also have two separate views unless what the users are doing is very similar. On Jan 2, 5:54 am, bruno desthuilliers

Re: swapping out request.user in views

On 1 jan, 23:30, nbv4 wrote: > I have a webapp that is accessed by the following urls (among others): > > example.com/foobar-page-23 > example.com/preferences > example.com/barfoo > > etc. > > When these URL's are access, the page is displayed using data from the > user who

Re: swapping out request.user in views

On Thu, Jan 1, 2009 at 11:30 PM, nbv4 wrote: > > I have a webapp that is accessed by the following urls (among others): > > example.com/foobar-page-23 > example.com/preferences > example.com/barfoo > > etc. > > When these URL's are access, the page is displayed using data from

swapping out request.user in views

I have a webapp that is accessed by the following urls (among others): example.com/foobar-page-23 example.com/preferences example.com/barfoo etc. When these URL's are access, the page is displayed using data from the user who is logged in via request.user. I also want it so the user can link