FullThread Page

The FullThread Page is (now) a page type. So, as with any page object, it appears in the structure editor and you can set its typical page properties (like template, CSS, etc).

In additions, it has some properties of its own that allow you to define more precisely how the FullThread Page looks.

A FullThread Page has been created automatically in your site, at yourSite/fullThread. So you may choose to skip the next section for now.

Creating a FullThread Page

To create a new FullThread Page, go to the structure editor of your site: /yourSite/admin/conversations/yourSite/structure, and select the folder in which you want to create the page.

In this folder's properties editor, scroll the window all the way down, until you get the "New File Or Folder" form. Type the name you want to give to your page in "Navigation Title". Set "Page Type" to "FullThread Page" and click on "Create New File".

The page will reload and show you a confirmation that the new object was created. Locate this object in the structure listing and click on it. This will open the properties editor for your FullThread Page.

Editing FullThread Page Properties

The FullThread Page has a set of common properties (like template or magicNavbar's) that we won't cover here. It has also its own properties:

• Order to show messages
  Choose "Heirarchical" or "Chronological" display of messages. Heirarchical is the default, and when used with the #msgIndentation macro in the item template, can be used to create an indented outline form of the thread, showing the direct reply relationship of each message. Chronological will sort all messages in the thread in time order by message creation date ( either ascending or descending as set by the next property ).
• If order chronological, sort ascending or descending?
  If the order is chronoligical, you may choose to have the most recent messages first ( descending ) or last ( ascending ).
• Max items per page
  If the number of messages in the thread excedes the number specified here, the thread will be broken into multiple pages. Special macros to build links to these pages in the page's templates are documented below.
• Indent String
  String to use in the #msgIndentation macro in the message template
• Show read flag?
  If yes, the #msgReadFlag macro will be used in the message template to display an icon indicated if the member has read a particular message.
• Page Template
  This is the template for the body of the page.
• Message Template
  This is the template for each message in the body. This can be a full message template. For more information, read about Message Macros.

Macros

Both templates are set by default, but feel free to edit them as you want. Here are the special macros for use only in these templates:

• In page template:
  • <--#threadPageContent-->
    The body of the page (you must include this macro call in your template, or the page would be empty).
  • <--#msgNoInThread-->
    Will be replaced with the number of messages in the thread.
  • <--#threadPrevLink-->
    Used when the number of messages in a thread exceeds the "Max items per page" property to create a link to the Previous page of of the thread.
  • <--#threadNextLink-->
    Used when the number of messages in a thread exceeds the "Max items per page" property to create a link to the Next page of of the thread.
  • <--#threadFoundLine-->
    Displays a reference for total messages in the thread, and those currently being displayed. For example, if a thread has 5 messages, and the "Max Items Per Page" property is greater than 5, it would return "5 of 5". If there are 15 messages in the thread, and the "Max Items" is 10, the first page would display "1 - 10 of 15".
  • <--#threadPageLinks-->
    Used when the number of messages in a thread exceeds the "Max items per page" property to create a links to all pages that constitute the thread.
• In message template:
  • <--#msgIndentation--> Will be replaced with the group of non breakable spaces that gives its indentation to each message in the thread view.
  • <--#msgReadFlag-->
    Will be replaced with the read flag, if the page property "Show read flag?" is set to Yes.