Blog Sections Open
Linking Images from assets/images in TinyMCE with KCFinder
If KCFinder opens the wrong folder for links, fix the browser path setup instead of copying files around and breaking your media workflow.
In many Evolution CMS projects, uploaded images live in assets/images, while KCFinder opens assets/files by default when you try to create a link in TinyMCE. That mismatch makes editors feel like the image browser is “wrong”, even though the real problem is simply how the browser paths are configured.
The practical goal
You want one predictable media flow: select the image, link it, and keep file validation rules intact. The cleanest approach is to align KCFinder’s target directories with the folders your editors actually use.
What to review
- the configured upload and browse directories
- whether TinyMCE expects a files folder while editors store images elsewhere
- permissions and extension filters for each folder
Recommendation
Do not solve this by duplicating media trees. Instead, reconfigure the browser so the link dialog and image dialog point at the same logical media location whenever that matches the editorial workflow.
Filtering a Resource List with a Select Form in Evolution CMS
A select-based filter can drive resource output cleanly if the selected value is treated as the parent container for the next listing query.
Counting How Many TV Fields Actually Contain Data
If a resource has several image TVs, count only the filled ones before you decide how to build the gallery or slider output.