Hi,
Great you can improve the project !!
V1.8 branch is the correct one to strat from.
Just pay attention that I frequently commit on this branch, to be sure get latest version.
add parameters in /tool/config.php (finish)
/db/maintenance.php must also be updated to automatically add the parameter on upgrading versions (config.php is displayed only at firts run)
do new job in user class (new method or modify existing, getSqlElementsFromCriteria)
imo new method in user class seems better (getSqlElementsFromCriteria is a very generic method used for all classes). You can also redefine getSqlElementsFromCriteria in class user, but then don't forget to call parent::getSqlElementsFromCriteria when needed.
Could you summarize how you expect to manage LDAP integration ?
- interface integrating LDAP users into user table ?
- direct LDAP control : how will you manage LDAP structure : only fit one mandatory LDAP structure, or define parameters to be able to fetch correct information on any LDAP structure ?
-how will you manage the link between LDAP users and resources and contacts ? (today, users, resources and contacts are stored in a single table, one line it possible to point to user and/or resource and/or contact (throught isUser, isResource and isContact flags).
These are the points that stopped me from investigating in LDAP interface...
Many thanks.
(you may reply to
Cette adresse e-mail est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. if you wish).