we proudly established a permissions system that obeys the abstraction pattern
access > permissions > roles > users
the "block visibility by role" feature circumvents this abstraction, by doing
access > roles > users
what looks easier in the first place and a victory of pragmatism over complex academic principles,
becomes a major PITA in practice:
know what happens if a sitebuilder adds a role, sets all permissions and... there's hidden permission stuff with blocks?
ever had to tell your child (or customer) why that role that has all permissions does not see block X?
we really do not want to start building hidden permision systems.
or the other way round:
"access by permission not roles"
like
"program against interfaces not classes"
Comments
Comment #1
marcingy commentedMoving to task this makes sense but nothing is actually broken at the moment.
Comment #2
geek-merlinforgot to add a constructive proposal:
implement one view permission per block
Comment #3
geek-merlinups, postings crossing.
Comment #3.0
geek-merlinadded programatic eclipse
Comment #6
tim.plunkettThis has been in block.module as long as I have been using Drupal. I'm going to call this a lost cause.
Please reopen if you feel strongly about it though!