Blog Sections Open
Running MultiTV on cp1251 Sites Without Breaking Output
A practical encoding note for MultiTV installations that behave differently on cp1251 sites than they do on UTF-8 setups.
Many old Evolution CMS projects still live on cp1251, which becomes a problem the moment a component assumes UTF-8 everywhere. MultiTV issues on cp1251 sites are usually not random. They are a sign that one layer in the stack treats encoding differently from the others.
Why this happens
- The site encoding and the component encoding expectations do not match.
- Saved JSON-like or serialized values are interpreted through the wrong charset.
- Frontend and manager layers normalize text differently.
When this happens, the safest fix is not to patch isolated symptoms blindly. First confirm the site’s actual encoding baseline, then verify whether the component truly supports it or needs normalization during save and render.
Fixing Errors After Restoring a Database Backup
How to approach Evolution CMS errors that appear only after a database restore, especially when the manager starts failing but the root cause is a mismatch in environment assumptions.
When the description Field Length Becomes a Real Limitation
How to think through description-length limits in Evolution CMS when the built-in field stops fitting the real SEO or editorial use case.