September 2003 - Zope-Dev

Re: [Zope-dev] unregistering products
by alan milligan 24 Sep '03

24 Sep '03

>alan milligan wrote at 2003-9-23 06:35 +0000: > > However, the original product is still available through >Products.meta_types > > and the factory construction mechanism. This is a pain as then users >must > > be careful as to what product's they create. > > > > It is inconvenient to comment out the registerClass calls in the >__init__.py > > to achieve this result. Is there any other technique to deregister >products > > yet still have them available in the PYTHONPATH to satisfy other > > dependencies? > >This could have some nasty side effects, e.g. "icon" may not get defined. > >Probably, a better solution would be to add "visible= 0" to >the "registerClass" call. > Yes - but this still has the product registered with the factory. It also requires an invasive editing which is a pain for upgrade paths. I was hoping for some sort of monkey patch, preferably placed within our derived class.... Any thoughts? Alan _________________________________________________________________ Surf the net and talk on the phone with Xtra Jetstream @ http://www.xtra.co.nz/products/0,,5803,00.html !

1 0

xron does not work with python 2.2
by robert 23 Sep '03

23 Sep '03

Hi there, it seams that the Product XRON does not work with python 2.2. I can create an instance, however when I try to enter into it from the zmi, I get an error: The object at http://localhost:8080/sprint/scheduler has an empty or missing docstring. Objects must have a docstring to be published. When I run the same site with Python 2.13 everything is fine. What could be the reason for that? thanks Robert -- mit freundlichen Grüssen Robert Rottermann www.redCOR.ch

3 2

unregistering products
by alan milligan 23 Sep '03

23 Sep '03

Hi, We have a relatively common situation whereby we will create our own product by deriving off an existing Zope product. However, the original product is still available through Products.meta_types and the factory construction mechanism. This is a pain as then users must be careful as to what product's they create. It is inconvenient to comment out the registerClass calls in the __init__.py to achieve this result. Is there any other technique to deregister products yet still have them available in the PYTHONPATH to satisfy other dependencies? Cheers, Alan _________________________________________________________________ Gaming galore at http://xtramsn.co.nz/gaming !

2 1

Attract the opposite SEX fle pjuyzwnnogas kj
by Kayla Mccormick 22 Sep '03

22 Sep '03

1 0

2.7.0-b2 - Critical ZPT TAL bug when using content-type text/xml
by Richard Waid 22 Sep '03

22 Sep '03

Yesterday I discovered a bug in ZPT for which I'm having trouble tracking down the source. This bug does not appear to occur in 2.6, but does appear to occur in both 2.7.0-b2 and 2.7.0-b1. Basically, if you're using a ZPT with a content-type text/xml, using a TAL path expression to access an attribute or method causes a security violation (Unauthorized). It does not happen if the ZPT is using content-type text/html. This is a critical bug for us, it will affect dozens if not hundreds of XML producing ZPT's if we were to upgrade to 2.7 from 2.6. I notice that someone previously reported something like this on the Zope list but I couldn't find a resolution (the message was a couple of months back), and there is a bug in the collector: http://collector.zope.org/Zope/1034/ To which I have added a comment, a test case and a traceback. The bug was talking about METAL macros, but it is almost certainly related. Two things are known to workaround this bug: 1) ZOPE_SECURITY_POLICY=PYTHON would probably work, since I forced an import error in AccessControl/ZopeGuards.py to force the use of the python version of guarded_getattr, and that fixed the problem. Which might suggest the problem is in cAccessControl ... though I dropped in the 2.6 version of that, and it didn't seem to fix the problem (maybe something in cAccessControl is only trigged under this scenerio), 2) Using getattr rather than guarded_getattr in PageTemplates/Expressions.py, line 348. Not the best solution :) The test case, for those too lazy to look in the collector (:)): --- 1. Create a page template 2. Use the text: <test xmlns:tal="http://xml.zope.org/namespaces/tal" tal:replace="here/id"/> 3. Set to content-type text/html -- it should work when you test it. 4. Set to content-type text/xml -- you will get a security violation when you test it (Unauthorized: You are not allowed to access 'id' in this context). ----- Any help tracking down this problem would be very greatly appreciated. Many thanks, Richard Waid Network/Software Engineer http://iopen.net

2 3

Re: Zope-Dev Digest, Vol 2, Issue 20
by Jeremy Hylton 22 Sep '03

22 Sep '03

Zope 2.6.2, Zeo 2.0.1b1 and python 2.2.3 > I'm trying to get this combo working (I know its not officially > supported). It works fine except for when a second client updates zeo > the changes aren't seen from the first client (until its restarted). I > ran the zeo tests with 2.2.3 and they all pass. Zope 2.6.2 seems to > work fine even with zeo when only one client is doing updates. Where > would I look to try and track down the problem (somewhere in the > caching code?) Is this even worth pursuing? I have another library > that I would like to use but it requires 2.2.3. You should download the latest ZODB 3.1 release and use the ZEO you find there. There have been many critical bugs fixed since 2.0.1b1; the current release is 2.0.4. See http://www.zope.org/Products/ZODB3.1. I'm not aware of any issues using ZEO with Python 2.2.3, but I can't comment on whether there are Zope issues. Jeremy

1 0

Zope 2.6.2, Zeo 2.0.1b1 and python 2.2.3
by Erik A.Dahl 22 Sep '03

22 Sep '03

I'm trying to get this combo working (I know its not officially supported). It works fine except for when a second client updates zeo the changes aren't seen from the first client (until its restarted). I ran the zeo tests with 2.2.3 and they all pass. Zope 2.6.2 seems to work fine even with zeo when only one client is doing updates. Where would I look to try and track down the problem (somewhere in the caching code?) Is this even worth pursuing? I have another library that I would like to use but it requires 2.2.3. -EAD

2 1

PCGI-Problem
by Andre Schubert 22 Sep '03

22 Sep '03

Hi all, i have a little problem. We have several Zope's running in our company. Versions are 2.5.1,2.6.1,2.6.2. All are running on Redhat Linux. All versions have the same problem, if i access them via pcgi and hit the Restart button in the Control Panel then the server goes down. If i do the same via ZServer port 8080 everything works fine. Has anybody found the same problem or is it a misconfiguration ? Many thanks in advance for your help.

2 3

2.6 -> 2.7 upgrade
by Andy McKay 21 Sep '03

21 Sep '03

Anyone got a bright idea how to upgrade users from 2.6 to 2.7? Im specifically thinking via the Windows installer here. A few files (probably) have to be moved around, no problem. Specifically Im thinking a users command line switches have to be turned into a ZConfig file. Fortunately for Plone I can read the registry and convert into a ZConfig, but no idea what the Zope Corp installer will do... I basically see that there is no automated upgrade. Back it up, install the new one and then read the docs... -- Andy McKay http://www.agmweb.ca

2 1

i18n:attributes DeprecationWarning on Zope head? "Space separated attributes in i18n:attributes are deprecated (i18n:attributes="value title")"
by Chris Withers 19 Sep '03

19 Sep '03

The message makes sense, what should they be replaced with? zope-tests(a)squishdot.org wrote: > ====================================================================== > Python Version:2.2.3 (#1, Jun 10 2003, 13:52:48) > [GCC 2.95.2 20000220 (Debian GNU/Linux)] > > Modules included: > Zope (HEAD) > > Running unit tests from /stuff/chrisw/ZopeTests/sandbox/Zope > /stuff/chrisw/ZopeTests/sandbox/Zope/lib/python/TAL/TALGenerator.py:870: DeprecationWarning: Space separated attributes in i18n:attributes are deprecated (i18n:attributes="value title"). Please use semicolon to separate attributes (i18n:attributes="value; title"). > File None at row, column (5, 3) > Attributes alt > , DeprecationWarning) > /stuff/chrisw/ZopeTests/sandbox/Zope/lib/python/TAL/TALGenerator.py:870: DeprecationWarning: Space separated attributes in i18n:attributes are deprecated (i18n:attributes="value title"). Please use semicolon to separate attributes (i18n:attributes="value; title"). > File None at row, column (1, 0) > Attributes name > , DeprecationWarning) > /stuff/chrisw/ZopeTests/sandbox/Zope/lib/python/TAL/TALGenerator.py:862: DeprecationWarning: Space separated attributes in i18n:attributes are deprecated (i18n:attributes="value title"). Please use semicolon to separate attributes (i18n:attributes="value; title"). > File None at row, column (14, 0) > Attributes name title > , DeprecationWarning) > /stuff/chrisw/ZopeTests/sandbox/Zope/lib/python/TAL/TALGenerator.py:862: DeprecationWarning: Space separated attributes in i18n:attributes are deprecated (i18n:attributes="value title"). Please use semicolon to separate attributes (i18n:attributes="value; title"). > File None at row, column (17, 0) > Attributes name title > , DeprecationWarning) > /stuff/chrisw/ZopeTests/sandbox/Zope/lib/python/TAL/TALGenerator.py:870: DeprecationWarning: Space separated attributes in i18n:attributes are deprecated (i18n:attributes="value title"). Please use semicolon to separate attributes (i18n:attributes="value; title"). > File None at row, column (1, 0) > Attributes value > , DeprecationWarning) > /stuff/chrisw/ZopeTests/sandbox/Zope/lib/python/TAL/TALGenerator.py:870: DeprecationWarning: Space separated attributes in i18n:attributes are deprecated (i18n:attributes="value title"). Please use semicolon to separate attributes (i18n:attributes="value; title"). > File None at row, column (1, 0) > Attributes alt > , DeprecationWarning) > ---------------------------------------------------------------------- > Ran 2288 tests in 1155.309s > > OK > > > _______________________________________________ > Zope-Coders mailing list > Zope-Coders(a)zope.org > http://mail.zope.org/mailman/listinfo/zope-coders > >

3 6