Not sure what Moshe intended, but I added a "value" form element to all nodes called "_currentstatus" storing the $node->status. Then, I compare it to the nodeapi $node->status on update/submit, and 0 changing to 1 represents a new publish.
<br><br>Yes, it's quite "hack-ish" but it works well enough. An argument could be made to store this state change information in the default node, but I guess that'll happen when enough people want it.<br clear="all">
<br>-- <br>Dan Ziemecki<br>Philosopher. Curmudgeon. Nerd.<br><br><br><div><span class="gmail_quote">On 9/30/06, <b class="gmail_sendername">Peter Wolanin</b> <<a href="mailto:pwolanin@gmail.com">pwolanin@gmail.com</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">With the caveat that you may have problems under PHP5 (see my previous<br>message), one possible way to check this would be to call node_load in
<br>your hook_nodeapi to get the cached node object that would have the<br>pre-edit value for publication status.<br><br>However, this (and most possible solutions) are a little hackish.<br>I'm not sure I know exactly what Moshe has in mind. For an example
<br>where the moderation status is preserved via the hook_nodeapi<br>implementation see this module of mine:<br><br><a href="http://drupal.org/project/content_moderator">http://drupal.org/project/content_moderator</a><br>
<br></blockquote></div><br>