If you make a block 'custom', existing users will have to enable it in their profile. If 'static' blocks were automatically enabled in the profile, blocks wouldn't seemingly disappear if you later decide to make them custom, but users would be able to disable them.
Would this be a viable approach?

Comments

al’s picture

al commented

This is quite a complex issue. If we make blocks enabled by default rather than disabled, the bug mentioned will go away. But it'll also mean that for modules that potentially generate a lot of blocks (import.module for example), the admin will have to go through and manually disable all of the feeds that make up a bundle.

Perhaps import.module could do with a rewrite to make its block output configurable somewhere else. For each feed/bundle that you create it should have a "create a block" checkbox.

Then having a default of enabled would make a lot more sense. If either the admin or the user overrides that, it's hidden.

Kjartan’s picture

Kjartan commented
Assigned: Unassigned » Kjartan
Category: bug » feature
bradlis7’s picture

bradlis7 commented
Status: Active » Closed (fixed)

This is old, and I don't really think it applies.