The module as it stands now disables view of the block if you're looking at the node which generated it. It does this by checking arg(0) for 'node' and arg(1) for the block delta. This behavior unfortunately also removes the ability to have the block display if you have argument driven pages associated to the same node.

As an example use case you have a page at node/%/stuffaboutthisnode that is generated by views and provides some additional information about things related to the node which provided a block. You'd like to have the node provided block show up at this path to provide navigation back to the parent node.

I think it may make sense to make the visibility behavior selectable, however for now I'm providing a quick patch which checks also for arg(2) and confirms whether or not we're on node/%/edit.

CommentFileSizeAuthor
nodeasblock.allow_view_on_arguments.patch433 bytesjerdavis
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dropcube’s picture

dropcube CreditAttribution: dropcube commented

It probably should be a setting, defined on a per node basis, but we already have a lot of settings, so I am not sure. Maybe we can show the block on all pages (even on own node page) and if someone needs the block disabled on the node page (the default behavior right now) then this can be done at the theme layer.

What do you think ?

jerdavis’s picture

jerdavis
Location Minneapolis, MN
CreditAttribution: jerdavis commented

I could go either way on this. I feel like the correct compromise would be a setting for "Show block on node page" that would control the current behavior of hiding the block when viewing the node or not, as that's not straight forward through regular visibility settings so giving the option of showing or hiding the block when looking at the node seems appropriate. Then allow regular block visibility and the theme layer to deal with other fine tuning.