It definitely needs reworking. But my problem is, on preview it goes:<br><br>1 - execute amazon_form(&$node)<br>2 - execute amazon_node_form_validate($form_id, &$form_values) with NO access to $node<br>3 - execute amazon_view($node) with NO access to $form_values
<br>4 - execute amazon_node_form_validate($form_id, &$form_values) AGAIN, with NO access to $node<br><br>I suppose I could toss a copy of $form_values into a global variable but that's something I actively try to avoid, to make debugging easier.
<br><br>Once I figure this out, I'll work with you on your filter.<br>
<br><div><span class="gmail_quote">On 1/6/06, <b class="gmail_sendername">Jeff Eaton</b> <<a href="mailto:jeff@viapositiva.net">jeff@viapositiva.net</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;">
<div><font face="Verdana" size="2"><span>I noticed that a
lot of the heavy lifting for the moduel is done in validate, including the
actual population of the node object with the amazon item information. The only
thing I can think of off the top of my head is to:</span></font></div>
<div><font face="Verdana" size="2"><span></span></font> </div>
<div><font face="Verdana" size="2"><span>Retrieve the
amazon data from scratch whenever a preview is built, based on the known ASIN
value. use the 'Validate' hook to establish whether the asin(s) are valid but do
NOT save, then retrieve the amazon data again and actually save it on submit. It
would entail more round-trips to amazon, but it would work cleanly unless I'm
missing something. Anyone? Thoughts? Corrections? Maybe you're already past that
point and I'm just echoing. :)</span></font></div>
<div><font face="Verdana" size="2"><span></span></font> </div>
<div><font face="Verdana" size="2"><span>Validate did a LOT
of heavy lifting in the old forms system, and that's been reduced with the new
api. It requires reworking some steps in more complicated
modules.</span></font></div>
<div><font face="Verdana" size="2"><span></span></font> </div>
<div><font face="Verdana" size="2"><span>--Jeff</span></font></div>
<blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div></div>
<div dir="ltr" align="left" lang="en-us"><font face="Tahoma" size="2"><span class="q">-----Original Message-----<br><b>From:</b> Earl Dunovant
[mailto:<a href="mailto:prometheus6@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">prometheus6@gmail.com</a>] <br></span><span class="q"><b>Sent:</b> Friday, January 06, 2006 4:31
PM<br><b>To:</b> <a href="mailto:development@drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">development@drupal.org</a><br><b>Subject:</b> Re: [development]
update hooks/APIs documentation<br><br></span></font></div><span class="q">My current task is
figuring out how to properly do the preview when the form is built BEFORE
validation or or submit hooks are invoked and neither hook has access to the
node object, nor do the node validation, insert and update hooks have access
to the form object. And this is my first look at image.module, which is
suggested as an example.<br><br>It's weird...I had less problems with the bulk
import form.</span></blockquote>
</blockquote></div><br>