I should have stated that my workflow script checks for image type in
this directory. It uses PIL to make a variety of image sizes, but uses
the pil image data to create a new object type in another directory.
The workflow script deletes the image in the original directory after
this has been done. Is there some way to perhaps test the size of the
image's data and have the script wait until the data is there or
involve the temp directory in some way (since uploading images through
a form works with this workflow) so that the image is whole before the
workflow script attempts to use it?
Regards,
David
On Wednesday, August 17, 2005, at 12:13 AM, David Pratt wrote:
I created a workflow for my images so that they would be processed as
soon as they are transferred into a specific directory. It works fine
when I cut and paste images to the directory it acts on but when I FTP
my images to this directory it fails giving me a 426 Error creating
file. My thinking is that the workflow may trying to use the image
before its data has arrived. I can FTP into the directory normally if
I temporarily change my workflow to act on a different directory - so
this verifies that the problem is between my workflow and FTP. Can
someone suggest a workaround to ensure the image is completely
available before the workflow tries to use it. I want to avoid any
kind of cron process in a big way as well. Many thanks,
Regards,
David
_______________________________________________
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 )
_______________________________________________
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 )
