<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html style="direction: ltr;">
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body style="direction: ltr;" bgcolor="#ffffff" text="#000000">
<br>
<p style="margin-bottom: 0cm; margin-top: 0pt;">Florian Loretan wrote:<br>
</p>
<blockquote
cite="mid:f968e9760804102337v281f7befp36175880ea48d47@mail.gmail.com"
type="cite">On Thu, Apr 10, 2008 at 11:25 PM, Zohar Stolar <<a
moz-do-not-send="true" href="mailto:z.stolar@gmail.com">z.stolar@gmail.com</a>>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">[...]<br>
On the other hand, there should be a way of selectively not displaying
some or all messages, in a comfortable manner. How about a
hook_message_alter? Has this ever been discussed?<font color="#888888"><br>
</font></blockquote>
</div>
<br>
I actually wrote a patch to add a hook_message_alter, but after some
investigation it turned out not to be a viable solution. Among other
issues, messages do not have a unique identifier that lets you target
them individually, and errors in the implementations of the
hook_message_alter hook only show up on the next page load. <br>
</blockquote>
I guess the patch should include a modification of drupal_set_message,
to add a unique message identifier.<br>
Such a method is used with drupal_mail, that forces a unique identifier
for each out-going mail. However, modules don't usually send mails as
often as they present messages, so this solution can be too hard to
implement (imagine that you have to track all your messages, and give
them unique ids... ). Adding messages to a modules would then become a
nightmare.<br>
If we want to communicate with the users, then presenting them messages
should stay an easy thing to do.<br>
<br>
<br>
(I notice this thread is loosing contact with its subject... going back
to the discussion about install messages:)<br>
<br>
Relating to what Earl mentioned before ("When installing a new module,
I still have trouble figuring out what to do next"):<br>
In the efforts of making Drupal more user-friendly, I also think that
the install messages can include a little notice of what to do next.
For example:<br>
after enabling "blog" - have a link to the admin/content/types/blog<br>
after enabling "contact" - have a link to the admin/build/contact, and
remind the user to activate the menu item<br>
after enabling "comment" - remind the user to check permissions, and
configure individual content types settings<br>
<br>
etrc.<br>
<br>
</body>
</html>