Moving the Evolution CMS Manager Without Patching Core Blindly

Changing the manager path is one of those tasks that sounds trivial until you try to do it in a real project. This older article documented both the motivation and the hidden complexity.

Why teams wanted it

• avoid path conflicts with hosting panels such as ISPmanager
• reduce obvious admin-path exposure
• gain more control over deployment layout

Main insight from the original post

Evolution CMS already had a helper like MODX::getManagerPath(), but the codebase still referenced manager/ directly in many places. That meant a true path migration required a careful sweep, not a single config change.

function getManagerPath() {
   global $base_url;
   $pth = $base_url . 'manager/';
   return $pth;
}

The practical workaround was to centralize the manager directory name behind a constant and replace hard-coded paths in the local build. The article used a custom constant such as MGR_DIR and patched the build consistently.

The modern takeaway is simple: if you move the manager, audit all path references first. Security-by-obscurity is not enough, but path normalization mistakes will absolutely break a deployment.