Add login form to "Forbidden" (403) page, when user not already authenticated

Apr 09, 2007 18:17


Title
Add login form to "Forbidden" (403) page, when user not already authenticated

Short, concise description of the idea
See title. 403 page should prompt unauthenticated users to log in, instead of the user having to find another page log in.

Full description of the idea
Regular scenario in my life: I make flocked post. I go away. Someone comments to my flocked post. I get comment email. I receive email and want to reply. I click on the reply-to link in the email and, Whups! I'm not logged in. So then I have to, you know, find another page to log in. Huh? Like every other website on earth with personalization, prompt the user to log in!
An ordered list of benefits
  • 1) Convenience to users.
  • 2) Makes LJ look that much more professional.

An ordered list of problems/issues involved
  • I presume it's no big deal for LJ's 403 page, which seems to be already custom, to differentiate between unauthenticated browsers (not logged in) and authenticated but unauthortized users (logged in, but not on flock flist). So as far as I know, this is, like, a half-hour's work with no ostensible drawbacks in its most elaborate form.

An organized list, or a few short paragraphs detailing suggestions for implementation
  • "Forbidden
  • You don't have access to that post with your current login status.
  • Log in to LiveJournal

    Username: ______________

    Password: ______________

    Secure | Standard

    (Forgot password?)"
  • etc.
  • Or if that's too hard:
  • "Forbidden
  • You don't have permission to access to that page with your current login status.
  • Log in to LiveJournal"

§ developer review, user interface, privacy, accessibility, security, usability, login

Previous post Next post
Up