Motivation

I'm strugling with class2 to understand how session handling works, how to properly login/logout to build an interface for an API that will use e107 user system.

Proposed Solution

Refactoring of session handling or a point in the right direction on how sessions work/dependencies so I can maybe implement It by myself and do a pull request.

Right now class2 is messy and definetly not well explained, many things happen behind the scenes in "misterious" classes that are loadded from everywhere

Example

Using common post for user login to any URL works well, but getting the code that is aparently being used to login

e107::getUser()->login($name, $password, $autologin)

Is not working as expected, as in case the password is wrong, you still get getUser()->isUser() as true, and getUser()->getData() returns still all data of the username provided, like if the session was properly inited..

This means that somehwere else, e107 is performing a cleanup if the userLookup was wrong, but I really can't find this behaviour...

Greetings,

• Nesjett