Using MultiTV as a Practical Alternative to mm_ddMultipleFields

This old question asked a very practical thing: was there anything in Evolution CMS similar to mm_ddMultipleFields, especially when rich text content was involved? That question marked a shift many projects were already making at the time.

Why the Old Pattern Started to Hurt

mm_ddMultipleFields was useful for compact manager-side helpers, but it was never the cleanest tool for structured repeatable content. Once editors needed richer fields, nested values, or more predictable output, the approach became fragile.

Why MultiTV Was the Better Fit

For grouped repeatable data, MultiTV was the more natural answer:

• it stores repeated field sets more cleanly
• it supports several useful input types in one structure
• it is easier to render consistently on the frontend
• it scales better for galleries, feature blocks, slides, and specification tables

What About Rich Text?

That was the real point of the original question. If a project needs repeatable text areas with richer formatting, the safest rule is to keep the editing experience as simple as possible. Use rich text only where the repeated block genuinely needs it. Otherwise plain text, URLs, images, and smaller semantic fields are easier to maintain.

Practical Recommendation

If you are deciding between patching an old manager helper and modeling the content more deliberately, choose the modeled approach. MultiTV is usually the cleaner path for structured repeatable content, while ManagerManager-style tweaks should stay focused on manager UX rather than data architecture.

Source: original community announcement. Related package docs: MultiTV documentation.