This is a simple Drupal 6 (at the moment) module that makes it possible to hide blocks from the main block list /admin/build/blocks. It does this by adding a tab to the local tasks menu on the blocks page, where site admins simply can check the blocks they like to hide from view. This is practical for two reasons:
- Hide system blocks (Who's online, who's new, Recent content, Powered by Drupal etc.) that aren't used so that they don't clutter the disabled-listing.
- Hide blocks generated by modules that are used via code, and shouldn't be available for insertion via the blocks interface.
This can be used to unclutter the block list for editors (or any role for that matter), as they'll only be shown the blocks that they actually use (or can/should use).
Project page: http://drupal.org/sandbox/vikfroberg/1495734
Git repos: vikfroberg@git.drupal.org:sandbox/vikfroberg/1495734.git
Comments
Comment #1
patrickd commentedwelcome,
You are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
(At least this has to be done before switching back to needs review)
I'm afraid this project is too short to approve you as git vetted user. We are currently discussing how much code we need, but everything with less than 120 lines of code or less than 5 functions cannot be seriously reviewed. However, we can promote this single project manually to a full project or - if possible - you can try to add more functionality to this one.
Please take a moment to create a README.txt that follows the guidelines for in-project documentation.
You can also get a review bonus and we will come back to your application sooner.
regards
Comment #2
spike22 commentedI would suggest this as a patch or feature of block module, not as an individual module. The approach, the idea or the way of thinking sounds good to me (I'd also like to see some improvements in that), just the implementation is not too much, even if the code is OK.
Comment #3
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.