<html>
<!-- BEGIN WEBMAIL STATIONERY -->
<head><style type='text/css'>
p {
margin: 0px;
color: #330066;
}
.spring {
font: normal 80% Verdana, Helvetica, sans-serif;
color: #330066;
}
</style></head>
<body>
<table background="cid:spring_01.gif" width='100%' height='100%' cellpadding=0 cellspacing=0 border=0>
<tr><td colspan=3 height=40> </td></tr><tr><td width=40> </td><td class='spring' height='300' valign=top>
<!-- WEBMAIL STATIONERY spring -->
<DIV></DIV>
<DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">
<P>William Smith wrote: <BR><BR>> altered her module's weight intentionally and for (presumably) good reason. </P>
<P>It's not terribly material, but the reason is because we wanted to "rescue" nodes from a user that gets deleted. The user.module does bad things before calling our module. There is an open issue about that.</P>
<P> </P>
<P>>It sounds as though your suspicion is correct that because your code is</P>
<P>> being called before the node module's code,</P>
<P>Actually, I don't believe that node.module is involved at all. This is done in theme.inc.</P>
<P> </P>
<P>Further, it dawned on me that the user timing issue is now actually in a separate add-on module, so I set the main module's weight to 1, so that it would run later and it made no difference.</P>
<P> </P>
<P>My suspicion now is that the theme.inc code runs after all the preprocess functions and there's not a lot I can do, except open an issue against D7 to have it check to see if that variable is already set before it changes it. That won't help my D6 code though.</P>
<P> </P></BLOCKQUOTE></DIV>
<DIV class=signature id=signature>--<BR>Nancy E. Wichmann, PMP <BR><BR>Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.</DIV><!--<BR>-->
<DIV> </DIV>
<!-- END WEBMAIL STATIONERY -->
</td><td width=40> </td></tr></table>
</body>
</html>