Blog Sections Open
Fixing eForm Email Headers That Arrive as Base64 Gibberish
One of the more confusing mail problems in legacy Evolution projects is receiving eForm messages whose subject or labels look like raw Base64-encoded header fragments. Typical Symptom =?UTF-8?B?0JfQsNC60LDQtyDQt9Cy0L7Qvd
One of the more confusing mail problems in legacy Evolution projects is receiving eForm messages whose subject or labels look like raw Base64-encoded header fragments.
Typical Symptom
=?UTF-8?B?0JfQsNC60LDQtyDQt9Cy0L7QvdC60LA=?=What It Usually Means
- the message is encoded correctly, but the receiving side interprets it badly
- charset settings are inconsistent between the site, database, and mail headers
- legacy mailbox handling or transport rules expose the raw encoded header
The right approach is to verify charset settings end to end: CMS config, database encoding, mail transport, and mailbox behavior. This is rarely fixed by changing only one form template.
Using word-limit Safely with Ditto introtext Output
What to watch when word-limit or PHx-style truncation is applied to Ditto introtext fields that may already contain formatting.
Choosing the Right 404 Page Strategy in MODX Projects
A practical note on custom 404 pages, error page IDs, and why routing-heavy sites need a deliberate not-found strategy.