On 12/27/06, <b class="gmail_sendername">Gabor Hojtsy</b> &lt;<a href="mailto:gabor@hojtsy.hu">gabor@hojtsy.hu</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Maybe it is not too late to stuff a few module_invoke_all() calls to the<br>proper places so module/theme changes are advertised for modules to watch<br>for. If it is too late, I would be very interested if others faced the
<br>same problem and how did they solved it.</blockquote><div><br><br>I think having a module_invoke_all() when a module/theme is enabled/disabled is<br>a very good idea.<br> <br>Examples are: sites with multiple admins can have an email send to a mailing list
<br>to inform them of site changes.<br><br>But with the code freeze, it may be too late to do it for 5.0. Although it would only<br>be Gabor&#39;s code that would be using it.<br><br>Gabory, if it does not make it to 5.0, simply create a few patches and bundle them
<br>with your module. Hopefully these very same patches would go in my the time it is<br>6.0.<br></div></div>