Tim Almdal
d9720b77e9
Merge branch 'master' into talmdal_dev
...
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-13 11:48:42 -07:00
Tim Almdal
03d0311618
Implement a user::is_writable() API method and disable the user add, updates and display if the Identity driver does not support writes. This is set in the config.identity.php
2009-10-07 21:40:05 -07:00
Tim Almdal
b3211cb2a8
Change the users.php controller so its no longer restful. The problem with our approach to restfulness is that it assumes that the resource will be found in the gallery database. It may well be there, but in the case of using plugable drivers from users, it could be in a ldap directory, it could be the gallery3 database, but the model could be wrapped in a control structure. So it was just easier to remove the restfulness and just call user::lookup instead.
2009-10-07 20:26:26 -07:00
Tim Almdal
6671bd8b85
Allow a groups property on the User implementation and load the Identity drivers early in the process so the session deserialization works.
2009-10-06 18:30:09 -07:00
Tim Almdal
ca17727478
Access the form validation rules via the API for groups and users
2009-10-05 17:08:27 -07:00
Tim Almdal
08c01fec6c
The initial commit of refactoring the user/group adminsitration into a driver.
...
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.
2009-10-05 16:27:52 -07:00
Tim Almdal