Blog Sections Open
Restoring KCfinder After Manager Paths Change
If KCfinder stops opening after a move or manager path change, check paths, connector URLs, and folder permissions together — fixing only one of them usually is not enough.
KCfinder failures after a hosting move usually come from configuration drift. The file browser may have worked before, but once manager paths, file paths, or connector URLs stop matching the new location, the browser can return HTTP 500 even though the rest of the site still loads.
What to verify first
- manager path and manager URL
- assets and file browser connector paths
- read/write permissions on the upload folders
- any stale absolute paths left in config files
Typical failure pattern
Teams often restore the old path values after testing, but KCfinder still fails because the browser connector is using a different path layer or because directory permissions were changed during migration.
What to do
Review the entire file-browser chain, not just one config field. If the manager was moved to a custom folder, make sure every related path reflects that change consistently. Then confirm that the PHP process can actually read and write the browser directories.
Rule of thumb
Whenever a site is moved to a new host, test the manager file browser immediately. It is one of the first places where path mismatches surface.
Allowing Duplicate Aliases Only Across Different Parents
Patch alias handling so documents can share an alias in different branches without creating identical URLs under the same parent.
Avoid Clearing the Entire Site Cache When Saving a Resource
Evolution CMS clears cache broadly by default, so if you need narrower invalidation you have to plan it deliberately instead of expecting per-resource cache out of the box.