[development] Being noisy on installation...
metzlerd at metzlerd.com
Fri Apr 11 04:06:52 UTC 2008
I realize that this is slightly off topic, but having run into
situations where I wanted to suppress the messages, I simply called
drupal_get_message and reset the message queue.
Perhaps these calls could be added to the profiile installations as
well as drupal_execute to make sure that these messages don't
interfere with the automated processes.
Anyway it's worked for me in the past, so I thought I'd mention it
incase it just hadn't been thought of yet.
On Apr 10, 2008, at 8:06 PM, Jeff Eaton wrote:
> I'm also opposed to this -- vigorously. Having built a number of
> custom profiles and related solutions for clients, it is a *pain*
> to have those modules splattering their messages all over during a
> carefully managed process.
> chx and I actually tried to get drupal_set_message() moved out of
> submit handlers as well, so that automated form processing wouldn't
> do the same thing, but we ran out of time to push through minor
> features like that.
> On Apr 11, 2008, at 12:28 PM, Morbus Iff wrote:
>> and saw one of my personal pet peeves jump out: "Even if your
>> module doesn't have need of a hook_install function, it's nice to
>> Display a note confiriming that the module is installed and ready
>> for action." Core doesn't do it at all and, as far as I can tell,
>> it originated with Views (which most folks take as an admonition
>> that It's Right).
>> Thoughts from the peanut gallery? At first blush, I'm horrifically
>> opposed to it, because I think we have enough to worry about then
>> reading /successful/ messages - I'd much rather Drupal interrupt
>> me when something /bad/ has happened, not when something I /
>> expect/ to happen actually happened. But, playing my own devil's
>> advocate, I could say that "well, there's precedence already - we
>> always inform the user when something has been created, updated,
>> or deleted successfully".
More information about the development