Blog Sections Open

Using Rich Text Fields Inside ManagerManager Workflows

A manager UX note about what can go wrong when a ManagerManager-driven field uses rich text content and inline styles.

Rich text fields behave differently from plain text fields, especially when manager customization extras are involved. A setup may look fine until the editor adds inline styles or formatted markup, and then the field becomes unstable on the next edit.

Why this happens

Manager-side customization flows often assume simpler text handling. Once styled HTML enters the field, encoding, sanitization, or field rendering assumptions can break.

What to check

  • how the field stores formatted content
  • whether the manager customization plugin expects plain text
  • whether the rich text editor and the custom field layer sanitize content differently

This is a good reminder that manager UX extensions should be tested with real formatted content, not just simple placeholder text.

Newer post

The New ManagerManager and Why It Still Matters

An extras spotlight on the renewed ManagerManager direction and why manager-level customization remained important for Evolution CMS teams.

Older post

Planning XML and HTML Sitemaps for a Multilingual Babel Site

How to think about XML and HTML sitemap generation when a site has multiple language versions and shared content structure.