...
/basic.php - similar to index.php but for devices with small screens or other handicaps (dumb browser...)
/accountstatus/accountstatus.php - Status and Pick-Up page for eduroam-as-a-Service Managed IdP user accounts
Coding your own
...
with YOURSKIN being an identifier of your choice. Inside that directory, you need at least the three files referenced above. Before calling your skinned pages, the CAT loader automatically loads the configuration, a skin handler, and depending on the page being called an array with extra information about the incoming request for your ease of coding. You find these as pre-defined constants and variables:
- CONFIG
constant, containing the global CAT configuration file. You do not normally need much from the config). See config/config-template.php for a breakdown of its contents - $skinObject
object with the skin handler (instance of the core/Skinjob class). The only function you need there is Skinjob::findResourceUrl(string, bool), You need it whenever you reference something in an external file (such as your own CSS, an image, a login link to the admin/ area ...) - $statusInfo
array with information about the sign-up token. Only present in accountstatus.php. Structure:
$statusInfo = ["token" => $cleanToken,
...
The skin pages are loaded with a cross-directory include() from the skin loader. Your skin should never assume to know its relative path on the server. It should rather construct all paths with $skinObject->findResourceUrl("IMAGES") (or "CSS" or "EXTERNAL" or "BASE") if you want to reference a image resource from the "global" stock of images (our stock is contained in the web/resources/ directory) , and a $skinObject->findResourceUrl("IMAGES", true) if you want an image that is only relevant for and confined in your skins/YOURSKIN/ directory. Your directory structure MUST mimick the one in web/resources/ for things to work.
...
Take a look at web/skins/example/. And of course for full functionality take a look at web/skins/classicmodern/.
Activating the skin
The default skin is the "classic" skin. The . Add a new skin to the global config (CONFIG['APPEARANCE']['skins'] array). As soon as the skin is in the config, the usual way to change it is via fed admin UI; add the new option "Preferred Skin for User Area" and type the string that matches YOURSKIN.
...
To make all pages appear in the desired skin, it is possible to hard-code the desired skin in the POST or GET leading to the CAT page. Append a
&skin=YOURSKIN (or POST equivalent)to the link and the UI will show with the desired skin immediately.
...