GitLab

bug - the smarty() function checks for whether the user is logged in,
and we're not sure that they are or are not until after the form has
been created. Made the login form use the div renderer.

is public. Check for the password having being changed just after the
login_submit function has determined that the user is logged in.

fieldsets, but other than that it works pretty well.

to 'value' and the request, as there's not much point in having default
values.

footer function. Re-implemented get_submitted_values using get_value, and
changed get_value to allow a callback function for getting the value, which
adds some more flexibility for customised elements.

calendar widget later, but this was to test how getting the value would
work.

elements.

session object stores.

creation to allow it to be created with a FK to the institution table.
Removed inserting of some default data (like the root user), as it needs to
be done after the auth plugin is installed.

and implementing the change form.

usernames/passwords are valid. Made the encrypt_password method public, so
it can be used when changing the password for a user. Use 'self' instead of
a broken class name.

that can't be inserted using XMLDB due to chicken/egg problems around table
creation.

call it the "insert core data step".

$smarty->display('artefact:internet:profile/index.tpl');

objects to array of user ids

of ? from another array