Download & Extend
Panels Taxonomy » Issues

Whoa! just what I need!

Posted by ktnk on June 8, 2007 at 6:28pm
Project:Panels Taxonomy
Version:5.x-0.2
Component:Code
Category:support request
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

I was scratching my head trying to figure out how to display views of different content types on a term page, and here is the module! Godsend!

Now, before I try it out, I want to confirm... did I read it right? Do I need panels 2 instead of panels?
My site is working with the latest Panels module (although the panels refuse to display blocks, but that's another story) and I'm very nervous about switching a soon-to-go-live site to the Panels2 Alpha 2 module - Will it even work with my current panels, or will I have to re-create existing panels with Panels 2?

Also, are the instructions written for making context-sensitive views to use in the panel for each term?

Thank you!
ktnk.

Login or register to post comments

Comments

#1

Posted by edrex on June 11, 2007 at 5:40pm

Hi ktnk, glad you find this useful.

I'm just about to release a re-written version which doesn't depend on panels 2, and in fact doesn't depend on panels at all so that it could also be used with a bare view etc. It will have its own admin page for configuring a term argument handler for ANY base path (could be a panel or a view or...). Each argument handler will provide a number of blocks for displaying term title/description, child terms, etc.

This is an important change as it allows several new features (setting page title to term/vocab name) and really cleans up the code.

Sorry, instructions for context view not included yet, will come in next release.

#2

Posted by Setzler on June 18, 2007 at 2:39pm

Timeline on version that's independent of Panel 2 alpha?

#3

Posted by edrex on June 29, 2007 at 7:01pm

Update: I decided to KISS and nix a rewrite (actually, I finished several rewrites, one completely independent of panels and one with an "arguments" tab added to each panel, but the UI for these totally sucked and the current UI is pretty simple and intuitive, so I just figured out workarounds for the limitations of the panels content item API.)

The current (0.3) release is pretty much how it's going to be.