diff --git a/lam/docs/modules-specification.htm b/lam/docs/modules-specification.htm index ad015035..7ea45172 100644 --- a/lam/docs/modules-specification.htm +++ b/lam/docs/modules-specification.htm @@ -508,6 +508,254 @@ all values of this column must be different values
+

2.2.9. dynamic_Message
+

+
+ + + + + + +
function dynamic_Message($attribute, $id)
+
+
+This function is only needed when a status message contains strings +with variables.
+$attribute is the attribute the +message is corresponding to.
+$id selects the exact message.
+
+Returnis an array as expected from StatusMessage().
+
+

2.2.10. load_Messages
+

+
+ + + + + + +
function load_Messages()
+
+
+This function is fills the array $this->messages. First Index (x) is +the attribute the message is corresponding to.
+Second Index (y) selects the exact message. Third Index (z) contains an +array as expected from StatusMessage().
+$this->messages[x][y][z]
+
+

2.2.11. load_attributes
+

+
+ + + + + + +
function load_attributes($attr)
+
+
+This function loads attributes when an account should be loaded.
+$attr is an array like the +array returned by get_ldap_attributes(dn of account) but without count +indicees.
+If all attributes are very simple are part of the dn of account it's +possible to just call $this->load_ldap_attributes($attr)
+which is part of baseModule.
+The function load_ldap_attributes loads all attributes which fit to the +objectClass of the module.
+This function has t be expanded when attributes have to be loaded from +a different DN or handled completly
+separat.
+
+

2.2.12. save_attributes
+

+
+ + + + + + +
function save_attributes()
+
+
+This function returns an array with changes which should be saved. If +all attributes are very simple are part of
+the dn of account it's possible to just call +$this->save_ldap_attributes($this->attributes, $this->orig).
+The return array has the following syntax: First index is the ldap dn +which should be changed. Second
+index is the kind of modification. Possible values are: 'add', +'modify', 'notchanged', 'remove'.
+Third index is the attribute which should be changes. Fourth index is +an array with all values of
+an attribute.
+If you want to call lamdaemon +first index is 'lamdaemon'. Second index is 'command'. Third index is +the command
+itself which should be executed by lamdaemon.
+
+

2.2.13. delete_attributes
+

+
+ + + + + + +
function delete_attributes($post)
+
+
+This function returns an array with the same syntax as +save_attributes().
+$post is the $_POST array. It +is needed t interact with the user.
+
+
+

2.2.14. proccess_attributes
+

+
+ + + + + + +
function proccess_attributes($post)
+
+
+This function proccesses user inputs. It checks user inputs. It also +saves changes in attributes.
+$post is the $_POST +array.  Some attributes ar not part of a profile, e.g. uidNumber. +If $profile
+is true attributes wich are not part of a profile won't be checked.
+LDAP attributes have to be stored in $this->attributes array. First +index is the attribute name. Second
+index is an array of values of an attribute.
+This functions can return three different variables. When 0 is returned +everything is ok. When a string is
+returned the string is the name of a subpage of the module. If it +returns an array the array contains status
+messages. First Index is the attribute which has triggered a message. +Second index is an array containing
+status message arrays.
+
+
+

2.2.15. proccess_*
+

+
+ + + + + + +
function proccess_*($post)
+
+
+This function has the exact behavoir like proccess_attributes function. +* is the name of the subpage which
+should be proccessed.
+$post is the $_POST array. It +is needed t interact with the user.
+
+
+

2.2.16. display_html_attributes($post)
+

+
+ + + + + + +
function display_html_attributes($post)
+
+
+This function creates meta HTML code. The code is the page the module +wants to display.
+Return is an array of meta HTML code.
+$post is the $_POST array. It +is needed t interact with the user.
+
+
+

2.2.17. display_html_*($post)
+

+
+ + + + + + +
function display_html_*($post)
+
+
+This function has the exact behavoir like display_html_attributes(). * +is the name of the subpage which
+should be displayed.
+$post is the $_POST array. It +is needed t interact with the user.
+
+
+ +

2.2.16. display_html_delete($post)
+

+
+ + + + + + +
function display_html_delete($post)
+
+
+This function creates meta HTML code. The code will be displayed when +an account should be deleted.
+This is needed to interact, e.g. should the home directory be deleted?
+The output of all modules is displayed on a single page.
+Return is an array of meta HTML code.
+$post is the $_POST array. It +is needed t interact with the user.
+
+

*: These functions do not need to be implemented if meta data is supplied. See 6 for a list of meta data diff --git a/lam/lib/modules/posixAccount.inc b/lam/lib/modules/posixAccount.inc index a6fe2c91..c312e208 100644 --- a/lam/lib/modules/posixAccount.inc +++ b/lam/lib/modules/posixAccount.inc @@ -533,7 +533,7 @@ class posixAccount extends baseModule { } } } - + // fixme TODO lamdeamon without DN if ($this->createhomedir) $return[$_SESSION[$this->base]->dn]['lamdaemon']['command'][] = $this->attributes['uid'][0] . " home add"; return $return; }