gallery3.git - A clone of the Gallery3 code for testing and development.

Age	Commit message (Collapse)	Author
2009-10-22	Change the name of identity library from Identity to IdentityProvider. ↵	Tim Almdal
	Create a helper class called identity to simplify call the Identity Provider. Move the contents of MY_Session.php to the new helper class and remove the MY_Session class
2009-10-21	re-add the lookup_group_by_name API Method.	Tim Almdal

2009-10-20	remove the lookup_group_by_name as it is not referenced	Tim Almdal

2009-10-20	Add lookup_group Identity provider API and change the permissions controller ↵	Tim Almdal
	to use it to get the group it is modifying
2009-10-20	Add a groups api method on the Identity provider and change ↵	Tim Almdal
	access_Core::_get_all_groups() to use this to get the defined groups.
2009-10-20	Changes to Identity interface to allow for multiple Identity providers. ↵	Tim Almdal
	What I've tested to this point, is you can install a new provider, switch to it, login as administrator, uninstall the default user module, reinstall the user module, switch back to the user module and login.
2009-10-19	Simplify the user interface by moving the password reset functionality into ↵	Tim Almdal
	the user module Bagging the User_Definition and Group_Definition abstract classes and replacing them with interfaces with the same names. Make sure all the unit tests work.
2009-10-18	Add a menu item to manage the Identity drivers if there is more than one ↵	Tim Almdal
	installed
2009-10-18	Move the default identity config into the users module and change the ↵	Tim Almdal
	Identity constructor to look in module::get_var(gallery, identity_provider) for the current identity driver. In addition, don't just arbitrarily lock the use module. Only lock gallery and the module that is referenced by "user_driver_module" variable.
2009-10-16	Remove all non Identity API methods from Identity.php. Created an ↵	Tim Almdal
	MY_Session class to provide the user state changes in the session and a login.php helper that has the login form.
2009-10-16	Cleanup merge of user/group helpers into Identity interface. Reduce ↵	Tim Almdal
	redundant code in the user module and remove references to the Identity helper from the user module as the user module should be able to access things directly. Simplify the get_user_list api method to just accept an array of ids to return user objects for.
2009-10-16	Start simplifying the interface by moving the static methods from user.php ↵	Tim Almdal
	and group.php. Tried creating a identity helper, but the helper identity.php was confused with the library Identity.php. So got around this by making the methods on Identity static and calling the instance within the static methods. Also temporarily moved the user.php and group.php back into the user module.
2009-10-16	Finish integrating the move of the user edit/update functions into the user ↵	Tim Almdal
	module. The premise is that the plugable user module will provide the update screens if the user backend supports updates.
2009-10-14	Clean up phpDoc and change the Identity driver so only one configuration can ↵	Tim Almdal
	be active at a given time.
2009-10-13	Merge branch 'master' into talmdal_dev	Tim Almdal
	Conflicts: modules/gallery/controllers/admin_users.php modules/gallery/controllers/password.php modules/gallery/helpers/group.php modules/gallery/helpers/user.php modules/notification/helpers/notification.php
2009-10-07	Implement a user::is_writable() API method and disable the user add, updates ↵	Tim Almdal
	and display if the Identity driver does not support writes. This is set in the config.identity.php
2009-10-06	Clean up extra single quotes from copy and paste	Tim Almdal

2009-10-05	Access the form validation rules via the API for groups and users	Tim Almdal

2009-10-05	The initial commit of refactoring the user/group adminsitration into a driver.	Tim Almdal
	Create an Identity library that defines the interface the Gallery3 expects Move the user and group helpers into the gallery module to provide the familiar interface into the Identity library. Create a Gallery Identity back-end that is supplied by the user module. The vision here is that all user and group code that is gallery or ui specific is contained within the core product. Anything that relates to manipulating a user or group is contained in the back end code that can be replaced.