Public Subscriber Website Customization - Edit Error Message Draft

On this screen, you edit the template that is used to create an error message display from a list of errors that may have been collected by LISTSERV Maestro in the course of validating user input. This display is shown integrated inline with the website page, which is why it should be visually distinctive. The template is generic and is used for all error messages of this subscriber list or list group.

Note: If you would like to change the actual error message texts, use this screen: Error Messages

Preview And Source Code

The main area of the editor allows you to show a visual preview of the error message display template. This preview automatically integrates the current draft version of the base page template and is shown dynamically with the code that you are currently editing on the Code pane.

To edit the content for the page, click the [Code] button in the editor toolbar and supply your desired changes to the HTML source code. While you are editing, you can toggle between preview and source code by using the [Preview] and [Code] buttons in the editor toolbar.

Switching to the HTML preview version of what you see in the editor while in code mode performs preliminary placeholder validation, which means that you may also see validation errors in the case your current edits damaged any of the available placeholders. The validation logic applied here is once again applied when you save your changes to finally create a new draft. This makes sure that only valid customizations are saved.

The Placeholders Section

The placeholders section defines the placeholders which can (or in some cases must) be used for the customization.

• Placeholder Hierarchy

  The parent-child structure shown in the section indicates whether a given placeholder can be used anywhere on the page or if the placeholder is only valid and available when used as child of its matching parent placeholder, as defined by the hierarchical tree structure.

• Optional Placeholders

  An optional placeholder can be included on the page, but does not have to be included. If such a placeholder is omitted, all its children (if any) must be omitted, too.

• Mandatory Placeholders

  A mandatory placeholder must be included on the page. If such a placeholder is omitted, LISTSERV Maestro will not accept the customization (i.e. a validation error message is shown when you try to save your draft).

  Mandatory placeholders are also additionally marked by using a bold font for their name.

If the placeholder itself is clicked, the placeholder is selected. A selected placeholder is shown inside of a box, with an additional short description of the placeholder and what it is for. Therefore, if it's not certain what a particular placeholder does exactly, or why it is required or not, simply select the placeholder to see this description.
With the description visible, click a second time and the placeholder tag for the placeholder is automatically inserted into the page code at the current cursor position.

If a placeholder is to be used on the page, it must be written using the special placeholder tag syntax. The syntax is slightly different depending on if the placeholder is one with a body or not:

• Without Body: The placeholder tag consists of a single tag and looks like this:

  {{maestro:NAME}}, where "NAME" must be replaced with the placeholder name, as shown in the tree. Note: Placeholder names are case sensitive!

• With Body: The placeholder tag consists of an opening and closing tag, with the placeholder body in between, like this:

  {{maestro:NAME}}...placeholder body goes here... {{/maestro:NAME}}, where in both the opening and closing tag "NAME" must be replaced with the placeholder name, as shown in the tree.

  The body, which is only outlined in the example above, can be any further HTML code and may also contain linebreaks to stretch over several lines or paragraphs. It is also inside of this body that the placeholder tags of the placeholder's children must appear. For example, with a tree definition like this:

  {{maestro:validationErrorsPresent}}
  {{maestro:validationErrors}}

  then the page must contain a placeholder structure similar to the following:

  {{maestro:validationErrorsPresent}}
      ...this is the validationErrorsPresent placeholder's body, which contains the child placeholder:
      {{maestro:validationErrors}}
      ...here the body continues, up to the closing tag:
  {{/maestro:validationErrorsPresent}}

Some placeholders may additionally contain attributes in their placeholder name, which is then written as follows:

{{maestro:NAME ATTRIBUTE="VALUE"}}

where "NAME" is to be replaced as shown above, and "ATTRIBUTE" and "VALUE" are to be replaced with the attribute name and value, respectively.

A placeholder may also contain several attributes, like this:

{{maestro:NAME ATTRIBUTE1="VALUE1" ATTRIBUTE2="VALUE2" ATTRIBUTE3="VALUE3"}}

If an attribute is not specified, a suitable default is assumed.

Placeholders with attributes:

• Text, Number, Email, or Password Profile Field Placeholder
• Button Placeholder (has mandatory attributes)
• Clickable Link Placeholder (has mandatory attributes)
• Quick Login Option Placeholder

(Placeholder types not listed above do not allow any attributes.)

Text, Number, Email, or Password Profile Field Placeholder:

Button Placeholder:

Clickable Link Placeholder:

Quick Login Option Placeholder:

(Only available on the login page.)

To save the changes, click the [Save Draft] button to return to the preview screen.