Closed (fixed)
Project:
Panels
Version:
6.x-2.0-alpha3
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
31 Mar 2009 at 07:44 UTC
Updated:
20 Aug 2009 at 19:50 UTC
I have 3 Taxonomy vocabularies on my site: Genre, Category, and Tags
Each are path auto-aliased to / (ex: genre/action )
I tried creating panels that have the same dynamic urls - (ex: genre/% )
When visiting the path, there are no errors, it just continues to show the regular tax term page. The same thing happens when trying to get views to override the path.
I don't want to use the standard taxonomy/term/ path because I need each panel layout to be different depending on which vocab it is for.
Any ideas on how to make this work?
Thanks
Comments
Comment #1
niklp commentedYou can do this with the default taxonomy/term/% ! What you need to do is forget Panels 2 and move to 3 though. You can override the default path in that, and add a handler for each taxonomy vocab that you want to display differently. At least that's my understanding.
There's a bit of a jump in the level of understanding required to do this, so I would try it on a test site...
Comment #2
pyxio commentedNikLP,
Do you know where there is any documentation for accomplishing this. I would like to do something similiar to Mike. I'd like to override the default node of a content type I have. I can figure out how to override all nodes, but I only want to override one type. Mike, let us know if you get this figured out. I'm also interested in overriding some taxonomy pages. Cheers, Kevin
Comment #3
niklp commentedI strongly doubt that there's any docs yet - this stuff is subject to a lot of change at the moment as far as I can tell.
If you create an override for a system page in the pages interface, you can tell the task handler to just be valid for that node type I think, and that's how you override just the one (altho you can make it valid for others too).
I believe this exact same thing is valid for taxonomy term pages and other stuff as well.
Comment #4
mstef commentedNikLP: Panels 3 was very buggy for me - notably with the Mini Panels module - items wouldn't delete, new items were created out of no where, settings weren't saved, etc. I didn't bother to post any bugs because it seemed so overwhelming, I figured it was fully supported yet. Can this be achieved with Panels 2? And how does that work with handlers like you were explaining? Every term's core path is /taxonomy/term/ - how would panels know that ID's 1-15 are for vocab 1 and ID's 16-22 are for vocab 2, etc? And even if it knew, how would you configure an entirely different panel for each vocab?
Comment #5
mstef commentedShould I just give up trying to override it? Remove the aliases and just use Views and theme files to write the tax term paths as I want them (directing to the panels dynamic path)?
It would be a pain in the ass but it would work at least..
Comment #6
niklp commentedI don't think Mini Panels has even been ported. I'd steer clear.
Panels 2 is stagnating. You're better off avoiding it altogether.
Overriding taxonomy terms paths... first of all, you need to use taxonomy context. If you've never used Panels 2 or 3 before, this is going to hurt your head. You might want to try setting up a demo site in D5 w/Panels 2.
The idea is that the panel gets a context (on the context tab) so that the pane(s) can be told various things, like what taxonomy term is currently "relevant" (ie in context).
When the panel page/pane has the context, it can then identify what's going on - so of course in the case of the taxonomy term context, a page can identify what the term is.
Task handlers mean that different panels pages (or maybe just layouts, I'm not entirely sure yet) can be assigned to the same path, just with different handlers. <- That's the really important bit.
Comment #7
mstef commentedAnd can that be done with D6/Panels 2?
Comment #8
niklp commentedJeez.
DON'T USE PANELS 2.
You can experiment with PANELS TWO under Drupal 5, but undder Drupal 6 USE PANELS THREE, kay?
Panels 2 for Drupal 6 is very very broken.
Comment #9
mstef commentedI haven't yet noticed a problem with Panels 2 but I assume I should take your word for it. Why is it a full release if it's very broken?
Why is Mini Panels included in Panels 3 if it doesn't work at all? Any other known critical problems with Panels 3?
Ah hah...I just messed with P3 and figured out the task handler system pretty quickly..brilliant module..thanks
Comment #10
Erco commentedBe sure your "taxonomy_term" default view is not enabled.
Is so disable it and the panel override should work.
Comment #11
niklp commentedI had this problem - this is correct. If you have a view AND a panel page set up to listen for /taxonomy/term/%, there is a menu router contention issue, and Views generally wins (for whatever reason).
Comment #12
Erco commentedYes,
An easy way to confirm that this is the problem is to try to export your Panel.
If it's the case, you will have a Drupal message that point out this Views/panels conflict
Comment #13
esmerel commentedPanels 3 is an RC at this point. Please try it, and if you have problems, open a new issue under that release.
Comment #14
pauln600 commenteddeleted