Fixing KCFinder Breakage After Updating to Evolution CMS 1.1b-d7.1

KCFinder failures after an Evolution CMS update are often blamed on permissions first. The donor case showed why that can be misleading. Permissions looked fine, the .thumbs directory existed, but the update still left the file browser unstable and produced related notices in TinyMCE link list logic.

One clue in the original report was a cp1251_general_ci environment, which is exactly the kind of legacy encoding setup that can make otherwise small file-browser assumptions fail in ugly ways.

What to check

• Whether file browser paths still resolve correctly after the update.
• Whether link-list helper scripts now emit notices or undefined offsets.
• Whether the hosting and database encoding combination changed the way asset paths are interpreted.

If the site uses older encoding conventions, treat KCFinder debugging as a full environment check rather than only a chmod problem.