Site Specific Customisation

From MSpace

(Difference between revisions)
Jump to: navigation, search
(New page: == Sites == Custom skins/configurations can be defined to change the way that mSpace appears. Each site must be a self contained folder inside: <pre>/sites</pre> The mSpace system attem...)
(Setting a Custom skin)
Line 21: Line 21:
===Setting a Custom skin===
===Setting a Custom skin===
-
In order to tell the system to use a custom skin you must first install the skin into the <tt>sites/tt> directory and then edit the following file (create it if it does not exist):
+
In order to tell the system to use a custom skin you must first install the skin into the <tt>sites</tt> directory and then edit the following file (create it if it does not exist):
<pre>/config/config.php</pre>
<pre>/config/config.php</pre>

Revision as of 15:27, 24 November 2008

Contents

Sites

Custom skins/configurations can be defined to change the way that mSpace appears.

Each site must be a self contained folder inside:

/sites

The mSpace system attempts to load files from the current site first but if it cannot find them it then attempts to the load them from the default directory. This provides a cascading file system that allows for specific sites to only need overload the parts of the default site that they wish to change.

Default

If no custom skin is used then the default is used:

/sites/default

Custom

When a custom site is used the system first tries to load the config file from:

/sites/{$current_site}/config.xml

This is where most of the customisation of how mSpace functions can be done

Setting a Custom skin

In order to tell the system to use a custom skin you must first install the skin into the sites directory and then edit the following file (create it if it does not exist):

/config/config.php

Example /config/config.php file

<?php
	$httpVariables['template'] = 'eprints';
?>
Personal tools