Docs Navigation Open
Legacy Extras
Treat legacy extras as historical assets: sometimes useful, often informative, but not always the best current choice.
Legacy extras are still part of everyday Evolution CMS work. Many long-running sites depend on them, and the old Russian documentation remains the richest donor source for understanding them.
Most Important Legacy Components
- DocLister — listings, TV filtering, sorting, JSON, custom controllers
- FormLister — forms, controllers, validation, external data sources, lexicons
- eForm — contact forms, callback forms, basic order forms
- Wayfinder — menu generation
- Breadcrumbs — breadcrumb navigation
- PHx — tag modifiers and conditional output
- ManagerManager — manager form customization
- YAMS, evoBabel — multilingual maintenance
- Commerce, Shopkeeper, eFilter — classic commerce stacks
Why Legacy Docs Still Matter
- they document parameters and usage patterns in detail
- they explain how classic tree-based sites were assembled
- they are often the only source for older snippets and manager tools
How to Use Them Safely
- keep the concepts and examples
- verify PHP and Evo 3 compatibility before reuse
- prefer current packages when they replace the same job cleanly
Previous
Current Extras
Current extras are the preferred starting point for new Evo 3 projects and refreshed project stacks.
Next
Creating an Extra
Create an Evolution CMS extra as a real package with composer metadata, a service provider, config, migrations, views, assets, and optional classic elements.