Overlaps with BPV module
moshe weitzman - January 1, 2008 - 16:43
| Project: | Block Assign |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
See my module at http://drupal.org/project/bpv. It doesn't force users to paste a snippit into the page visibility section so thats a nice improvement overb this module. However, my module doesn't have a UI for setting visibility like this one. Perhaps the author of this module will take the good parts of my module and we can retire mine? if you will do that, i will write a hook_disable() for this module so that we don't screw up sites upon disabling this module.
#1
I would love to integrate the two when I have a chance. Might take me a bit to get to it, but I'll keep in touch when I manage it.
#2
I would love to see this.
I think the block administration in Drupal is long overdue for an overhaul to more of a rules based assignment. The sites I run are becoming a logistical nightmare. I've thought of tackling this myself, but it's good to see someone beat me to the punch (as often happens).
Moshe, I read what you did on observer.com, and thought "why isn't this core?".
#3
It migth be core worthy, if we get the marriage proposed here working, Help wanted.
#4
I've updated my code with the block update query from bpv and to disable the display options form on block configuration. I've also set it to insert a regex to display the user block on all pages. Else when people install, they'll suddenly have no blocks and their sites will be totally hosed. One day maybe the install script will check existing block visibility statuses and try to honor them on install. I'd welcome review of the changes to make sure they're sane before I make a release of this.
#5
Tried out the module, the changes you made seem to work well.
It would be good to move away from the regex when creating the association. Instead, you could have two fields where people could people could list URIs - the first would be a list of conditions where to display the block, and the second a list of conditions where not to display the block.
For instance, if I want a block to display on the blogs on my site, except John Smith's (whose blog is a blog/johnsmith), the first field would have "blog" and the second field would have "johnsmith".
A second example would be that I want to have a block on all my add node pages, except for the "review" content type. The first field would have "node/add" and the second field would have "review".
If you leave both fields empty, the block displays on all pages.
Another helpful addition would be the ability to give a name to the block assignment. If I want to create a list of blocks to appear on all of my article pages, it's easier to pick out the title "Article Pages" than search for a regex string.
...perhaps this should have been a feature request.
#6
Some of those features are in BPV module. So I encourage the author to incorporate the remaining features of BPV like controlling block visibility via node type, page path, etc.