Table of Contents
A large problem with complex web sites and infrastructure is the lack of a consistent user profile area. When working with multiple web applications you are often forced to maintain several sets of username/password combinations.
GenieGate is not just a PHP application, it also contains a programmers API and was designed for complete customization through the use of templates and the model-view-controller design pattern.
Wherever possible, a hidden LOCATION parameter can be used to determine where the user is directed after completing something. For the most part, editing the HTML in GenieGate should not be required. In the cases where it is desired, the design supports something known as "views" this is more or less a fancy way of saying it's all template based.
Editing the templates directly
is strongly discouraged instead, you should copy
the template to ~/geniegate/lib/GenieGate/views/users/
(or ~/geniegate/lib/GenieGate/views/admin/)
and edit it there.
Alternatively, you may edit the appropriate view/NNN.xml file setting up paths to files (and even PHP classes!) of your own choosing. These are simple XML documents patterned after the Jakarta Struts package from apache.
The default template set contains the filename at the bottom of the screen, this can be used as a guide for which template to edit. This text is given a class attribute of "debug" (in the stylesheet).