Blog Sections Open
Building a Custom Checkbox TV Input in Evolution CMS
Sometimes the default TV input types are close to what the project needs, but not quite enough.
The original post described a custom manager input called Custom Check Box. The goal was to get a checkbox-style TV interface that behaved better than the default field for a particular editorial workflow.
What was changed
The approach extended manager-side TV rendering by adding a new input type in manager/includes/tmplvars.inc.php and then wiring it into the TV type selector.
Example render logic
case "checkbox_custom":
$field_value = !is_array($field_value) ? explode("||",$field_value) : $field_value;
$index_list = ParseIntputOptions(ProcessTVCommand($field_elements, $field_id,'','tvform'));
...
break;
Why teams did this
- default checkboxes did not fit the required layout or behavior
- multi-select lists were not editor-friendly enough
- the project needed a more controlled manager UI for structured values
This kind of customization belongs squarely in the ecosystem story: one of Evo’s long-standing strengths was that teams could reshape the manager when the default input controls got in the way.
Source: original community announcement.
Using modExtra as a Starting Point for MODX Package Development
How the modExtra training workflow helped developers understand package structure, processors, assets, and transport builds in the MODX ecosystem.
Shopkeeper vs miniShop2 for Large Catalog Projects
How to think about Shopkeeper versus miniShop2 when a catalog grows large and the project needs more structured commerce workflows.