Act templates

THE FULL LIST OF ALL ACT TEMPLATES

This page documents all templates used within the Act framework.

All templates listed here exist in Act. If you add template files to your conference templates/ directory, they will override the default Act templates.

TEMPLATES YOU SHOULD MODIFY

User Interface

These templates define the look of your conference.

• ui

  This is the master template, included by every other template in the system. It's used as a WRAPPER template by the Act system, ensuring all generated pages shares the same headers, titles, and footers.

  You're strongly advised to use it as a WRAPPER template on your static pages as well.

• menu

  There is no default menu template. You must create one before you start using Act.

• menus/item

  There is no default menus/item template. You must create one before you start using Act.

• menus/section

  There is no default menus/section template. You must create one before you start using Act.

• error_ui

  This template defines the look of the error messages within Act. You probably should simply add an error class to your CSS.

  This is the original template (all of it, actually):

      <span class="error">[% content %]</span>
      <br />

TEMPLATES YOU MAY WANT TO MODIFY

Many templates actually include other templates that contain the actual Act logic. You may want to add specific information to them.

• talk/schedule

  This is the main schedule template. Change it if you want to add information around the schedule table. See http://conferences.yapceurope.org/2003/ for an example.

TEMPLATES YOU SHOULD NOT OVERRIDE

Talk templates

Those templates manage visualization of information on talks.

• talk/add
• talk/ical
• talk/list
• talk/show
• talk/removed
• talk/added
• talk/notify_subject
• talk/import
• talk/schedule_table

  This is the schedule itself. Don't forget to include it if you set up your own version of talk/schedule.

• talk/notify_body
• talk/talk_list

User templates

• user/add
• user/create
• user/updatepassword
• user/fake_payment
• user/list
• user/main
• user/show
• user/added
• user/photo
• user/stats
• user/purchase
• user/change
• user/rights
• user/unregister
• user/payment
• user/search_form
• user/reset_password_subject
• user/reset_password_body
• user/register
• user/forms/new_user
• error

  This templates uses error_ui template to format the output. It receives an error id list through the errors parameter, fetch the corresponding message from the msgs hash nad chooses the selected language using the global.request.language parameter, before calling error_ui to format the message.

Event templates

• event/add
• event/list
• event/show
• event/removed
• event/added

Login template

• login

  The login page is used every time Act needs to authenticate a user.

  login template calls ui as WRAPPER for the header and footer stuff.

  It expects an action uri string representation to be passed as the action parameter. It also expects a destination uri to be passed in case you need to redirect the user to another page upon authentication).

  It will provide two fields for collecting credentials: credential_0 for username and credential_1 for password.

  The template will also provide a true value for the join parameter, meaning that the user pressed the submit button.

• logout

  The standard logout template is not useful. It only provides information stating that you just logged out from the system, no extra actions or other possibilities.

Menu templates

• menus/user
• menus/admin
• menus/talks
• menus/users
• menus/talks_body
• menus/talks_head
• menus/events
• menus/treasurer
• menus/act_confs

Error template

TEMPLATES YOU SHOULD NOT REPLACE

Or you'll break your site.

Core Templates

Core templates implement internal important template-processing routines that the system relays on to implement certain tasks.

Don't override them unless you know what you're doing.

• core/talk/schedule
• core/user/add
• core/user/purchase
• core/user/create
• core/user/rights
• core/user/register
• core/twostep/ok
• core/twostep/form
• core/twostep/email_subject
• core/twostep/email_body

Common macros

• common

  This template defines commonly used macros.

• Macro Documentation

  Those macros can be found at the common template source.

  • talk_link(talk)

    Receives a talk object as the first parameter;

    Creates a link to the given Talk Info page, using the talk title as the link name. It will make the talk title bold if the talk is already accepted for the conference.

    This calls make_uri_info() function passing using the talk.id field to identify the talk and build the link. It will also use the talk.title field for the link text and talk.accepted field to decide about format.

  • talk_confirmed_link(talk)

    Receives a talk object as the first parameter;

    Creates a link to the given talk info page, using the talk title as the link name. It will make the talk title bold if the talk is already confirmed for the conference.

    This calls make_uri_info() function using the talk.id field to identify the talk and build the link. It will also use the talk.title field for the link text and talk.confirmed field to decide about formatting.

  • talk_modify_link(talk)

    Receives a talk object as the first parameter;

    Buid a "modify talk" link that allows one of the organizers or the talk owner to change it. Organizers always can change a talk, it doesn't matter the current status of the conference. Talk owners only can change a talk until the organizers unset both the talks_submissions_open and talks_edition_open configuration options.

  • event_link(event)

    Receives an Act::Event object as parameter;

    Returns a link to the event information page for this event object, using event.title as the link text.

  • event_modify_link(event)

    Receives an Act::Event object as parameter;

    Builds a link to the editevent page, allowing only event organizers to edit the event properties.

  • user_info(user)

    Receives an Act::User object as parameter.

    Builds a link to the user information page, either using the user.nick_name (if user.pseudonymous is on) as the link text or the classical "First-Last name (nickname)" format.

  • timeslot(t)

    Receives as input either an Act::Talk or an Act:Event object, and returns:

    For Act::Talks, a link for the user information page, a link for the talk (bold indicates talk already confirmed) and the talk duration in minutes; Also adds up information about the track this talk is included into.

    For Act::Events, a link for the event information page, and the event duration in minutes.

    For anything else, this macro just will return the parameter passed into, becoming as harmless as possible.

Payment templates

• payment/list
• payment/notify_subject
• payment/confirm_invoice
• payment/payment
• payment/notify_body
• payment/invoice