David Pratt wrote at 2005-8-22 15:12 -0300:
...
# Using default put method from NullResource
def _default_PUT_factory( self, name, typ, body ):
...
def PUT(self, REQUEST, RESPONSE):
...
Why do you override these methods as apparently, you do not use
them...
I guess my thought
David Pratt wrote at 2005-8-21 23:43 -0300:
...
# Catch put in traversal
def __bobo_traverse__(self, REQUEST):
method=REQUEST.get('REQUEST_METHOD', 'GET')
if method == 'PUT':
PUT(REQUEST, RESPONSE)
Usually, __bobo_traverse__ gets
Hi Dieter.
On Monday, August 22, 2005, at 01:45 PM, Dieter Maurer wrote:
David Pratt wrote at 2005-8-21 23:43 -0300:
...
# Catch put in traversal
def __bobo_traverse__(self, REQUEST):
method=REQUEST.get('REQUEST_METHOD', 'GET')
if method ==
David Pratt wrote at 2005-8-19 15:38 -0300:
First step is to make new type - will
do this today but might need to ask a question or two when I get to
bobo traverse portion. When you say another auxillary object, what kind
of object is this so I understand a bit better?
One similar to
Hi Dieter. I think I understand. What I have done so far is to make a
upload folder product. I have taken the portal folder base class to
create a portal upload folder base class, commented out the PUT_factory
method and added the following methods for bobo traverse and PUT. I am
then
David Pratt wrote at 2005-8-18 20:57 -0300:
...
All for exception of one thing - I want to
delete the object as part of the workflow since it is no longer needed.
...
I use manage_delObjects like so:
# Delete original object from the upload folder
Hi Dieter. This is an excellent idea! I was looking at this to
restrict the content that could be put into the folder as well. This
fits really well with this too. First step is to make new type - will
do this today but might need to ask a question or two when I get to
bobo traverse
I guess what I have learned so far is that the data of an object in an
automatic workflow transition
from a PUT is not there until it completes - but the good thing is that
the data is in the request body variable.
So I can check the request method and if a PUT, use the request's body
David Pratt wrote at 2005-8-17 18:08 -0300:
Hi Dieter. Many thanks for your reply. The place in my workflow that it
failed was opening the image.
IOError: cannot identify image file
...
error here -- image = PIL.Image.open(original_file)
This does not look like a workflow problem.
Instead,
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
David Pratt wrote at 2005-8-17 00:13 -0300:
...
but when I FTP
my images to this directory it fails giving me a 426 Error creating
file.
Look at your error_log object to find out the real reason
(and get the traceback).
--
Dieter
___
Zope maillist
Hi Dieter. Many thanks for your reply. The place in my workflow that it
failed was opening the image.
IOError: cannot identify image file
for image_data in image_data_list:
# Get original image data into string object
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
13 matches
Mail list logo
