Fixing TinyMCE Upload Errors After a Hosting Move by Correcting MODX_BASE_PATH

After a hosting migration, TinyMCE uploads could suddenly fail even though the editor itself still loaded. One of the clearer historical cases involved an open_basedir warning from the file browser because the internal path had been built incorrectly.

The error pattern

Warning: file_exists(): open_basedir restriction in effect...
File(...site.ruassets/plugins/seturl_js_tinymce.inc) is not within the allowed path(s)...

The missing slash in the generated path was the giveaway. The browser script was effectively resolving a broken base path after the move.

What actually fixed it

The final resolution was not a TinyMCE reinstall and not another plugin update. The real fix was correcting MODX_BASE_PATH so the file browser generated valid absolute paths again.

Why this mattered

This is one of those small migration bugs that can waste a lot of time because everything looks almost correct. The lesson still holds: after moving an Evolution CMS site, path constants and browser integrations should be checked before blaming the editor itself.

Related posts

Fixing KCFinder “Unknown Error” Upload Failures in TinyMCE
Fixing File Manager Paths That Resolve to undefined/files Instead of assets/files

Why this belongs in the timeline

This post matters because it shows how Evolution CMS teams solved real project problems with small, explicit patterns instead of heavy abstractions. That practical, incremental style is one of the clearest through-lines in the old Evo ecosystem.