in dev and alpha2 versions of Panels I cannot create multiple contexts for node/% (I want different ones for different content-types). I remember seeing someplace in the issuesQ that this was not yet ported... but I can't now find the reference.
Is this working yet? 'cause if it is, I am not seeing it and that leaves me quite stuck :-)
Comments
Comment #1
sdboyer commentedThe issue you're probably thinking of is #314463: D6 port - create secondary tabs for context switching, although "not yet ported" is not an accurate thing to take away from that thread. Different displays per node type is fully possible, right now.
Comment #2
pisco23 commentedThanks for the quick answer.
I was thinking of this
http://drupal.org/node/314463#comment-1049887
And I guess I may just be plain confused... what I am looking for is the tabbed alternatives under the "Content" tab, which appear after having declared an argument (like NodeID) under the Context Tab.... These never appear in D6 - and from the above linked comment, I'm reading that this is a menuing issue
I looked at how the "tabs" appear as a URL on a D5 site I get URLs like
?q=admin/panels/panel-page/mycontentype_override/edit/content/argument_0-forum
I have tried replicating this format directly in the URL for D6, to bypass the need for the tabbed menu items, but with no success.... so for the moment I have a node/% override which beautifully formats my main content-type nodes, and makes all the other CTs useless.
Am I doing something wrong? or do I just need to be patient :-)
Comment #3
sdboyer commentedAhh, yeah. I see.
"Ported" is accurate insofar as the interface looks/behaves the same, but with the changes in the menu system, making that veneer look the same really has very little to do with 'porting' and a lot more to do with re-architecting. That's why it's taking time.
But this is on my radar, and I don't intend to mark Panels as being in beta until it's solved. Nor do I intend for there to be an alpha3. Do the math ;)
Comment #4
pisco23 commentedcool - I'll be patient :-) wish I could help, but I am far from able.
- not wishing to use too much of your time which is certainly better spent on dev, than on "support" ... but is the workaround of going directly with ULRs possible at this stage?
Also - and its off topic - but I really appreciated your blog on user-panels.
Comment #5
sdboyer commentedThanks :)
Keeping in mind that I haven't actually TRIED that manually-entering-the-URL workaround...yes, it should be possible. Best way to do it would probably be to make a version on D5 that's the same as your D6 one and see what the argument URL would be, then slap it onto the end of your D6 url.
Comment #6
mackh commentedsubscribe
Comment #7
mfbsubscribe
Comment #8
pisco23 commentedI have tried this approach (using a fresh D5 setup to get the URL structure) - and it doesn't object to the URLs, but the changes make to the content show up on the default context and there is no indication of my new "Content Type" having registered anything at all. there appears to be more than just a menuing issue here :-(
Comment #9
mackh commentedI tried entering the URLS as well, still can't get to the content edit page for displays by node type. Would be great to see this fixed.
Any other pointers or workarounds much appreciated. Anything I can do to help?
Comment #10
KrisBulman commentedsubscribe
Comment #11
sdboyer commentedNothin really to be done to help with this one, unfortunately. These, and other menu-related issues, have been the source of much hand-wringing and headdesking for merlin and I. Best I can say is that it seems like we've poked out a light at the end of the tunnel, and should be seeing some progress soon.
Comment #12
raiyne commentedThose of us with this issue; is there another workaround besides the v.5 URL workaround? We definitely have to override all content types within one panel page correct?
Comment #13
sdboyer commentedUnfortunately, even the URL workaround doesn't work - I finally tried it myself after suggesting it a while back. The problem has to do with loader functions, the menu system, storing cached objects, blah blah ick ick blah.
There are a few things I'm workin up the mojo to get moving on that ought to get this fixed, but at this point it's really just best to assume you can't have multiple displays per some argument-based criteria (like node type) at ALL in D6.
Comment #14
pisco23 commentedshame... thats really a bit of a show stopper for me. I guess I'll have to start to learn some themeing for my other node-types !
Comment #15
raiyne commentedTheming by node types? Is this another override function for drupal, much the same as theming specific views? (in principle?)
Comment #16
dorien commentedsubcribing
Thanks for the great work!
Comment #17
aaron commentedsubscribe
Comment #18
shiroitatsu commentedsubscribing. power and love to the developers. i just wish i would be able to help with this great module, but i'm just a measly designer.
Comment #19
sdboyer commentedFixed in -dev...yar!
Comment #20
Flying Drupalist commentedWow, stupendous. Thank you so much!
Comment #21
pisco23 commentedChristmas... twice in one week. Thanks ;-)
Comment #23
raiyne commentedIs the new release working for some of you? It is still not functioning for me. Latest updates. Is there a certain way you have to implement the contexts?
Comment #24
pisco23 commentedthe latest dev version is working for me - what isn't functioning for you?
Comment #25
raiyne commentedI am using the latest 6.x dev release:
I've added two Vocabulary Term Contexts "News" and "Reviews" under the context tabs, now shouldn't there be a tab or selection for each panel separately in the content tab?
Comment #26
pisco23 commentedI've used Node Context and have tabs based on the selected content types. I haven't tried Taxonomy. I'll give it test when I have time.
Comment #27
raiyne commentedMind if I run through the steps just to make sure I'm not missing anything?
- New panel page, I gave it a panel name of "node_override", with a path of "node/%". Everything else on the settings I left blank.
- On the context tab: You have 4 options:
- Node, which is an individual node and not what I want correct?
- Node Add Form: Which you can adjust to a particular content type and is what you used, correct? Just switch the Keyword to "reviews" and select content type "reviews" (In my case)
- Node Edit Form: Which is just for that and not what you used?
- Taxonomy Vocabulary: What I was using and couldn't get to work.
After you save there should be individual content tabs on the layout settings and content tabs correct?
Appreciate your help, btw.
-Ben
Comment #28
pisco23 commentedOn the context tab, you should have three 'higher level' options than that one you mention: Arguments, Context and Relationships. What you want (imho) is to set the Argument to "Taxonony term" - and ignore the 'Context' drop down. You'll then get a pop-up asking which vocabs you want to have set individually (and here I can be not much of a guide, as I am still confused about this... http://drupal.org/node/328929) but basically selecting the item you want, and reselecting it under "Own Display" - should bring up the tabs you are looking for.
Comment #29
raiyne commentedYou, my friend, are a hero among men. Works perfectly now...
You ever work on something so long that it feels like a weight is off your shoulders when you figure it out? Well...thats me right now!
Thanks again man.
Comment #30
pisco23 commentedI know exactly what you mean - and I've had tons of help from the community (including the excelent developpers of panels and views...) - so its good to be able to give back, even if its small beer ;-)
Comment #31
raiyne commentedActually, I found out that when using a Node ID Argument, you have access to the Node Contexts when trying to add it to a pane. I wasn't able to use the Node Context's when creating a Taxonomy Term argument.