Blog Sections Open
Changing One TV Dynamically When Another TV Changes
A manager-side pattern for making one TV field react to another, useful when the second field depends on a section chosen in the first field.
Some editor workflows need dependent TVs: the first field selects a directory or category, and the second field should immediately offer resources from that chosen location.
The donor scenario
- TV #1: a dropdown of directories
- TV #2: a checkbox or selector of resources from the chosen directory
The challenge is that standard TV bindings do not automatically refresh one field when another field changes.
How legacy projects solved it
The usual route was a manager-side enhancement: attach JavaScript or a plugin-driven callback so changing the first TV triggers a refresh of the second TV field options.
What this means in practice
- the first TV provides the selected parent ID
- an AJAX endpoint or custom manager script loads the new option set
- the second TV UI is redrawn with the relevant resources only
This is a good example of where custom manager UX can be more effective than trying to force all logic through static TV bindings alone.
Auto-Filling an Empty TV from the Parent Resource
A manager-save pattern for inheriting a TV value from the parent resource when the child field is left empty.
Always Stay: Keeping the Manager in Edit Mode After Save
A small manager plugin pattern that changes the default save behavior so editors stay on the current form instead of being bounced back to the list.