Postponed
Project:
Views Term Path Override
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 Jan 2011 at 18:36 UTC
Updated:
15 Feb 2011 at 01:45 UTC
Seems doing it via Term ID is the first hurdle. How much work do you think creating another argument class would be for Term ID parallel to views_tpo_handler_taxonomy_term_name.inc class?
Is there perhaps an example somewhere of a Term ID class as a base? That could have the TPO settings and values replaced in?
Am I massively understating the difficulty?
Thanks.
PS: For me it's really all about the depth issue.
Comments
Comment #1
plachSupporting term ids will require a massive refactoring of VTPO code base since I'll need to find a clever way to reuse the code implementing the logic shared by the two handlers. Hence this will be for 6.x-2.x-dev if someone doesn't provide a patch before.
IIRC supporting depth is not possible since the taxonomy API function VTPO is based on takes only a single term argument.
Comment #2
rburgundy commented+1 subscribing
Comment #3
youkho commentedsub