cvs: pear /Perm_LiveUser/docs changelog.txt database_erm.png

mw21st Wed Aug 21 18:45:07 2002 EDT Added files: /pear/Perm_LiveUser/docs changelog.txt database_erm.png Log: Initial commit, second try with the now correct package name Perm_LiveUser Index: pear/Perm_LiveUser/docs/changelog.txt +++ pear/Perm_LiveUser/docs/changelog.txt Brief version history: v1.2 (10/06/2002) - Major Modification: - All sourcecode is now stored on a CVS server, therefore all files from now on will have new version numbers - Dropped the freshly-introduced factory method because of problems with session serialization (that could have been overcome, but at a great loss of simplicity). In the future, a manager class will be used for creating LiveUser objects and storing them into a session. This will also prove to add flexibility later on. ******************************************************************* Warning: API break between these versions! ******************************************************************* v0.5.0 (26/05/2002) - Major modification: Start of the modularization process. LiveUser is now split into a base class and subclasses, each providing connectivity to a different type of backend. Currently there is only one supported backend, namely PEAR::DB. Since this implies a certain break in API-BC, I've chosen to skip some version numbers. This also puts the package back in beta status. If you need a 100% proven, stable version, keep using v0.2.8 until further notice. Complete list of API changes: - Object instances are no longer created with the "new" operator. Instead, the method liveUser::factory() is used. - Setting the default timeout for login recognition and the $allowDuplicateHandles option in the class constructor is no longer supported. Expect support for configuration files soon that will make your life even easier. ******************************************************************* Warning: API break between these versions! ******************************************************************* v0.2.8 (04/02/2002) - BUGFIX: In 0.2.7, users could login when providing an empty password, even if the option $checkpw was set to TRUE. Fixed. v0.2.7 - Major modification: Totally renewed login process, new method readUserData() reads, well, user data (this was done in the login() method before). See method comments. v0.2.6 - Minor modification: Beefed up method userExists(). See method comments for details. v0.2.6 - Minor modification: Added optional parameter $checkLogin to method checkRight(). See method comments for details. v0.2.5 - Minor modification: Added $this->allowDuplicateHandles - set this to allow multiple users in the database to have the same login handle. Users with the same handle can then only be identified by their passwords, so you have to make sure in your application that if you allow duplicate handles you won't allow identical passwords. This can be useful. Trust me, it was a customer's request. By default, this is set to FALSE. v0.2.4 - Minor modification: Added if(is_array...) to method readRights() which should eliminate "...is not an array or object" errors. Should the current user have no rights in any area, $rights will now be FALSE. v0.2.3 - Minor modification: Added option $updateLastLogin to login() function. This allows to use the login function to just load all data into the object without modifying the date of that user's last login. Useful for administration tools (guess what I'm working on right now) v0.2.2 - Minor modification: No more plaintext passwords. Passwords must be stored into the database MD5-encoded. v0.2.1 - Minor modification: Now user can't login if not valid v0.2.0: Added user groups v0.1.0: From initial design to first working version (without usergroups)