Skip to content

docs(custom-tvs): keep the pathing plugin on 2.3 and 3.x - #614

Open
Ibochkarev wants to merge 1 commit into
modxorg:3.xfrom
Ibochkarev:docs/issue-201-custom-tv-pathing
Open

docs(custom-tvs): keep the pathing plugin on 2.3 and 3.x#614
Ibochkarev wants to merge 1 commit into
modxorg:3.xfrom
Ibochkarev:docs/issue-201-custom-tv-pathing

Conversation

@Ibochkarev

Copy link
Copy Markdown
Collaborator

Description

The custom TV tutorial said the pathing plugin would not be needed from MODX 2.3 because Namespace would handle paths. That is wrong. People skipped the plugin and got a text field instead of the Template dropdown.

On Revolution 3.x, GetInputs can list types from {namespace}/tv/input/, so the type may appear in the TV editor. Rendering on a Resource still goes through modTemplateVar::getRenderDirectories('OnTVInputRenderList'). If the plugin does not output the Extra path, getRender() falls back to the core text renderer.

The tutorial now says the plugin is required, matches the events it actually handles, and notes the text-field fallback.

Checked against Revolution origin/3.x: modTemplateVar.php, Processors/Element/TemplateVar/Renders/GetInputs.php.

Affected versions

3.x (same trap on 2.2+; the old 2.3 claim is what #201 hit on 2.7.3)

Relevant issues

Fixes #201

The tutorial claimed Namespace would replace OnTVInputRenderList.
Skipping the plugin still falls back to a text field on the Resource
form. Fixes modxorg#201.
@Ibochkarev
Ibochkarev requested a review from Mark-H August 18, 2026 01:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue on extending-modx/custom-tvs

1 participant