This feature was requested on September 2, 2006 [1], but closed one hour later:
For consistency as well as features, Block configuration options should be available in admin/panels for blocks just like they are in admin/block. Right now only title text option is configurable, but it does not have all the configurable options that are available as in admin/block. That would make more sense and also enhance the value of this module.
This is important, in order to keep associated blocks features and capabilities inside panels, so what was the reason to close the last request?
-------
[1] http://drupal.org/node/82079
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | panels-4.7.6_blockconf.patch | 1.28 KB | nacho.mg |
Comments
Comment #1
slantview commentedI created a patch to allow the page-specific visibility settings to pass thru from the block settings here: here
Hope this helps. When I get a chance, I'll try to add the code for the custom visibility settings.
/v
Comment #2
merlinofchaos commentedIt turns out to be hard to do block configuration -- I mean, we can put the form in, but the settings for it are global, meaning that you can't set them on a per block basis.
actually...that's not entirely true. There may be some really funky games we could play, but it could negatively impact performance, so I don't think we want to do that.
Leaving this open -- we at least now have block visibility settings respected, which is a plus.
Comment #3
nacho.mg commentedActually, I was not talking about visibility but custom configuration of the block. Of course you can configure it using block page, but is quite unusable.
well, I think that the problem here (my point of view) is the obsolete unique block instance. This is fine when you have block per site (right/left side blocks), but now that users can construct several pages using the same block as content with different configurations (panels way, for example), the block instance is a needed concept.
Anyway, here's a patch to allow custom block configuration from in the panels configuration interface.
Comment #4
merlinofchaos commentedI completely agree that the uniqueness is a problem. And I agree that having to go to the block configure page is a usability impediment.
I took a quick look at this patch...I don't think block specific stuff should be in panels.module itself -- it should be in block.inc if at all possible. The less panels.module knows about the actual content, the better.
BTW, when you submit a patch, please set the status to "Patch (code needs review)" -- I happened to see this one in my mailbox, but I often get busy and blow through those, and when I come back I look at patches before I look at bugs.
Comment #5
nacho.mg commentedI agree with your position about leave panels apart of content. But at the other hand, our end users don't matter about implementation questions so when we develop a site we must look for usability. That's the reason why we had to use this workaround. At the end, client is right ;-)
In any case, block debate is very interesting and affects several modules (as someone said, the proof is in the pudding :-P)
sorry about the status mistake
Comment #6
catchfixed in panels2 :) but not for 4.7