Closed (works as designed)
Project:
Taxonomy Views Integrator
Version:
7.x-1.0-beta3
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
6 Mar 2013 at 18:53 UTC
Updated:
26 Jul 2019 at 14:45 UTC
Jump to comment: Most recent
Comments
Comment #1
duaelfrHi !
This is by design. Views' default display is not intended to be displayed, so you need to create an other display.
If you have some arguments against this, I am open to discussion.
Best regards.
Comment #2
Anonymous (not verified) commentedI'm not against it I just seem to remember you could choose the master display rather than say a page or block display?
The beauty of this was that you could use the Taxonomy Term ID argument in your view without needing to specify a path.
As I understand it (and I might be wrong!), using the current TVI, I'd need to create a page display and then set my path as taxonomy/term/%
Doing so would mean I would override the core taxonomy display and in turn would mean that all my vocabularies would use this TVI view not just the one I checked.
In short, TVI was useful to me because I could render each taxonomy differently using different TVI views.
If this is not the case, apologies!
S
Comment #3
Anonymous (not verified) commentedJust marked this as needing review. S
Comment #4
duaelfrAt the moment when you enable TVI, the default drupal behavior is lost, so giving your views the taxonomy/term/% path will not change anything.
On vocabularies and terms where TVI override is disabled you will have the default drupal behavior emulated by the module.
Did you upgrade to the latest beta ?
I do not remember if it was already made in beta1.
Comment #5
Anonymous (not verified) commentedAhhh, okay yes... I must have got caught out between versions.
Thanks,
S