Page layout is handled using template files wherever possible.
Template files are simply HTML files with special tags embedded in them. Mig expands these tags at runtime.
Tags are surrounded by %% marks, such as this example:
<title>%%pageTitle%%</title>
In this case, "pageTitle" is the relevant tag name.
There is a glossary of tags later in this document.
If you don't know anything about HTML you can try checking out http://www.htmlhelp.com/ or looking for some other online help sites by using a search engine such as Google [ http://www.google.com ].
Make backups of template files before modifying them in case things don't work out as expected.
An "include" function is provided. To include a file, place a directive like this one on a line by itself:
#include "filename";
Such as:
#include "custom.html";
The contents of the specified file will be inserted in place of the
#include placeholder.
If the file mentioned by #include is a CGI file then it will be
executed, and its output will be placed there instead. NOTE: CGI can only
be used with Apache servers (and not even every installation
of Apache will do this correctly). Sorry, it's a limitation in PHP
that I can't work around.
If including a CGI make sure it prints appropriate HTTP headers before anything else (just like any other situation where CGI is used).
Please note some things about #include:
ln -s /www/htdocs/includes/custom.html /www/htdocs/mig/templates
This would create a symbolic link /www/htdocs/mig/templates/custom.html which would point to the real file /www/htdocs/includes/custom.html. Thus, there's only one copy to maintain.
The#include directive must be on a line by itself. It will not
function if anything else is on that line. Also, the filename
must be in quotation marks, and the command must be terminated with
a semicolon. Here are some examples:
#include "custom.html"; # RIGHT
#include "custom.html" # WRONG - no semicolon
#include custom.html; # WRONG - no quotes
<p>#include "custom.html";</p> # WRONG - not alone on line
As of version 1.2.5 it is possible to include PHP files as well as other
types of files. The one difference is that for PHP files the filename must
have an extension of either ".php" or ".php3".
There are three special files that Mig uses for its own purposes.
text/css (Cascading Style Sheet)
markup.
If you are using PHP-Nuke, PostNuke, phpWebThings, PHPWebSite, XOOPS or Geeklog these three files will not exist. This is called "Portal" mode. In their place you'll find mig_folder.php and mig_image.php which are the same basically as folder.html and image.html respectively. In Portal mode the CSS file is not used (Portal systems usually have their own CSS definitions). See the portal document for more about how to properly install things in Portal mode.
The following is a glossary of recognized Mig template tags, and what they are expanded to.
<a href="%%newLang%%=es">Espanol</a>
<a href="%%newLang%%=it">Italiano</a>
Then, anyone visiting your pages would be given a default page in English
(or whatever $mig_language is set to in config.php) but clicking on
the links as shown above would tell Mig to switch over to the new language
(in this case either Spanish or Italian).
You can also link directly to a version of your site before the visitor ever gets there (so they don't have to get English first, then switch). To directly link you'd add a ``mig_dl=LANG'' parameter to your URL. So if your usual link looks like this:
http://my.gallery.com/mig/index.php
You'd instead use this:
http://my.gallery.com/mig/index.php?mig_dl=es
Or you can link even if there are already parameters in the URL; just use an & instead of ?
http://my.gallery.com/mig/index.php?currDir=./My_Stuff&mig_dl=es
rawurlencode() in case
there's a space embedded in it or something.
$largeLinkUseBorders
If desired, one can define a per-folder template file. This can be done
with the FolderTemplate entity, as discussed in the "mig_cf"
document.
Mig uses a Cascading Style Sheet (CSS) file to manage all of its element colorization. Things like the page background, background colors for table cells, all are managed by the CSS file templates/style.css.
I don't have the inclination or time to write a tutorial on how CSS works, so please see http://www.htmlhelp.com/reference/css/ or whatever else you come across to figure out how CSS works. There are some books on this topic available as well (try searching for "CSS" at Amazon.com). A basic example follows, though.
To change background color of description tables from #f0f0f0 (grey)
to #FF0000 (red):
Before:
TD.desc {
color: #333333; padding-top: 4px;
background: #f0f0f0; padding-bottom: 3px;
font-size: .9em; padding-left: 4px;
text-align: center; padding-right: 6px;
}
After:
TD.desc {
color: #333333; padding-top: 4px;
background: #ff0000; padding-bottom: 3px;
font-size: .9em; padding-left: 4px;
text-align: center; padding-right: 6px;
}
In this example, only the third line (background) was changed.