--------- META tags --------- Technically, these guys aren't tokens, but it is very important that your event description files contain them. This is the most important thing to include in your event files. The value of EVENTNAME is used as the headline for the event listing. If it's not set, you get a null headline, which makes it impossible for users to click on the link to see your event details. CATEGORY is optional and specifies the category the event belongs to. If you're going to use the categorization feature, be sure to set this - events which don't belong to any category only appear when all categories are displayed. You can also specify a comma-separated list of multiple categories. LOCATION is optional and may be used to specify a URL to which users should be directed for event details instead of being sent to a normal event detail page. If this is set, any body in the event file will never be displayed to a user, so you may as well not include anything other than META tags. If you're familiar with crontabs, this one should come easily to you. If not, don't worry - it's not that tough. Each of the 4 parameters can take a comma-separated list of the following types of values: * - Match any number a number - Match only that number num1-num2 - Match any numbers in the range num1 to num2, inclusive */num - Match any number divisible by num num1-num2/num3 - Match any number in the range num1 to num2 inclusive and divisible by num3 The parameters are year, month (1 = January), day of month, and day of week (0 = Sunday). Now some examples: REPEAT="* * 1 *" - Event takes place on the first of every month REPEAT="* * * 6" - Every Saturday REPEAT="*/4 * * *" - Every day during leap years REPEAT="* */2 14-20 5" - The first Friday following the second Saturday of all even-numbered months -------------------------------- General information about LowCal -------------------------------- VERSION - Version of LowCal URI - Last component of URI at which LowCal was accessed (e.g., if LowCal is at http://somehost.org/lowcal/my-calendar, %URI% = "my-calendar") ------------------------ Current date information ------------------------ DATE - Date in mm/dd/yyyy format EDATE - Date in dd-mm-yyyy format YEAR - 4-digit year MONTH - Number of month (1 = January, 2 = February, etc.) MONTHABBR - 3-letter abbreviation for month name (Jan, Feb, etc.) MONTHNAME - Full name of month (January, February, etc.) DAY - Day of month DAYABBR - 3-letter abbreviation for day of week (Sun, Mon, etc.) DAYNAME - Full name of day of week (Sunday, Monday, etc.) -------------------------- Adjacent month information -------------------------- LASTMONTH - Number of previous month (relative to MONTH) LASTMONTHYEAR - Year in which previous month falls LASTMONTHABBR - Abbreviated name of previous month LASTMONTHNAME - Full name of previous month NEXTMONTH, NEXTMONTHYEAR, NEXTMONTHABBR, NEXTMONTHNAME - Info on following month ----------------- Event information (only valid in event headers, footers, and bodies) ----------------- EVENTNAME - Name of event ------------------------------ Displayed category information ------------------------------ CATLIST - List of displayed categories separated by ", " or "all events"; intended to be suitable for display to users CATPARAM - List of displayed categiries separated by only a comma; intended to be suitable for use in links CATBOX - Displays a multiple-select list box tied to the category parameter containing a list of all categories in the event directory's 'categories' file CATBOXSIZE=n - Sets number of rows displayed by CATBOX to n - defaults to 3 -------------------------- Start/end date information (only valid in list headers and footers) -------------------------- DATERANGE - Range of dates included in list; "" if only one day is displayed, " - " if multiple days are included Same as current date tokens, but prefixed with "START" or "END": STARTYEAR, STARTMONTH, STARTMONTHABBR, STARTMONTHNAME, STARTDAY, STARTDAYABBR, STARTDAYNAME ENDYEAR, ENDMONTH, ENDMONTHABBR, ENDMONTHNAME, ENDDAY, ENDDAYABBR, ENDDAYNAME