Listdom Developer Templates and Builders Documentation

本頁內容尚未翻譯。

What this page covers

This page explains how Listdom resolves templates, where theme overrides fit in, and how Elementor integration is wired in the codebase.

Template resolution (`lsd_template`)

Primary resolver: lsd_template($tpl, $override = true).

When override mode is enabled, extracted data shows this lookup order:

Plugin template: plugins/listdom/templates/{tpl}
Parent theme override: {parent-theme}/listdom/{tpl}
Child theme override: {child-theme}/listdom/{tpl}
Final filter stage: apply_filters('lsd_template', $path, $tpl, $override)

Use this to customize rendering while keeping plugin core update-safe.

Taxonomy template behavior

For Listdom taxonomies, LSD_Taxonomies::template() checks locate_template('taxonomy-{taxonomy}.php') and falls back to plugin templates when theme files are absent.

Examples in extracted data:

taxonomy-listdom-location.php
taxonomy-listdom-category.php
taxonomy-listdom-feature.php
taxonomy-listdom-tag.php
taxonomy-listdom-label.php

Available template groups

Core template inventory includes groups such as:

auth/*, dashboard/*, elements/*, maps/*, paginations/*
payments/*, privacy/*, profile/*, search/*, single/*
skins/* (accordion, carousel, grid, list, halfmap, table, timeline, etc.)
taxonomy templates, widget templates, plus empty.php and iframe.php

For a practical walkthrough, see Customize Listdom template files.

Elementor integration

Elementor package hooks into lsd_listing_before_single_content.
If a listing is Elementor-built, the package sets $single->style to listing ID and returns $single->builders().
Widgets are registered via elementor/widgets/register.