It is impossible to select a block that is assigned to region in the theme other then currently in use.
I.e if I use for admin interface garland theme and for site - other, I can only use blocks from garland only.

why don't just allow all blocks (even not used)

Comments

jtsnow’s picture

jtsnow commented

I have a solution for this in progress, but it hasn't been committed. One problem with this is that it ignores any role visibility restrictions. But, as long as the user is aware of that, I think it will work.

matslats’s picture

matslats commented
Version: 6.x-1.x-dev » 6.x-1.0-beta1
Component: Code » User interface
Category: bug » task

Just had a very hard time selecting my block as a widget source.
I was working in garland but had another theme available.
The block only appeared when I disabled the second theme.

Why select blocks from $block_list, which gets only the blocks visible to that user?
Why not put all the blocks in the list?

Here is how the blocks are found by the blocks module: foreach (module_list() as $module) {
$module_blocks = module_invoke($module, 'block', 'list');
if ($module_blocks) {
foreach ($module_blocks as $delta => $block) {
//then you can make your list with $module, $delta, and perhaps $block

jtsnow’s picture

jtsnow commented
Status: Active » Closed (won't fix)

The reasoning for selecting blocks available for the current user was that selecting blocks in a different way may lead to a security issue because a user should not be able to view blocks that he/she does not have permission to view. In any case, this is being addressed in the 6.x-2.0 version. I would suggest that you use the latest dev version unless you are somehow attached to the 6.x-1.0 branch.