- Zope - Zope lists

Mounting ZODB issue
by Jonathan Cleaver 09 May '06

09 May '06

Hi all, I am trying to mount the ZODB of a Plone 2.0.5/Zope-2.7.6/Python 2.3.5 on a Plone 2.1.2/Zope-2.8.5/Python 2.3.5 I have created the appropriate entry in the zope.conf thus... <zodb_db weeble> mount-point /weeble <zeoclient> server 10.4.96.98:9999 storage 1 name zeostorage var $INSTANCE/var </zeoclient> </zodb_db> I know that this setup works on another Zope instance, because I cut and pasted it out of the zope.conf there. I do not believe that there are any firewall issues between the servers because a seperate instance on t the same machine is already connecting to this ZEO server. The problem that I have is that when I create a ZODB Mount Point, the weeble mount point appears available but when I click Create the browser just sits there waiting for a reply that never comes. The ZODB Mount Point is not created. The Zope instance, however, does not appear to deadlock; I can just stop the browser browse the ZMI perfectly well. Is this a Zope version issue? Is there a 'rule' in ZEO where it can only accept one connection from each client machine? Or have I just missed a step in the process? Many thanks in advance. Jonathan Cleaver Defence Academy - UK

7 10

Preventing files from being viewed by web clients
by Brian 09 May '06

09 May '06

I have a flash app that accesses .xml files. The source is viewable and some creative crackers have figured out how to meld a url together to get vital information from those .xml's. I need to prevent the web client from directly accessing them. Is there a directive (such as Apache's) or mechnisim to keep web clients from accessing yet allow my app access these files? Somthing like <FilesMatch \.(?i:gif|jpe?g|xml)$> Order allow,deny Allow from <some file name> Deny from all <some other web trick> </FilesMatch> in zope.conf or ??? TIA Brian

5 4

Re: [Zope] long name as ID
by BKJ＠telefonica.net 09 May '06

09 May '06

Hi Sergio! You can change the ID to tittle, adding the following line to your archetype: Ex: schema = schema ----> at_rename_after_creation = True <------ content_icon = ..... Bye! ----Mensaje original---- De: sofrosine(a)gmail.com Recibido: 09/05/2006 13:16 Para: <Zope(a)zope.org> Asunto: [Zope] long name as ID Hi all, I have developed an archetype based product named msf_folder, and it stores the id with a very long string like msf_folder.2006-05-09.8558117482, instead of the title I have written. Is this a normal behaviour? How can I change the ID to the title I have given it? Thanks Sergio _______________________________________________ Zope maillist - Zope(a)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 )

1 0

long name as ID
by Sergio Gomez 09 May '06

09 May '06

Hi all, I have developed an archetype based product named msf_folder, and it stores the id with a very long string like msf_folder.2006-05-09.8558117482, instead of the title I have written. Is this a normal behaviour? How can I change the ID to the title I have given it? Thanks Sergio

2 1

Re: [Zope3-Users] Zope 3.3.0 beta 1 released!
by Stephan Richter 08 May '06

08 May '06

On Monday 08 May 2006 17:07, Lorenzo Gil Sanchez wrote: > Is there a small document or howto explaining how to migrate from the > old skins/layers to the new system? I migrated by reading the deprecation messages and following their advice. :-) Unfortunately, we do not have the resources to write migration guides or new feature how-tos. I hope that someone (thinking specifically of Jeff Shell here) will blog on the new features and changes. :-) Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training

1 0

Zope 3.3.0 beta 1 released!
by Stephan Richter 08 May '06

08 May '06

Hello everyone, The Zope 3 development team is proud to announce Zope 3.3.0 beta 1. Zope 3 is the next major Zope release and has been written from scratch based on the latest software design patterns and the experiences of Zope 2. Cleanup of the Zope 3 packages has continued to ensure a flexible and scalable platform. We continued the work on making the transition from Zope 2 to Zope 3 by making Zope 2.10 use even more of the Zope 3 packages. But we're not there yet. **You can't run Zope 2 applications in Zope 3.** Downloads http://zope.org/Products/Zope3 Installation instructions for both Windows and Un*x/Linux are now available in the top level "README.txt":http://www.zope.org/Products/Zope3/3.3.0b1/README.txt file of the distribution. The binary installer is recommended for Windows. Zope 3.3 requires Python 2.4.1 to run. You must also have zlib installed on your system. Most Important Changes Since 3.2 - Provided a new component registry API that allows multiple component registries to be combined more flexibly than before. See 'zope.component.interfaces.IComponentRegistry' for more information. - Greatly simplified local-component registration. See 'zope.component.interfaces.IComponentRegistry' for more information. - Moved many packages out of zope.app to make them easier to use outside of Zope. - Change the session credentials plugin to make it configurable in which fields it looks for the credentials. - Added a new API for collating text. You can now adapt a locale to 'zope.i18n.interfaces.ILocales.ICollator'. You can then use that to sort strings, such as menu entries, in a locale-specific fashion. - A new 'zope.annotation.factory' helper function that makes it easier to create annotations. Also added a README in 'zope.annotation' which explains how to use it. - Added a more complete set of widgets for fields that use iterable sources. These widgets now mirror the set provided by vocabulary-based fields. - Added a cleaner and more robust API to testbrowser for setting file-upload data. - Deprecated several ZCML directives: * factory * vocabulary * content (as an alias to the class directive) * modulealias * renderer:renderer - The 'browser:layer' directive and the 'ILayer' interface has been deprecated. Registering layers has become obsolete, layers should be created as interfaces extending 'IBrowserRequest'. - The 'browser:skin' directive has been deprecated. Skins should be created as interfaces extending 'IBrowserRequest' and can be registered using a simple 'utility' directive. - The 'ISkin' interface has been renamed to 'IBrowserSkinType'. For a complete list of changes see the 'CHANGES.txt' file. Resources - "Zope 3 Development Web Site":http://dev.zope.org/Zope3 - "Zope 3 Dev Mailing List":http://mail.zope.org/mailman/listinfo/zope3-dev - "Zope 3 Users Mailing List":http://mail.zope.org/mailman/listinfo/zope3-users - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments Thanks goes to everyone that contributed. Enjoy! The Zope 3 Development Team

1 0

LocalFS problems
by Dennis Allison 08 May '06

08 May '06

Chris, Andreas, others LocalFS product (1.3-andreas) seems to be having a problem with the <dtml-tree> tag in Zope 2.9.2/Python 2.4.2. The <dtml-tree> behavior is very different for a folder with three nested sub-folders (a list of the three nested sub-folders) that what is seen when pointed to a LocalFS with three nested subdirectories, even though they should be similar or the same. The problem seems to be with the tpValues() program in the LocalFS product which returns an empty list. The controlling flag, o.isPrincipiaFolderish, seems to be set to zero when it ought to have a value of 1 when the object being referenced is a LocalDirectory instance. As a result, instead of returning a list of sub-directories it returns an empty list. There seems to be some trickery going on with the isPrincipiaFolderish and the tree_view attributes, but I don't quite get what's supposed to happen. SmileyChris? I think these were your mods. Incidentally, the ZMI panel which uses <dtml-tree> seems to have the same sort of problems I am seeing when there is a LocalFS. Has anyone else encountered this problem? I plan to move to the 1.7-rc1 version, but there does not appear to be a fix for a bug of this sort in this latest release.

3 3

Metal:fill-slot *always* returns a <span>?
by Doyon, Jean-Francois 08 May '06

08 May '06

Hi there, I have a "master template" with a slot definition like this:  <div metal:define-slot="main"></div>  And another template which attempts to fill it with something like: <div metal:fill-slot="main" tal:define="childtopics python: here.aq_parent.getChildTopics(); childmaps python: here.aq_parent.getChildMaps(); topicmode python: len(childtopics) > 0;"> <h1 tal:content="here/Title"></h1> Now for some reason I can't figure out, the end result ALWAYS has <span> tags surrounding the content of the slot, despite the fact I say here they shoul dbe "div"'s ...  <span> <h1>Freshwater</h1> I've tried other things like: <div metal:define-slot="main" /> Or <metal:define-slot metal:define-slot="main" /> But no matter what I do, there's a span, even when everything says "div". This is a problem because the end HTML does not validate, and I work in a rather large organization that requires it's HTML content to validate ... I've tried looking through the TAL/PageTemplates code, but without much success ... What am I missing here? Is this a bug/misfeature? Could any one point to the source code that handles this? Thanks, Jean-François Doyon Internet Service Development and Systems Support / Spécialiste de dèveloppements internet et soutien technique Canada Centre for Remote Sensing/Centre Canadien de télédétection Natural Resources Canada/Ressources Naturelles Canada http://atlas.gc.ca Tel./Tél.: (613) 992-4902 Fax: (613) 947-2410

3 2

Re: [Zope] strange behaviour:can not access source-view.gif but a copy of it
by Dieter Maurer 08 May '06

08 May '06

robert rottermann wrote at 2006-5-3 16:10 +0200: >what I meant is that I only can access the trough its "normal" url >(using apache) > >www.ersigen.ch/view-source.gif > >never terminates What does the "wget -S http://www.ersigen.ch/view-source.gif" gives you? -- Dieter

2 2

ftp server deadlocking zope with DeadlockDebugger
by Michael Kaplan 08 May '06

08 May '06

Hello, about 2 weeks ago I reported about my ftp-problem (see attached listing). In the meantime I installed DeadlockDebugger-1.0.tgz from http://www.zope.org/Members/nuxeo/Products/DeadlockDebugger Here is the output of this program for the thread that seems to be responsible for the deadlock. This happens when I open a ftp connection to the server, cd to a directory and launch the 'ls'-command: Thread 11 (GET /dirname/manage_FTPlist): File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/ZServer/PubCore/ZServerPublisher.py", line 23, in __init__ response=response) File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/ZPublisher/Publish.py", line 386, in publish_module environ, debug, request, response) File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/ZPublisher/Publish.py", line 187, in publish_module_standard response = publish(request, module_name, after_list, debug=debug) File "/home/www/Zope-2.8.5-0/Products/PlacelessTranslationService/PatchStringIO.py", line 51, in new_publish x = Publish.old_publish(request, module_name, after_list, debug) File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/ZPublisher/Publish.py", line 104, in publish object=request.traverse(path, validated_hook=validated_hook) File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/ZPublisher/BaseRequest.py", line 272, in traverse bpth(object, self) File "/home/www/Zope-2.8.5-0/Products/LinguaPlone/I18NBaseObject.py", line 421, in __before_publishing_traverse__ stack.append('not_available_lang') File "/home/www/Zope-2.8.5-0/Products/LinguaPlone/I18NBaseObject.py", line 140, in getTranslation return l and l[0] or l File "/home/www/Zope-2.8.5-0/Products/LinguaPlone/I18NBaseObject.py", line 176, in getTranslations return self.getCanonical().getTranslations() File "/home/www/Zope-2.8.5-0/Products/LinguaPlone/I18NBaseObject.py", line 232, in getCanonical return ret File "/home/www/Zope-2.8.5-0/Products/LinguaPlone/I18NBaseObject.py", line 196, in isCanonical return not bool(self.getReferenceImpl(config.RELATIONSHIP)) File "/home/www/Zope-2.8.5-0/Products/Archetypes/Referenceable.py", line 105, in getReferenceImpl return refs File "/home/www/Zope-2.8.5-0/Products/Archetypes/ReferenceEngine.py", line 583, in getReferences return self._resolveBrains(brains) File "/home/www/Zope-2.8.5-0/Products/Archetypes/ReferenceEngine.py", line 716, in _uidFor return uuid, obj File "/home/www/Zope-2.8.5-0/Products/Archetypes/ReferenceEngine.py", line 634, in isReferenceable return (IReferenceable.isImplementedBy(object) or File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/Interface/_InterfaceClass.py", line 111, in isImplementedBy return visitImplements( File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/Interface/Implements.py", line 86, in visitImplements return r File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/Interface/Implements.py", line 86, in visitImplements return r File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/Interface/Implements.py", line 86, in visitImplements return r File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/Interface/Implements.py", line 81, in visitImplements elif implements_class == TupleType or type(implements) is TupleType: Could anybody explain what's wrong here and how to repair it? Thanks, Michael > I have a problem with the Medusa FTP server deadlocking Zope completely. > > I'm using Zope 2.8.5-final, python 2.3.5, sunos5 with standard port > settings and port-base 1500, e.g. > > ZServer.HTTPServer.zhttp_server (Port: 9580) > ZServer.FTPServer.FTPServer (Port: 9521) > > I can connect to the ftp server >> ftp localhost 9521 > > > Connected to localhost. > 220 FTP server (Medusa Async V24763 [experimental]) ready. > Name (localhost:root): ******* > 331 Password required. > Password: ****** > 230 Login successful. > ftp> cd dir > 250 CWD command successful. > > The standard ftp commands *cd*, *lcd*, *put* and *get* work fine. > > But if I try to use *ls*, *dir* or *mkdir* Zope seems to arrive in an > infinite loop blocks one cpu completely and has to be restarted.

3 4