|
From: Craeg S. <cs...@ar...> - 2003-04-28 21:36:04
|
Yikes. This is bad news. However, please see the following: http://mail.zope.org/pipermail/zope-dev/2003-April/019341.html I am cc-ing this to the development mailing list. I think you may have identified our first bug :) Zope clearly has different behavior for objects > 64K and we probably just need to do some buffering or something. Thoughts? --Craeg > Ever since this wonderful product has been released, I have been playing with it, and have come to a bump in the road that I simply can't get over. Here is the basic problem, let's say I have a folder called "forest" and I am populating "Forest" with uploaded files (or Add --> File in the ZMI). Works fine, so cool -- I can FTP these trees into my forest and each renders beautifully with the magic of a modular XML transformer. OK, so it works fine _if_ the XML files are under 64Kbytes. If I try to process a freshly uploaded file, it hangs and eventually spits out "EOF reached" in the zope stupid log. As if this wasn't strange enough... It continues -- so I 'modify' the OFS fileEdit.dtml page to allow me to directly edit the text of the XML file (it won't normally display if the text is >= 64K). So I make absolutely NO changes whatsoever to the XML on the screen and click "Save Changes". If I slap my modularxform at the end of the URL, the transform works. So, I am unsu! re of where the problem lies -- I have been trying different things in the Zope code (leaving the XML methods untouched). Any thoughts? > |