Configuring HTTP and HTTPS Correctly in Evolution CMS

Moving a legacy Evolution CMS site from HTTP to HTTPS is not only about installing an SSL certificate. The CMS configuration also needs to reflect the canonical protocol correctly. Typical Settings MODX_MANAGER_URL http:

Moving a legacy Evolution CMS site from HTTP to HTTPS is not only about installing an SSL certificate. The CMS configuration also needs to reflect the canonical protocol correctly.

Typical Settings

MODX_MANAGER_URL http://www.mysite.ru/manager/
MODX_SITE_URL    http://www.mysite.ru/

Once the site is served over HTTPS, stale HTTP constants can produce mixed-content problems, redirect loops, or manager/login confusion.

What to Review

site URL and manager URL constants
base href output
rewrite rules and redirects
hard-coded asset URLs in templates and chunks

Protocol changes should be treated as a full canonicalization task, not a one-line config edit. If one layer still thinks the site is HTTP, users will eventually notice.

Newer post

Preventing Memory Exhaustion in Eletters Queues

What to check when Eletters or another mail queue process runs out of memory before finishing a batch.

Older post

Fixing the xmail Redeclare Error in Legacy eForm Setups

How to understand and fix the classic “Cannot redeclare xmail()” fatal error in older Evolution CMS and eForm combinations.