In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Relationship Graph View Issue ] Dependency Graph ]
related to child of duplicate of

Viewing Issue Simple Details
ID Category Type Reproducibility Date Submitted Last Update
0000225 [In-Portal CMS] Optimization task N/A 2009-08-13 08:31 2010-07-22 15:06
Reporter alex View Status public  
Assigned To alex
Priority normal Resolution fixed  
Status closed      
Summary 0000225: Move login-related code away from UsersEventHandler class
Description Currently we have very large method (u:OnLogin event) in UsersEventHandler, that is used only once during user login. It sits there and eats memory in each user event handler created even, when user is already logged-in or not logged-in at all. I propose to
- create UserHelper class and move all login-related code to it;
- make loginUser method, that will have 3 input parameters: $username, $password, $dry_run = false

This method will login user with given credentials and return error as constant otherwise. When $dry_run parameter is specified, then it's only checked, that user with given credentials will be able to login if he tries to.

As the result of this optimization we will be able to transparently login users we want. Also we can upgrade this method, so it can login user by given ID (login and password not checked). Also we can specify where user should be logged-in: front-end or admin. This way it will be easy to implement feature, when administrator can login as any of front-end users without even knowing their password.
Additional Information

Web Development by Intechnic
In-Portal Open Source CMS
In-Portal Open Source CMS
Copyright © 2000 - 2009 MantisBT Group

Powered by Mantis Bugtracker