Lists, Forms, and Search

Lists, forms, and search are where Evolution CMS stops being only a page tree and starts acting like an application. In classic projects this layer is built mostly from snippets and extras.

Lists: DocLister

DocLister is the main classic listing tool. It began as a replacement for Ditto and became more flexible and faster than the older stack. It can list resources from the tree, filter by TVs, sort with type-aware TV values, return JSON, and extend behavior through controllers.

[[DocLister?
  &parents=`45`
  &tpl=`news_row`
  &paginate=`1`
  &tvList=`cover,lead,published_at`
  &tvPrefix=``
  &orderBy=`menuindex ASC`
]]

Forms: FormLister and eForm

FormLister is the stronger classic choice when the form needs controllers, validation, lexicons, file-based params, API modes, external data sources, or reusable field logic. eForm is still common on legacy sites for contact forms, callback forms, and simple order forms.

[[FormLister?
  &formid=`feedback`
  &controller=`Form`
  &rules=`name:required,email:email:required`
  &tpl=`feedback.form`
]]

[!eForm?
  &formid=`contact`
  &tpl=`contact.form`
  &to=`sales@example.com`
  &subject=`New message`
!]

Navigation and Search Helpers

• Wayfinder — menus from the resource tree.
• Breadcrumbs — path from the root to the current page.
• eFilter — filter form and sorting layer, often paired with DocLister in catalogs.

[[Wayfinder? &startId=`0` &level=`2` &outerTpl=`main.nav` ]]
[[Breadcrumbs? &showHomeCrumb=`1` &tpl=`crumb.row` ]]

Catalog Filtering

In classic catalog builds, eFilter usually renders the form while eFilterResult or DocLister renders the result set.

[!eFilter!]
[+eFilter_form+]
[+eFilter_form_delete+]
[[eFilterResult]]

Rule of Choice

• use DocLister for listings and archives
• use FormLister for serious form flows
• keep eForm for simpler or legacy callback/contact scenarios
• use Wayfinder and Breadcrumbs when navigation comes from the tree

See also Current Extras and Legacy Extras.