Closed mathias closed 10 years ago
No test, but I didn't quite know how I'd set it up, so I omitted it.
Steps to reproduce:
I'm confused. I think this basically turns require_user into a no-op... actually, it would log the user out on any page that has a require_user filter. I'd expect that this would break user profile editing, for one.
Yeah, the build failed, so this is clearly not the fix. For some reason I was thinking require_user
was called when we detected that the resource required a logged in user but there wasn't a current_user
.. Which isn't what it's doing.
What this needs is something more complicated than redirect to root unless we have a logged in user
since it needs to clear the session when we redirect, too.
That should work, and passes tests.
Closing due to inactivity.