Blog Sections Open

Fixing Editor Image URLs on Babel-Based Multilingual Sites

A practical path-handling fix for editor-inserted images on multilingual Evolution CMS sites.

Images inserted through a visual editor often work on one branch of a multilingual site and break on another. The usual cause is path style, not the image itself.

In Babel-style setups, editor content that stores paths like assets/img/photo.jpg may resolve differently depending on the current branch. Switching to root-based paths such as /assets/img/photo.jpg removes that ambiguity.

What to standardize

  • Editor-inserted media should use one consistent path style.
  • Multilingual branches should not depend on relative asset paths.
  • Any content migration should normalize old image paths if needed.

This is a simple fix, but on multilingual Evo sites it prevents a lot of “works here, fails there” editor complaints.

Newer post

Understanding TV Value Size Limits in Evolution CMS

How to reason about large Template Variable payloads in Evolution CMS and what to change when stored values approach database field-size limits.

Older post

Recognizing a Reinfection Pattern in a Compromised Evolution CMS Site

How to spot a recurring reinfection pattern when a hacked Evolution CMS site keeps recreating malicious rewrite rules and obfuscated PHP payloads.