- Zope - Zope lists

Adding DTML Templates to ZClass instances
by Eron Lloyd 29 Jun '00

29 Jun '00

I would like to have an option when creating an instance of a folderish object to have a "index_html" template automatically added to the new object once it is created. I have the template for the inserted index_html sitting in my root directory of Zope. How can I tell the constructor method to add this template as a DTML Method (template_dtml) to the just created instance and rename it to "index_html"? This I cannot find documented anywhere. What I'm trying to do is practically identical to the option available when adding a standard DTML Document/Method from the management interface. Thanks in advance, Eron

1 0

RE: [Zope] 2.2b3 Tutorial issues
by Amos Latteier 29 Jun '00

29 Jun '00

> The tutorial included with 2.2b3 now "works"; however, the > documents are in > the wrong order (9, 10, 11, 1, 2, 3, 4 etc). And every page > generates a > JavaScript error on IE 5.01 (syntax error on line 74). Thanks for the bug report. I can easily fix the "order" issue, but I am so far unable to reproduce the JavaScript error. Can you give me more information about your platform, the error message and what steps you took to achieve the error? If you do things differently (like create an instance of the tutorial with the product add list) does the tutorial work? Thanks! -Amos -- Amos Latteier mailto:amos@digicool.com Digital Creations http://www.digicool.com

1 0

How to update DTML built from Python level?
by Lalo Martins 29 Jun '00

29 Jun '00

If I, for example, edit .../lib/python/OFS/documentEdit.dtml, what kind of black magic do I have to do to make my changes take effect? I'd think it is only a matter of restarting Zope, but that doesn't work :-/ []s, |alo +---- -- Hack and Roll ( http://www.hackandroll.org ) News for, uh, whatever it is that we are. http://zope.gf.com.br/lalo mailto:lalo@hackandroll.org pgp key: http://zope.gf.com.br/lalo/pessoal/pgp Brazil of Darkness (RPG) --- http://zope.gf.com.br/BroDar

2 2

Alternate User Folders Broken in 2.1.6? HELP!!!
by jiva＠devware.com 29 Jun '00

29 Jun '00

It seems as if all the alternate user folders I have tried (GUF, UserDb, etc) all seem to be broken under 2.1.6 They worked fine in 2.1.4, but when I upgraded to 2.1.6 they broke!! HELP! I need to solve this ASAP! -- Dishonor will not trouble me, once I am dead. -- Euripides

1 0

Getting Zope error when starting Zope, installed on ISP's machine
by Fusion Group 29 Jun '00

29 Jun '00

I installed Zope on my ISP's virtual server, and I'm getting an error when I run the start script. The server is running Apache, but I don't really need to use Apache for this particular domain. I haven't tried to figure out how to access Zope through PCGI, because unless that is the only way to allow Zope and Apache to run on the same machine, this isn't necessary. I have Zope and Apache successfully running on my own development machine (SuSe Linux), but my problem is running it on a virtual server (FreeBSD). Below is the error message I get. Any help would be greatly appreciated. 2000-06-29T17:13:10 PROBLEM(100) ZServer Computing default hostname Traceback (innermost last): File "/usr/home/orb6b/usr/zope/Zope-2.1.6-linux2-x86/z2.py", line 493, in ? logger_object=lg) File "/usr/home/orb6b/usr/zope/Zope-2.1.6-linux2-x86/ZServer/medusa/http_serve r.py", line 560, in __init__ ip = socket.gethostbyname (socket.gethostname()) socket.error: host not found

1 0

RE: [Zope] DTML Document class Id bug, somewhat fixed. But now se tName ...
by Brian Lloyd 29 Jun '00

29 Jun '00

> And indeed the problem was with the fact that I was > subclassing the > DTML Document, which as explained in > http://www.zope.org/Members/AlexR/ZClassIDBug > somewhat mangles the Id property. Public thanks to Rik > Hoekstra <rik.hoekstra(a)inghist.nl> > for suggesting that. > I added this fix (from the page I mention above) to the > constructor method, > >  > <dtml-call "setName(REQUEST['id'])"> >  > > And when I try creating a new object, it blows up in my face with this > error: Walter - this is sort of a tricky one :( The problem is that the ZClass id bug is a legitimate bug (fixed in the 2.2 series), but your fix uses a method that should never have been accessible in the first place (and in fact the hotfix makes it inaccessible, as it should have been all along). So there are two things you could do here to get along until you can upgrade to 2.2. One, you could edit the __init__.py in the Hotfix product's directory and comment out the line: DocumentTemplate.DT_String.String.setName__roles__=[] ...and restart Zope. That will make the setName method unprotected again though, so don't do this lightly. By unprotected I mean that other people could call setName on _your_ objects and screw things up if they wanted to. An alternative would be to create an external method like the following in your class: def temporary_hack(self, id): self._setId(id) ...and try using:  <dtml-call "temporary_hack(REQUEST['id'])">  That should let you solve it without reopening a security hole. Hope this helps! Brian Lloyd brian(a)digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com

1 0

Newbie question on Zope and WorldPilot
by Angel Rivera 29 Jun '00

29 Jun '00

Hey Zope Meisters!!!! I am a newbie who is trying hard to get WorldPilot to run. i think i got most of it to work until it comes to add a WorldPilot Product Instance and no matter what I have tried it will not work. Can someone direct me to a doc or give me help? TIA, -ar Zope is: Zope-2.1.6-solaris-2.6-sparc WorldPilot is 1.0.4

2 1

Error on installing DemoPortal from PTK
by Indra Gunawan 29 Jun '00

29 Jun '00

I've installed PTK import the demo portal, restart Zope. but when I want to create Portal object, (all of them succeeded). I'm using Zope 2.1.6 on Windows 2000, and using PTK 0.7.1 after I'm confirming my mail server, the page return something like this and stop Error Type: AttributeError Error Value: setMemberProperties Could you guys help me please? Thanks -IGUN-

1 0

DTML Document class Id bug, somewhat fixed. But now setName ...
by Walter A. Aprile 29 Jun '00

29 Jun '00

Hi, I had (have) a problem with the Id property on an Article class that subclasses the DTML document. And indeed the problem was with the fact that I was subclassing the DTML Document, which as explained in http://www.zope.org/Members/AlexR/ZClassIDBug somewhat mangles the Id property. Public thanks to Rik Hoekstra <rik.hoekstra(a)inghist.nl> for suggesting that. I added this fix (from the page I mention above) to the constructor method,  <dtml-call "setName(REQUEST['id'])">  And when I try creating a new object, it blows up in my face with this error: Unauthorized You are not authorized to access setName. Traceback (innermost last): File /usr/local/zope/lib/python/ZPublisher/Publish.py, line 214, in publish_module File /usr/local/zope/lib/python/ZPublisher/Publish.py, line 179, in publish File /usr/local/zope/lib/python/ZPublisher/Publish.py, line 165, in publish File /usr/local/zope/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: ArticleClass_add) File /usr/local/zope/lib/python/ZPublisher/Publish.py, line 102, in call_object (Object: ArticleClass_add) File /usr/local/zope/lib/python/OFS/DTMLMethod.py, line 150, in __call__ (Object: ArticleClass_add) File /usr/local/zope/lib/python/DocumentTemplate/DT_String.py, line 502, in __call__ (Object: ArticleClass_add) File /usr/local/zope/lib/python/DocumentTemplate/DT_With.py, line 148, in render (Object: ArticleClass.createInObjectManager(REQUEST['id'], REQUEST)) File /usr/local/zope/lib/python/DocumentTemplate/DT_Util.py, line 329, in eval (Object: setName(REQUEST['id'])) (Info: setName) Unauthorized: (see above) I _think_ that my user on this system has enough permissions to do this. Should I just ditch the class and recreate it (under the hypothesis that I botched something while I was creating it the first time), or should I pester the guy that made my user for additional, God-like, power ? And what is so special about setName ? This is under: Zope version: Zope 2.1.6 (binary release, python 1.5.2, solaris-2.6-sparc) Python version: 1.5.2 (#8, Nov 16 1999, 10:05:41) [GCC 2.8.1] Thanks in advance, Walter -- Vita brevis, ars longa, occasio celeris, experimentum periculosum, judicium difficile. Attention: Un train peut en cacher un autre -><- Eris aprueba este email ! -><- http://redescolar.ilce.edu.mx

1 0

RE: Zope Question entry: Security changes
by Brian Lloyd 29 Jun '00

29 Jun '00

> Description: (I posted this to zope-dev, but havent seen an > answer yet. Im adding it here so it doesnt get forgotten) > > some questions raised by > http://www.zope.org/Documentation/How-To/ProductAuthorUpdateGuide > > > Firstly, how does the presence of > __allow_access_to_unprotected_subobjects__=1 in a class > affect access to attributes in derived classes? Does it > affect the whole instance, or just attributes of the class > that includes it. In the following example I know subobject_2 > is accessible, but what about the others? > <example snipped> Toby, (sorry not to get back to you earlier on this) The security assertion is generally tested on instances, so if an instance has the assertion in its class (or any of its base classes) then it is effective for all of the base classes of that object. > Secondly, I am confused that there have not been any security > changes in ObjectManager.py and PropertyManager.py. As I > understand it, the subobjects that they manage (ie properties > and folder items) now fall into the inaccessible-by-default > category. What am I missing? Actually there has been a change: the security assertion is in SimpleItem.Item (which acts as a base class for most, but not all, Zope objects). This is why "dynamic" attributes such as properties continue to work as before. Your first reaction might be (as mine was) "well, doesn't that just put us right back where we were before?". Not quite. What has been done is a first step to changing the policy to deny- by-default rather than allow-by-default. Having the assertion in the Item class has the effect of: o allowing access to properties and some other kinds of attributes that are not currently explicitly protected, needed for backward compatibility o DISallowing access to certain other things that the old security rules would have allowed - for example under the old rules alone it was possible to get to the func_globals and other attributes of methods that you really shouldn't have access to. We had to handle that with special cases, which was painful and error prone (and only worked for problems that you knew about). The new policy with the security assertion allows us to keep access to properties and things we _need_ access to for backward compatibility, but also has the effect of protecting things like method attributes and other (possibly unknown) bits that should be off limits (a method would need a security assertion of its own for those things to be accessible). While this is not totally perfect and still requires you to be careful about protecting attributes of base classes, it is better than it was before and a first step on the road to where we want to be that shouldn't cause too much angst among users and product developers. Hope this helps - I'm going to reformat this a little and add it to the Product author guide. Brian Lloyd brian(a)digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com

1 0