Blog Sections Open
Troubleshooting KCFinder Path Problems in Older Evolution Builds
If KCFinder behaves strangely in an older Evolution setup, the first suspect is usually path configuration rather than the editor itself.
KCFinder issues in older Evolution builds often looked random, but the root cause was usually simple: the connector and path settings were no longer aligned.
Typical Symptoms
- the browser opens but shows the wrong directories
- uploads land in an unexpected place
- selected files come back with incorrect URLs
Why It Happens
Older integrations often depended on MCPUK-specific assumptions and path variables such as /home/dmi3yy2/evo.im/www/. Once those assumptions drifted, the browser still loaded but stopped behaving correctly.
The practical takeaway is to debug the filesystem path and public URL mapping first. Media-browser bugs are often configuration bugs wearing a UI mask.
Making `paramEditFull` Work with `shk_widget` in Shopkeeper
How to reason about paramEditFull, TV-backed parameters, and shk_widget output when Shopkeeper parameter editing stops behaving correctly.
Sending Custom `header()` Responses from Evolution CMS Export Logic
How to reason about custom response headers when exporting files such as Excel documents from an Evolution CMS context.