Blog Sections Open
Importing CSV Data into Multiple TV Fields in Evolution CMS
A practical guide for projects that need to import catalog or structured data from CSV into more than one template variable at once.
CSV imports are easy when one source column maps cleanly to one field. Real projects are rarely that tidy. The donor case dealt with a more common need: import structured CSV data into multiple TV fields and keep the mapping predictable.
Why this gets tricky
- CSV files often arrive with mixed formatting.
- One source column may need transformation before it fits the destination TV.
- Editors still expect the imported values to behave like native Evolution CMS content afterward.
The safe approach is to treat import mapping as a contract: define which CSV column feeds which TV, normalize the data before saving it, and avoid writing ambiguous values that will later be impossible to filter or sort correctly.
For catalog-heavy sites, clean import rules usually save more time than any single frontend optimization.
Building TV-Based Filtering with eFilter in Evolution CMS
How to set up eFilter and eFilterResult to build TV-based filtering interfaces in Evolution CMS.
Sending eForm Messages to Multiple Recipients Cleanly
How to design an eForm mail flow that sends notifications to more than one recipient without turning the form into a maintenance problem.