Hi Earl,
After trying to get hardcoded argument handling working in Panels 2 for weeks, I finally got exactly what I want last week after your great remark in http://drupal.org/node/199850#comment-674956 to go for args[] instead of arg(). The corruption of the panel was a /div mistake, so it is working in alpha14!
But now I downloaded beta1 and am testing it..and I miss the hardcoded argument handling. See attached picture for what I mean.
Could you please set it back, if I am right off course, so the hardcoded argument will work again please? And I can try with the newest version?
Otherwise if it is still there, where can I find the hardcoded arguments possibility?
What I need is that for the same view-with handling code, I could very easily alter the termnames in these, so the panel shows the right queries and I can reuse the view as much as I like. As said this is working great now in alpha14.
Thanks for considering if you left it out.
Greetings,
Martijn
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | pane_bottom.jpg | 57.65 KB | summit |
| panels-pane-arguments.jpg | 83.51 KB | summit |
Comments
Comment #1
summit commentedOff course the selected radiobutton in the picture is wrong in my situation, as you explained in: http://drupal.org/node/199850#comment-674059
The right picture attached.
Thanks for your response!
greetings,
Martijn
Comment #2
catchI've also been unable to get this working with more than one argument - I had term/nodetype for mine. The arguments worked fine dynamically from a page view. Taxonomy term by itself was fine, term/nodetype from panels wasn't. I also tried term, nodetype just in case I misunderstood the help text (also didn't work).
Comment #3
summit commentedCatch,
Could you still see the possibility to fill in hardcoded arguments as shown in the attached picture http://drupal.org/files/issues/pane_bottom.jpg ?
I am not seeing this possibility anymore..
greetings,
Martijn
Comment #4
catchyes, it's still there with panels_views_legacy.
I'm not yet sure how it works with panels_views. I think you set each argument in different fields, based on my limited usage.
taxonomy_term: some argument
node_type: some argument
instead of
arguments: some argument/some argument
Comment #5
summit commentedHi Catch,
I don't see the UI to implement it. I am trying the context stuff to get working, but until now without result. I also think for what I am needing, that is a little to much.
The hardcoded argument handling worked in alpha14, I hope it comes back in again..
Where did you find the argument handling in panels_views_legacy, and how can you alter the arguments than on UI?
greetings,
Martijn
Comment #6
catchpanels_views_legacy gives me exactly the same ui as alpha 14. I couldn't get this working in alpha 14 (or it might've been a -dev just after alpha14) though. Make sure you have permissions for panels_views_legacy - that caught me out for about 10 minutes.
Comment #7
summit commentedHi Catch,
So you do see the arguments in the panels-pane popup with beta1? Like shown in picture: http://drupal.org/files/issues/pane_bottom.jpg , right?
I am superadmin on the testsite, so permission shouldn't be the problem right? Otherwise, how can I set the permission other than in access-control?
Greetings,
Martijn
Comment #8
summit commentedHi Catch,
I see them again, the arguments, may be it was a permission problem!!
I have an error now in the includes though, don't know if it is related..
Greetings,
Martijn
Comment #9
catchchanging title now they've reappeared.
Comment #10
summit commentedThanks Catch! Yes they have reappeared.
Did you solve your argument issue also?
greetings,
Martijn
Comment #11
merlinofchaos commentedThis may be happening because panels_views.inc is active but no views are loaded in it.
Does adding
$types = array();on line 692 of panels_views.module fix it for those of you getting this?Comment #12
summit commentedHi Earl,
Yes error gone with adding $type = arrray();
Exact code:
Thanks also for views_legacy, great it is still there!
greetings,
Martijn
Comment #13
michelleFixed the error for me as well.
Michelle
Comment #14
hedac commentedthank you..... that fixed it for me too :)
Comment #15
merlinofchaos commentedSorry, not actually 'fixed' until a patch has been committed. =)
Comment #16
merlinofchaos commentedCommitted this as part of another patch.
Comment #17
OutCast commentedBest little piece of code I ever seen! Fixed it for me.
Comment #18
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.