that helps in the case, where one does not change any objects in the ZODB, but if one for example deletes objects in the formprocessing, which you can mark in the formcode, then the deleted objects still show up in the form, cause it is all done in one transaction. Dylan Reinhardt wrote:
When you want to immediately display the results of changing information in a form, I find it works best when a form submits to itself rather than to an intermediate target. Doing this avoids the caching/latency issue altogether.
For example:
---------------- <!-- Process changes first -->
<dtml-if is_form_submit> Do form processing here... </dtml-if>
<!-- Draw the form with the latest data available -->
<form target=<dtml-var URL> method=post> <input type=hidden name=is_form_submit value=1> Form code goes here... </form> ----------------
HTH,
Dylan
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
-- Mit freundlichen Grüßen Joachim Schmitz -------------------------------------------------------------------- AixtraWare Ingenieurbüro für Internetanwendungen Telefon: +49-2464-8851, FAX: +49-2464-905163 --------------------------------------------------------------------