Agaric wants a way to decide who sees what status messages
Agaric wants a way to hide certain status messages -- such as the one produced by the update status module! -- from certain users.
http://api.drupal.org/api/function/drupal_set_message/6
and
http://api.drupal.org/api/function/theme_status_messages/6
have no solution presently, and it's not clear they ever should-- what kind of hook would allow modules to see what module is setting a message and something about the message other than the text itself, which would be expensive to test on?
Something that could decide which messages show on the screen and wchich go to watchdog would be great, but again I don't see this being light enough weight.
Maybe the modules that matter should be asked to implement unique privileges. Truly, the update status module's "this is out of date" is the only one we want to hide from clients.
So an extra permission called in the module to test whether it should even call drupal_set_message ("view update status messages") would be all we need.
That's still a patch to Drupal 7 core. We (or some good soul with a Drupal shop that doesn't want unnecessarily bugging clients) should submit it as early as possible.
Resolution
More like this
- Agaric wants to never, ever see the message illegal choice detected by administrator
- Agaric wants Drupal to upload files with any or no extension and stop being a pain about it
- Agaric Wants: to be able to add taxonomy terms en masse by checking off nodes in a list
- Agaric wants Drupal photo gallery with mass upload where albums can belong to people who set access per picture
- Testing nodeapi to see when it lets us do what


Comments
Post new comment