Hi Nancy,
For larger vocabularies I propose using argument handling as view-blocks are handled within panels-pages. Getting dynamically building block content.
So when the url is http://www.trekking-world.com/over/nepal/kathmandu-valley/kathmandu all arguments can be handled differently by a panels-page (over) with different panel-page-panes using the same weblinks_randomblock!!
With this solution there needs only to be one weblinks_block, which can handle arguments like views. So almost the same as you told me on http://drupal.org/node/388870#comment-1312750 except that there should not be a page been build, but a block on a page. And it should work within panels as view-arguments does because it should get the termid from the termname context.
It will look like as follows then:www.trekking-world.com/[panel-page]/[country-termname]/[province-termnam...
PANEL-PAGE "over" will have the following content:
------------------------------------------------------------------------------
|-----------------------------------------------------------------------------
|Panel-pane 1: Weblinks_randomargument_block
|Argument %2 (country termname context)
|-----------------------------------------------------------------------------
|Panel-pane 2: Weblinks_randomargument_block
|Argument %3 (province termname context)
|-----------------------------------------------------------------------------
|Panel-pane 3: Weblinks_randomargument_block
|Argument %4 (city termname context)
|-----------------------------------------------------------------------------
So only on page-buildup, the different blocks are constructed through argument handling then. Panels works so, that if there is no right argument or trigger to show the block, it is simply not shown. So above will also work for www.trekking-world.com/over/[country-termname] and then only the country random weblinks block should show.
Hopefully this is helpful in getting a solution for larger vocabularies?
Greetings,
Martijn
Comments
Comment #1
nancydruI have been experimenting with this and am able to sort of do it by invoking the standard block building. I am also starting to look at how to implement Views to do this, which may end up being the better solution for Panels.
One "challenge" I already see is that this would not be getting any block settings because the block has not necessarily been built.
Comment #2
summit commentedHi Nancy,
Why shouldn't the block necessarily be build. If there is at least one weblinks node it should allready be build, right?
If you are looking into panels. I advice you to look into panels3 with ctools/delegator. It is not yet finished, but it is the way forward for MerlinofChaos with panels.
Looking forward to test the random-block with arguments for you!.
greetings,
Martijn
Comment #3
nancydruYou're talking about effectively accessing the block code without going through the normal block building, which includes settings specifications.
Comment #4
summit commentedHi Nancy, I do not know what I am talking about I think in this perspective...looking forward to test for you.
What I have in mind, a weblinks_randomblock with arguments, and the arguments are build up through the context.
Right now with ctools/delegator the argument can be build up trough context, and than it is clear for the panel-pane holding the weblinks_randomblock what the argument handling should be. Say for instance termname or termid.
Greetings, Martijn
Comment #5
nancydruLet us also keep an eye on #399608: Allow a multiblock to contain arguments.
Comment #6
summit commentedYes, Argument handling like views2 (taxonomy termname, termid, others..like %1 %2 etc..), and then integrating it with panels, like views would be great! Then argument handling will be vert flexible and for both issues ok, right?
Thanks again for going into this Nancy!
Greetings,
Martijn
Comment #7
summit commentedHi Nancy,
Thinking about this further. What I do with panels3/ctools/delegator is show view2-panes in panel-panes, therefore if weblinks would be possible to build a view with arguments, it will be inherited in the panels-pane.
So enough is view2-support with arguments, right? Would this be easier, than straight panels3 support?
greetings,
Martijn
Comment #8
nancydruIt might be.
Comment #9
summit commentedHi Nancy, I think it is the way to go, because views2 can than be handled in different other forms/modules like panels 3 and the flexibility will be enormous. Views2 will itself then select random etc..so that will be out of weblinks hand than, right?
Greetings, Martijn
Comment #10
kompressaur commentedDoes Weblinks still not work with Panels? Im finding it 'a big hole' in my website due to this. Be nice to be able to add some context to it. Maybe i just dont know enough. Great module though.