Fixing Image Paths for the Second Site in a Multisite Evolution CMS Setup

Multisite setups usually work until asset paths reveal which site the codebase was originally built for. The donor case came from a second site whose images still resolved against the primary site's asset expectations instead of the path the second site actually needed.

This is a classic multisite problem: the codebase is shared, but file paths are not always abstracted cleanly enough for every site to behave independently.

What usually causes it

• Hard-coded asset paths in templates or chunks.
• Assumptions that assets/ lives under one specific document root.
• Frontend markup that was written for one host and then reused without path normalization.

The safest fix is to treat asset URLs as part of the site configuration layer, not as literal strings scattered through templates. In multisite Evolution CMS projects, image paths should always be built from the current site context so the second site never inherits the first site's filesystem assumptions by accident.