Fixing Mixed Content in the Evolution CMS Manager Under HTTPS

When an Evolution CMS manager is opened over HTTPS but its plugins still request JavaScript and CSS over plain HTTP, the backend can fall apart very quickly. The browser blocks those insecure requests, and the visible symptoms range from missing TinyMCE and CodeMirror assets to broken ManagerManager widgets and JavaScript reference errors.

The core problem is not the browser itself. It is that one or more manager-side paths are still being generated as hard-coded http:// URLs.

Typical symptoms

• Mixed Content warnings in the browser console.
• jQuery is not defined or CodeMirror is not defined errors inside the manager.
• Plugins that work over HTTP but partially break over HTTPS.

Where to look

• ManagerManager widget assets.
• TinyMCE plugin paths and link list scripts.
• CodeMirror CSS and JS includes.
• Any custom manager plugin that builds asset URLs from a fixed base URL instead of the current request scheme.

Practical fix

Audit the manager-side plugins and replace hard-coded absolute HTTP asset paths with either scheme-aware URLs or relative paths. If the site is already committed to HTTPS, forcing those assets to load from the secure origin is the safest move. Once those references are corrected, the console errors usually disappear together because the dependent libraries can load normally again.

This is a good example of a backend issue that looks like “random JavaScript breakage” but is really a URL normalization problem.