Since content is now just another block, if you disable block.module all content disappears. That content includes the content at admin/build/modules. Which obviously means you can't re-enable the block module again. Or do much of anything really.

Any reason not to make this a required module?

CommentFileSizeAuthor
requireblocks.patch455 bytesalpritt

Comments

damien tournoud’s picture

damien tournoud commented
Status: Needs review » Closed (duplicate)

See #367380: Make block module optional for the discussion.

alpritt’s picture

alpritt commented
Priority: Critical » Normal
Status: Closed (duplicate) » Active
Issue tags: +Usability, +D7UX

Thanks for pointing me to the other issue.

I'm going to re-awaken this one for now. Having read the other issue, I suspect the place to solve this is going to be in the design of the new 'Structure' section as planned for d7ux. I don't think that has an issue yet, so I'll just tag this one appropriately and possibly mark it a duplicate later if that makes sense.

Anyway, making this module optional seems like a good move for developers, but we've opened up a brand new path for non-developers to hit a dead end.

senpai’s picture

senpai commented
Priority: Normal » Critical
Status: Active » Closed (duplicate)

Accidentally turning off block module prevents you from being able to re-enable it. See #516150: Add fallback for main content block rendering

I've posted a screenie over there in comment 2, and we really need to fix this asap because it's not only a usability problem, it's an unusability problem too! :)