Selector: A Better Document-Picking TV for DocLister and Related Content

Older document-picking solutions in Evolution CMS were often good enough for simple relations but awkward for modern content modeling. Selector was interesting because it pushed the concept further: a more flexible custom TV with tighter DocLister integration and better room for project-specific controllers.

Why it stood out

• It worked well for related-content scenarios.
• It could be integrated with DocLister-driven selection logic.
• It allowed custom controller classes instead of forcing one rigid behavior.

Project-level customization

the article showed how to create a controller class such as RelatedController and set DocLister parameters directly inside it. That meant a team could define exactly which resource tree, publication rules, or filters the selector should use.

This is why Selector belongs in the ecosystem story rather than only as a troubleshooting note: it reflects a better way to build relational editing workflows in Evolution CMS.

Source: Extras.Evolution catalog entry for Selector.