[ANNOUNCEMENT] LiveUser-0.15.0 (beta) Released.

From: Date: Tue, 15 Mar 2005 12:34:59 +0000
Subject: [ANNOUNCEMENT] LiveUser-0.15.0 (beta) Released.
Groups: php.pear.general 
Request: Send a blank email to pear-general+get-18065@lists.php.net to get a copy of this message
The new PEAR package LiveUser-0.15.0 (beta) has been released at http://pear.php.net/. Release notes ------------- Important: We are migrading away from .sql dumps which were MySQL specific towards the MDB2 xml schema format. Therefore we have removed the .sql files from the sql directory in favor if xml schema files and a installer class defined in install.php. general notes - moved all config parameter handling inside the containers into init() methods - reworked RC4 handling into cryptRC4() method - fixed bug in LiveUser_Perm_Storage_XML::mapUser() method which would result in read issues if the user is not the first user in the xml file - moved authTableCols from the database containers into common - added conversion of PEAR errors to error stack in several places - disable password checks in the auth containters if password is set to false in the authTableCols config option - some cleanups and refactoring to add support for the authTableCols fields in the XML container like in the database containers - added Session auth container that checks a password as set inside the session. this could be useful in combination with a CAPTCHA - use LIVEUSER_ERROR constant instead of LIVEUSER_ADMIN_ERROR_QUERY_BUILDER - added allowEmptyPasswords auth container option - added install.php class to handle database schema installation via the MDB2 - removed sql files from the sql directory schema manager to provide support for other RDBMS than only MySQL - removed unused userExists() auth container method (use admin interface instead) - accept all config parameters by reference inside the containers - move readAreaAdminsAreas over to Complex where it should be. - the observers mechanism now use PEAR::Event_Dispatcher auth schema structure - handle is now unqiue by default perm schema structure - moved default database structure into separate file (using the GLOBALS super globals) - default datatype for auth_user_id should be 'text' (thx Matthias aka Nomatt for spotting) - table rights_implied should have been right_implied in the perm schema structure - removed has_level from the database schema - added area_admin_areas and all it's joins - fixed remember me feature in example2 - remove empty placeholders and block in loadTemplate() calls in example4 - added translation_id field in liveuser_translations table - fixed bug in group subgroup table joining in the schema structure examples - fixed bug in example1 onLogout -> postLogout (bug #3135) - fixed php5 issues in example4 - all examples now have a unique database name by default Package Info ------------- LiveUser is a set of classes for dealing with user authentication and permission management. Basically, there are three main elements that make up this package: * The LiveUser class * The Auth containers * The Perm containers The LiveUser class takes care of the login process and can be configured to use a certain permission container and one or more different auth containers. That means, you can have your users' data scattered amongst many data containers and have the LiveUser class try each defined container until the user is found. For example, you can have all website users who can apply for a new account online on the webserver's local database. Also, you want to enable all your company's employees to login to the site without the need to create new accounts for all of them. To achieve that, a second container can be defined to be used by the LiveUser class. You can also define a permission container of your choice that will manage the rights for each user. Depending on the container, you can implement any kind of permission schemes for your application while having one consistent API. Using different permission and auth containers, it's easily possible to integrate newly written applications with older ones that have their own ways of storing permissions and user data. Just make a new container type and you're ready to go! Currently available are containers using: PEAR::DB, PEAR::MDB, PEAR::MDB2, PEAR::XML_Tree and PEAR::Auth. Related Links ------------- Package home: http://pear.php.net/package/LiveUser Changelog: http://pear.php.net/package/LiveUser/download/0.15.0 Download: http://pear.php.net/get/LiveUser-0.15.0.tgz Authors ------------- Markus Wolff <wolff@21st.de> (lead) Lukas Smith <smith@backendmedia.com> (lead) Björn Kraus <krausbn@php.net> (developer) Arnaud Limbourg <arnaud@limbourg.com> (lead) Helgi Þormar <helgi@trance.is> (lead)

« previous php.pear.general (#18065) next »