I'm unsure how to parse your first sentence. However, I think you may be pointing out that the login form has a node_id=XXXX hidden inside of it in order to determine which node gets loaded when one submits the form. Obviously, this node_id can't be set to blazar's personal favorite node's ID if we don't know yet that blazar is the monk who is going to use the form to log in. Which belies the "easy to implement" claim (since the point seems to be to avoid the extra round-trip which blazar must lack the patience for since there are so many ways to get to your favorite node with a single click after login and it isn't even hard to use Free-Nodelet JavaScript to eliminate the need to click).
But it would be possible for the heart of the login code to note that $q->param('node_id') is login and override it (for POST requests). But that also strikes me as a rather sloppy hack. Perhaps not unacceptably crufty, though.
- tye
In reply to Re^4: Customizable login page? (precog)
by tye
in thread Customizable login page?
by blazar
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |