Available layouts

Status: done (100%) — refinements remain possible; the page-header markup in particular may later move into tablestyle() if a suitable template mechanism is found.

How layouts work

Each layout registered in theme.xml has one file:

layouts/<name>_layout.html

The file contains the layout's own chrome and {---} where the page content renders. Core inserts the file at the {---LAYOUT---} marker of theme.html, inside the shared <div class="page {PAGE_CLASS}"> wrapper — layout files therefore start at .page-wrapper (or their aside), never with .page itself.

Every layout declared in theme.xml must have its file, and theme.html must exist too — if either is missing, e_theme::loadLayout() silently falls back to legacy theme.php layouts.

The layout renderer parses line by line — keep every shortcode on a single line in layout files and partials.

Current layouts

Layout	custompages	Purpose
full	—	full page, horizontal header, boxed width
auth	login fpw signup	centered auth pages
page (default)	page faq	boxed page with the magic page header
sidebar	news	magic page header + right menu column
home	FRONTPAGE	full-width marketing front page
memberdesk	—	member area, left vertical sidebar
raw	—	bare output

Each layout has its own page with the exact structure and rules.

Magic shortcodes — {---CAPTION---} and {---BREADCRUMB---}

The page and sidebar layouts render a Tabler .page-header whose content comes from core magic shortcodes (e_render::getMagicShortcodes()):

• {---CAPTION---} — the caption of the page's main render,

• {---BREADCRUMB---} — the current breadcrumb, by default rendered via e107::getForm()->breadcrumb().

Which render is "main" is designated by {SETSTYLE=default} — that is why those two layouts use default before {---} while the others use card.

Never switch the page or sidebar layout to {SETSTYLE=card} — the magic shortcodes are fed by the default-styled main render, and with card the page header stays empty.

Core also offers theme hooks for customizing the output: if theme_shortcodes defines sc_caption($caption) or sc_breadcrumb($bread), their return value replaces the marker instead of the default rendering.

{SETSTYLE} styles

Which style each layout uses and what tablestyle() renders for it is documented on theme.php. Rule of thumb: card for plain content layouts, default only for the layouts with the magic page header.

Per-layout behaviour without per-layout files

• Body classes — {BODY_CLASS} on the body tag (see theme.html).

• Page wrapper classes — {PAGE_CLASS} on the shared .page wrapper (auth → page-center).

• Header/footer variants — the {HEADER} / {FOOTER} shortcode switches: auth and memberdesk suppress the header, memberdesk loads footers/footer_small.html (see Header & footer partials).

In all three shortcodes, THEME_LAYOUT must be read via defset() at call time, inside the method. The theme shortcode batch is a singleton created on the first getScBatch('theme') call anywhere — a plugin or menu can instantiate it before e_theme::initThemeLayout() has defined the constant, so constructor caching works only sometimes.