[Zope-dev] Policy for Collector-Issues 545 and 1217?
Hi, there are two collector-issues related to problems when Zope-Objects get ids like 'content_type' or 'URL1'. I think this problem exists for all names used in the REQUEST-object or general acquisitionable attributes of ObjectManagers. http://zope.org/Collectors/Zope/545 http://zope.org/Collectors/Zope/1217 I don't think that these issues cannot easily be solved in Zope2 without breaking the whole acquisition-magic. What to do? The problem exists, but a fix is hard to find... if at all. Accepting? Rejecting? Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: The bleak Future of Zope?!
Martin Kretschmar wrote: Maik Jablonski of the german speaking Zope Users Group DZUG issued a pretty bleak outlook for the future of Zope. What are your oppinions? Hi to all, I'm not able to respond to all mails in this thread due to a trashed shoulder (very unlucky cyclocross-crash last week), but I'm feeling the need to make some simple remarks. 1) Chris is right: Yes, I've had a bad day...;) 2) My initial mail wasn't intended for zope-dev. So I'm a little bit suprised that it made it to this list. If anyone feels offended (esp. Jim), I'm very sorry, but if I want to complain about Zope2/3 on this list, I would use other words. The initial mail (written in german) was written in a state of fear (not anger). The translation (and maybe my mail itself) didn't transport my fear about the future of Zope very well I guess. 3) To say it clearly: I would have never started the German Zope User Group two years ago if I were not totally convinced of Zope (the technology the community). Bringing up a community in Germany (with several big conferences, etc.) was a lot of work (believe me), so I don't feel as a usual freerider who only complains but does not give something back to the community. But my resources are limited as well, so I can't take additional tasks as documentation, release-management, etc.pp... If this means I'm not allowed to say anything critical about these points then I'm very, very sorry making any remarks... 4) Stephan, you're right, I did not study Zope3 (and the zope3-dev-list) very well. My initial approach to Zope3 ended with the impression: huh, complicated stuff, but I don't have time to work it out in the moment! Then I've talked to many people who said similar things about their first experience with Zope3 (maybe I've talked to the wrong people, than this is my fault, sorry again). So I came up with the impression: yeah, Zope3 is cool, but complicated (stated as 'academic' in my mail)! (at least if you don't have the time to work things out by diving into the source). And if you run several mission critial applications you don't have time to look into this kind of new stuff. But you're right, Stephan: If you want to stay in technology business, you have to invent (read: improve by a complete redesign) the wheel many times. So I don't think that Zope3 is useless for the future of Zope. 5) But there's some kind of a bad impression in my mind (maybe it is without any foundation, than all things are in best state): Zope2 isn't maintained very well anymore due to limited ressources (bug fixes, documentation, see mail from Andreas), but Zope3 isn't production ready at all. So if you talk to people making the decisions in the IT-business they say: Zope2 seems to be a dead horse, Zope3 is just a child which learns to run... Let's settle our business on more approved technologies like Java / Net (or even PHP...;)). We can't wait anymore... This kind of frustrating impression made me writing the mail about the future of Zope, because I'm in love with Zope and not Java, Net or PHP... [[[6) Just a personal note to Stephan: You're right again about the quickdirty design of some of my products (esp. Epoz, I have simply no knowledge about JavaScript at all (and I don't like it), but Epoz seems to do a good job for many people until Kupu is finished). My job (read: strength) is custom-application-development (talking to customers and reading their minds, developing prototypes to track down the issues the customer meant and didn't told me and didn't dream of etc.pp., developing securing maintaing web-applications which need to work in an environment with 20.000 students 2000 office-workers etc.), not application-framework-design-nor-development, so my products are just some wired by-products of my daily work. About MailBoxer: If you think MailBoxer is just another mailinglistmanager (like mailman) you didn't get the idea of it... MailBoxer is a lightweight mailinglist-framework (!, yes I've done some kind of framework, it can be done better, but it solves my problems this way) which is built on the power of Zope to achieve some things you can hardly achieve with Mailman (at least I wasn't able to to). So I've reinvented the wheel once more to solve some of my application-needs...]]] Hope this made things a little bit clearer... I didn't want to attack ZC / Zope3-devs / the community or anyone else. I'm just fearing that we miss the train for Zope2 AND Zope3 in the moment... if you don't think so, I'm fine...:) Keep zoped, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] RE: Resolved security-related collector issues for thepublic?
Hi Brian, Brian Lloyd wrote: As the person who unfailingly gets flamed no matter which way the decisions leans :), I think we are probably at a point where we should have an official, documented and community-agreed-to policy on how these kinds of things will be handled. My intent was not flaming anyone... Sorry for that. I just tried to take the voice of the average Zope-Admin (installs Zope from a recent stable release, waits for the security-maintainers of distros to get security patches etc.). At a minimum, having a clear and documented policy would provide the benefit of 'no surprises' - if you disagree with the policy, or some aspect of it, you would at least be able to plan around it. Very good idea...:) If all Zope-Admins can read before an installation: Security exploits will be exposed to the public as soon as they're resolved in the CVS everyone will should run Zope out of CVS. My point was: Give people a chance to react on exposed security flaws. The statement above will do that because people should be prepared...:) Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Resolved security-related collector issues for the public?
Hi, there were several security-related fixes in the collector (and the collector-mailing-list) in the last days. Normaly security-related stuff is not visible for the public... and this seems to be good to avoid exploits etc. Lots of security-stuff is fixed now, but I don't think that all people will migrate their servers as soon as possible (due to limited time, the experience of the Zope-2.6.3-desaster, vacations, etc.pp.). With all the mentioned security-exploits in the collector out there, the probability of attacks will rise. And I don't think that this will shed a good light on Zope. My proposal: Can we have a delay for making security-related fixes public? Just a month or two or so... Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Resolved security-related collector issues for the public?
Hi Jamie, Jamie Heilman wrote: Hiding the bugs doesn't avoid anything, it just leaves zope administrators helpless in the dark. ... How exactly was ZC supposed to release a new version of Zope with the fixes but at the same time not divulge the nature of the security flaws? Release an obsfucated binary distribution and say Trust Us? That doesn't sound very much like open source. In the past we had something like Hotfixes for security problems... Easy to install for the average administrator and that's it. I can check out the current Zope from a CVS... So getting security fixes is no problem for me. But I'm not an average Zope-Admin or -User. There are many admins / users out there who aren't able to do this (maybe they should learn it, but that's another point). Installing Zope 2.6.3 was a big mess (even renaming in the ZMI was broken) and most people rolled back to 2.6.2. Some people run even 2.5.1 (lots of Debian-Users etc.). If we don't have a easy-to-install-security-fix for such people (or a so called stable release, which works out of the box) we should a little bit cautious about releasing exploits. That's my point... Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: bugday results.
Chris McDonough wrote: Bugs squashed: 22 1105, 1107, 1108, 273, 331, 350, 382, 391, , 1095, 1074, 1110, 1016, 616, 682, 822, 582, 445, 799, 923, 426, 1100. Not bad for a five-person IRC channel. ;-) Hi, just as a little post-contribution from me (I was out of office all the day and couldn't join :( the bug day), all the links to the fixed bugs for lazy click-and-view-people like me: http://www.zope.org/Collectors/Zope/1105 http://www.zope.org/Collectors/Zope/1107 http://www.zope.org/Collectors/Zope/1108 http://www.zope.org/Collectors/Zope/273 http://www.zope.org/Collectors/Zope/331 http://www.zope.org/Collectors/Zope/350 http://www.zope.org/Collectors/Zope/382 http://www.zope.org/Collectors/Zope/391 http://www.zope.org/Collectors/Zope/ http://www.zope.org/Collectors/Zope/1095 http://www.zope.org/Collectors/Zope/1074 http://www.zope.org/Collectors/Zope/1110 http://www.zope.org/Collectors/Zope/1016 http://www.zope.org/Collectors/Zope/616 http://www.zope.org/Collectors/Zope/682 http://www.zope.org/Collectors/Zope/822 http://www.zope.org/Collectors/Zope/582 http://www.zope.org/Collectors/Zope/445 http://www.zope.org/Collectors/Zope/799 http://www.zope.org/Collectors/Zope/923 http://www.zope.org/Collectors/Zope/426 http://www.zope.org/Collectors/Zope/1100 Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Can someone fix 893?
Hi, there are already patches and test-cases for http://collector.zope.org/Zope/893 (MailHost._mungeHeaders is broken for full-named-email-addresses like Jablonski, Maik [EMAIL PROTECTED] ) When something is still missing, I will provide it... Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Heads-up: 2.6.2 b3 and 2.7 a1 releases
Brian Lloyd wrote: and all of the items considered important to get into the 2.7 alpha 1 have been merged. Hi Brian, I've talked to Andreas at EuroPython yesterday about the ZRest-Product, which was originally written by Richard Jones. Andreas added this to 2.7. In my opinion we should go for a more general TextDocument-Content-Type, which allows switching between RestructuredText, StructuredText and PlainText (newlines_to_br). I've looked into ZRest-Product on my travel back from EuroPython and would think, that the additional switchable-text-format-support could be easily integrated. Should I provide patches? I would also provide the missing icon for the ZRest-Product. Another one: If I implement the described changes, we should switch ZRest to a more general meta_type: TextDocument (formerly ReStructuredText Document). How about that? I think that this is no showstopper in general, but switching the meta_type could be one, if people start to work with 2.7... Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Patching object class
Florent Guillaume wrote: I have the need to update some persistent objects in a ZODB to change their class. One use case comparable to the one I have would be to change all objects of type Folder to OrderedFolder. To do that, I envisionned finding all thoses objects and doing ob.__class__ = OrderedFolder ob._p_changed = 1 Would this work ? If not, what other hack could I do ? The idea being that I don't want to recreate all the objects. Maybe you should install OrderedObjectManager for bringing order to all your folders. http://www.zope.org/Members/mjablonski/OrderedObjectManager I'll release an api-updated version when 2.7 is released. Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Any thoughts on when Zope 2.7 beta1 might be available?
Chris McDonough wrote: Hi Craeg, 2.6.X appears to work great with Python 2.2. We even removed the startup warning lately. I'd go this way were I you as 2.7 is probably still some time away and you almost certainly don't want to be tracking the trunk, as its relatively volatile at the moment. Hi Craeg, I run 2.6.1 with Python 2.2.2 with several additional products without any problems. I learnt my lessons from upgrading to early major releases of Zope, so I would go for 2.6.1 with Python 2.2.2 instead of waiting for a (maybe) buggy release of 2.7.0... Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Using index.htm(l) files like index_html
David Cain wrote: How can I customize my Zope server to treat index.html and index.htm files like index_html files? Your question has nothing to do with developing the Zope Application Server, but only with developing applications with Zope. So you should ask on [EMAIL PROTECTED] Your question: Place a DTML-Method into your Zope-Root with: dtml-var _['index.html'] (you can add some condition tests for index.htm of index.html if you want to.) -mj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] CRITICAL!!!! CVS: Zope/lib/python/OFS - Image.py:1.141.4.3
Hi,
BIG PROBLEM WITH THIS CHECK-IN FROM YESTERDAY: I've updated my ZOPE and
now all Images are broken!!! ZOPE lives behind a SQUID.
I think that
RESPONSE.setBase(None)
is NOT a good idea at all!!! Commenting this out and all works as
expected...
Maybe someone else can check this issue...
-mj
Update of /cvs-repository/Zope/lib/python/OFS
In directory cvs.zope.org:/tmp/cvs-serv2993/lib/python/OFS
Modified Files:
Tag: Zope-2_6-branch
Image.py
Log Message:
Check in for #342 on behalf of slinkp
=== Zope/lib/python/OFS/Image.py 1.141.4.2 = 1.141.4.3 ===
--- Zope/lib/python/OFS/Image.py:1.141.4.2 Wed Nov 13 14:18:41 2002
+++ Zope/lib/python/OFS/Image.py Mon Dec 16 19:40:23 2002
@@ -133,6 +133,7 @@
Returns the contents of the file or image. Also, sets the
Content-Type HTTP header to the objects content type.
+
# HTTP If-Modified-Since header handling.
header=REQUEST.get_header('If-Modified-Since', None)
if header is not None:
@@ -374,7 +375,9 @@
self.ZCacheable_set(None)
data=self.data
-if type(data) is type(''): return data
+if type(data) is type(''):
+RESPONSE.setBase(None)
+return data
while data is not None:
RESPONSE.write(data.data)
___
Zope-Checkins maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-checkins
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: CRITICAL!!!! CVS: Zope/lib/python/OFS - Image.py:1.141.4.3
Andy McKay wrote: Well there you go, I deleted my sandbox and did clean cvs checkout and it seems to have updated correctly. I've put back Paul's patches as he originally intended them to be. Sorry about that. Thank you, Andy! It works. I can see all my pretty images again... even if Zope runs behind a Squid...:) Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: information disclosure vulnerability
Jerome Alet wrote: probably the HelpSys object shouldn't be available by default to non-authenticated users, because it gives too much information on the currently installed products. access any Zope site this way : http://your.zope.site/HelpSys and you'll learn what products are available on the server. Another way to gather this data would be: http://YourServer/Control_Panel/Products/ExternalEditor gives Anoynmous the ZopeStartPage if ExternalEditor is installed and a SiteError if not. -mj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Collector 697 should be critical!!!
Hi, http://collector.zope.org/Zope/697 should be set to critical, because it results in loosing essential data. Case: We store much of our Keywords etc. in multiple-selects. Everytime a user edits and saves such a multiple-select, all items with NON-Ascii-characters [german umlaute for example] won't be shown as selected cause of the bug. So the next Save Changes will loose all this items. I don't know where's the best place to fix this issue, but it need to be fixed as soon as possible... Cheers, Maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: What do I get from 'cvs co Zope'?
Stefan H. Holek wrote: It appears that when I currently do 'cvs co Zope' I get a version that already requires Python 2.2.2. GvR's zdctl.py stuff uses lambdas in a way that Python 2.1 does not grok. How can I get at a Python 2.1.3 post 2.6.0 checkout? You have to specify the correct branch: cvs -z7 -d :pserver:[EMAIL PROTECTED]:/cvs-repository checkout -r Zope-2_6-branch Zope please read: http://dev.zope.org/CVS/FrontPage -mj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Collector 697 should be critical!!!
Casey Duncan wrote: If this is critical for you, then you will probably need to develop a patch for it in order for it to make it into 2.6.1; unless anyone else wants to volunteer. I don't feel comfortable enough with the unicode converters to do this. For me it's critical, but maybe for others too who haven't even noticed the problem. They loose content everytime someone Save Changes on a PropertyTab with multiple-selects... That's why I'm thinking that this bug should be marked as critial. I don't have much experience with the unicode-converters too... that's my problem for this issue...:-( Abel Deuring told me a patch, which solves the problem in the meanwhile: In OFS/dtml/properties.dtml I replaced select name=xyz:utf8:list multiple with: select name=xyz:utf8:list:string multiple It works for me, but I'm not sure, if this is a good approach on this problem (think of the integers as items for the multiple-select). -mj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: What catalog/index to use ...
Guido van Rossum wrote: I don't know where you would expect a patch to be found, but in this particular case the Zope Collector is a good place to look: http://collector.zope.org/Zope/597 Use the collector, Luke! ;-) Um, that's not a patch. Can you attach a context or unified diff to the collector item? sorry for that. but the only difference between old and new code is the (?L)-flag in the reg-exps. cheers, maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: What catalog/index to use ...
Guido van Rossum wrote: The problem seems to be that ZCTextIndex indeed does not do the splitting right if German Umlauts are used. There is no option for Unicode-aware splitter. Instead of a Vocabulary it uses a Lexicon, which just offers two options: HTML aware splitter and Whitespace splitter. I haven't tested the whitespace splitter yet, but the HTML aware splitter did not do the Umlaut thing right without the patch, i.e. it used umlauts as splitting characters ... That's just what the default ZMI interface for ZCTextIndex offers. It's easy to add your own splitter by writing a few lines of Python code. RTSL. of course everyone can write his own Splitter... one for german, one for french, etc.pp. but what is the problem with the patch? is pythons-regexp (?L) not just intended for this simple way of localizing software? and think of the european market: no one will buy Zope, if it is not working with your native language out of the box. and that's what the patch for... cheers, maik -- Maik Jablonski __o www.zfl.uni-bielefeld.de _ \_Deutsche Zope User Group Bielefeld, Germany (_)/(_) www.dzug.org ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: What catalog/index to use ...
Joachim Werner wrote: Does it make sense to get ZCTextIndex fixed (there seems to be a patch in the collector already) or should I go with TextIndexNG? If yes, is it ready for production environments? hi, I've submitted a patch for locale-support for ZCTextIndex: http://collector.zope.org/Zope/597 I run this patch on a production site [most content is german] without any problems. I think, if all test-cases for ZCTextIndex succeed with this patch, it should be merged into the next official release so all european zopers can use ZCTextIndex without patching it... in my opinion: high priority for this one done :-) cheers, maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: What catalog/index to use ...
Casey Duncan wrote: The main reason I have not merged this already is that I lack a sample to make a new test with. If someone can provide me with some content samples that break now, but work with the patch, I will make a new test and checkin the fix for 2.7 perhaps 2.6.1 if desired. -Casey hi Casey, try some words with german umlaute. things like: mülltonne waschbär behörde überflieger the last one will work without the patch. explanation: the first character is splitted away [non-ascii-character] [both for storing the word in the Lexicon and resolving the query-words through the queryparser]. so it will in both cases end up in berflieger searching for 'überflieger' will give you correct results. this is the reason, why some people think, that ZCTextIndex works with german 'umlaute', but it does not...;-) hope this is helpful. cheers, maik ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] FTP issue or Alternative
hi, this list is for the development of ZOPE. you better ask on [EMAIL PROTECTED] for help using ZOPE. a first hint for your problem: http://www.zope.org/Members/arielpartners/ExternalFile -maik jablonski On Thu, 2002-06-27 at 19:25, Ahsan Imam wrote: Hello All, I am trying to FTP images into various zope directories. Some of the images show in zope as 0k. When I check these out in the file system they are greater than 0k and I can view them. So I put like a 5 second sleep in my script before every image is ftp'ed. This method did reduce the number of 0k files however it did not eliminate the problem. I do not want to use the use 5 second method as the scripts takes a very long time to complete. Is there something I am not aware of? What other method can I use? Can I simply take a OS directory structure and import it into zope? I am not sure how. Can you point me some sample code or literature. Your help or guidance is much appreciated. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] symbolic link patch
hello, i found this patch for creating symbolic links within zope: http://lists.zope.org/pipermail/zope-dev/2001-August/012711.html snip - edited CopySupport.py - copied the manage_pasteObjects method to a manage_pasteMonikers method - commented the #ob=ob._getCopy(self) line (the duplicate object part) - added a Paste Ref button to the lib/python/OFS/dtml/main.dtml file that calls the pasteMonikers method /snip it seems to be great for my purposes works fine i plan to use it on a production system. has someone any information about problems with this kind of patching? something like breaking the database in long terms or even more ugly? thank you, Maik -- Maik Jablonski Zentrum fuer Lehrerbildung Universitaet Bielefeld Germany ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
