- Zope - Zope lists

Newbie q: Name.error at startup
by Michael Beddow 10 Jun '99

10 Jun '99

Trying to get started with Zope, I've compiled 2.0.0a1 on RedHat 5.2 with Python 1.5.2. No errors during compile, but when I try http://localhost:9673/manage I get (after the username/password challenge) Zope Error Zope has encountered an error while publishing this resource. exceptions.NameError The traceback is:  This happens whether I run ZopeHTTPD or ZServer, and whether I access localhost or use a browser remotely. Guess I've missed something somewhere. Can anybody give me a hint? Michael Beddow

3 5

RE: [Zope] Why base href?
by Alexander Staubo 10 Jun '99

10 Jun '99

You turn it off -- just comment out some code in HTTPResponse.py -- but who knows what the side effects might be. I asked about this some time ago and my impression was that nobody knows exactly why it's there. Maybe some (obsolete?) peculiarity with DTML, I dunno. -- Alexander Staubo http://www.mop.no/~alex/ "`Ford, you're turning into a penguin. Stop it.'" --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_ >-----Original Message----- >From: zope-admin(a)zope.org [mailto:zope-admin@zope.org]On Behalf Of >Christian Andreassen >Sent: 10. juni 1999 20:47 >To: zope(a)zope.org >Subject: [Zope] Why base href? > > >For some reason, Zope sometimes add a <base href=> tag in HTML >documents. >When Zope is used in combination with Apache and Apache is >configured to >rewrite incoming requests to a Zope folder that is not the >root folder, this >will cause trouble if there are any relative URLs in the >documents. The way >Zope determines the URL in the base href in combination with >the way Apache >rewriting works will often, after clicking around the site a >few times, lead >to something like >www.mysite.org/mysiteroot/mysiteroot/mysiteroot/somedoc in >the address line of the browser. It looks ugly, it tricks the >browser from >caching documents properly and visited links will look unvisited. > >Does anybody know why <base href> is inserted automatically? >Any tricks for >turning it off? > > >_______________________________________________ >Zope maillist - Zope(a)zope.org >http://www.zope.org/mailman/listinfo/zope > >(For developer-specific issues, use the companion list, >zope-dev(a)zope.org - http://www.zope.org/mailman/listinfo/zope-dev ) >

3 2

Name of top level folder
by Alex.Thomas＠dresdnerkb.com 10 Jun '99

10 Jun '99

OK, an easy one - what's the Name of the top level folder? I need it to pass to the #tree tag so it displays the whole structure. Thanks! alex --- cut here, sigh... ########################################## This email, its content and any files transmitted with it are intended solely for the addressee(s) and may be legally privileged and/or confidential. Access by any other party is unauthorised without the express written permission of the sender. If you have received this email in error you may not copy or use the contents, attachments or information in any way. Please destroy it and contact the sender on the number printed above, via the Dresdner Kleinwort Benson switchboard on +44 171 623 8000 or via e-mail return. Internet communications are not secure unless protected using strong cryptography. This email has been prepared using information believed by the author to be reliable and accurate, but Dresdner Kleinwort Benson makes no warranty as to accuracy or completeness. In particular Dresdner Kleinwort Benson does not accept responsibility for changes made to this email after it was sent. Any opinions expressed in this document are those of the author and do not necessarily reflect the opinions of the Bank or its affiliates. They may be subject to change without notice. ##########################################

1 0

superuser
by Dmitry B. Khlonin 10 Jun '99

10 Jun '99

How I may differentiate in the DTML method or external method the superuser from the rest users? f.e.  This is superuser.  This is not superuser.

1 0

RE: Squishdot and Portal Toolkit
by Butch Landingin 10 Jun '99

10 Jun '99

<snip> > Subject: RE: Squishdot and Portal Toolkit > From: Michel Pelletier > > No overlap, but very complimetary product. The portal toolkit deals > with things like membership and cataloging, whereas squisdot is a > discussion like system ala slashdot. One way in which the two product > could work together better is if squishdot made sure all of it's objects > get cataloged so as to be site wide searched. I suspect, but I don't > know, that squidot uses the searching machinery of Confera, which is > similar to what the catalog uses. I guess squishdot could be patched to > use it's indexing machinery if a catalog is not present, and the > catalog's if it is. It does! it does! :) I just added some new indexes for the add'tl fields but used the same classes that Confera used. I totally agree that they are complimentary and should work together (I just don't have a clue how ;)) I'd love to get more feedback on how they can be more integrated. Some of the ideas my friends and I kicked around (way back when I haven't even heard of the portal toolkit) was how we could incorporate user customization features into Squishdot -- things like user profiles -- which admins set up -- this would be like a set of privileges which can control what things a user can do -- like for example -- add topics, add articles, make comments, what topics they have access to, etc. Users are then attached to particular user profiles (e.g. company employee, corporate client, executive manager) and "inherit" the particular privileges from the profile they are attached to (e.g. what topics are available). They can further personalize their "Squishdot experience" by subscribing or unsubscribing to particular topics, changing the format of their pages, etc. (something similar to what Slashdot has today, but easier to manage). We also had this idea of implementing something like a "Theme" folder -- a folder in which you can define a set of properties/objects together as a "theme", e.g. a particular set of variables that control the color and images of a page. You can then bundle a set of "themes" together, and choose what theme you liked based on the user preference or programmatically through DTML and your objects in that folder would automatically choose the right "theme" and render your html accordingly. I don't know enough about the membership/cataloging features of the Portal toolkit but methinks there's something there we can use. Any ideas? Best regards, Butch Landingin butchland(a)yahoo.com _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

1 0

database query brings up authentication challenge
by Graham Chiu 10 Jun '99

10 Jun '99

I don't understand what's happening here. Using ODBC to local Interbase, 1.11, NT4, Zserver and local testing with Netscape 4.5. I am querying a parts database of some 13000 items. I search on keywords contained within a varchar field. Usually it works, *but* if I use a specific word ( which in this case happens to be 'Philips'), it brings up the authentication challenge. If I complete the challenge, the query proceeds. If not, it says I'm not authorised to access RRP ( which is one of the database fields ). On another query which brings in over 200 results, when hitting next 50 for the 3rd time, the browser then offers to download the .html as though the wrong headers are being sent. Puzzled newbie. ------- Regards, Graham Chiu gchiu<at>compkarori.co.nz

1 0

RE: [Zope] Z Classes Tutorial: Rough Draft
by Amos Latteier 10 Jun '99

10 Jun '99

> Amos, I have tried to follow this tutorial while running Zope 2.0.0a1 > using both ZODB2 and ZODB3, without success. The stumbling > point is not > being able to see the additional view tab 'Properties' while examining > an instance. Is this a ZClasses or Zope 2 bug, or am I not > following the > tutorial correctly I just tested this and I too experience this problem. I think that it's a bug. Digging a little it seems to me that the view is not passing muster in filtered_manage_options(). I'll file a bug report. Thanks for the bug report. -Amos

1 0

Why base href?
by Christian Andreassen 10 Jun '99

10 Jun '99

For some reason, Zope sometimes add a <base href=> tag in HTML documents. When Zope is used in combination with Apache and Apache is configured to rewrite incoming requests to a Zope folder that is not the root folder, this will cause trouble if there are any relative URLs in the documents. The way Zope determines the URL in the base href in combination with the way Apache rewriting works will often, after clicking around the site a few times, lead to something like www.mysite.org/mysiteroot/mysiteroot/mysiteroot/somedoc in the address line of the browser. It looks ugly, it tricks the browser from caching documents properly and visited links will look unvisited. Does anybody know why <base href> is inserted automatically? Any tricks for turning it off?

2 1

Z Classes Tutorial: Rough Draft
by Amos Latteier 10 Jun '99

10 Jun '99

Hello Zope Fans: Here's the first rough draft of a Z Classes Tutorial. Take a look and let me know what you think. Please note that Z Classes are an *experimental feature* of Zope at this time. We debated about whether to make a release now or wait until Z Classes were more fully cooked (and until we had more bandwidth to answer questions about Z Classes). We decided to make a release now. I think that if you play with Z Classes you'll agree that they represent a very exciting development. Have fun, and send me your feed back on the tutorial, I'd love to improve it. -Amos -- Introducing Z Classes About this document Z Classes are an exciting addition to Zope which made their debut in the 1.11 release. This document is an introduction to using and understanding Z Classes. This information will be added to the Zope Manager's Guide soon. Important Warning *IMPORTANT NOTE: Z Classes are currently (as of Zope 1.11.0pr1) an experimental, unsupported feature in Zope.* Bugs still exist in the current Z Classes implementation. In addition new features will probably be added and existing features may be changed in the near future. We fully intend to make Z Classes rock solid, but we're just not there yet. Introduction What are Z Classes? Z Classes herald a big change in Zope. Classes allow you to build your own objects through the web. In effect, instead of being limited to existing objects like Folders, DTML Documents, when building your site, you can now define your own objects. For example, if your site includes things like employee manuals, bug reports, shopping malls, etc., then you can actually create Employee Manual objects, and Bug Report objects, and all the rest. In short, Z Classes let you create and store "your kinds of things" instead of Zope things. You define your Classes in the Control Panel, and then you can create and manipulate your objects just as you create and manipulate Folders, DTML Documents, and all the other standard Zope objects. As you change and update your Classes, all the existing instances of those classes are updated. So if you add a new method to your Employee Manual class, all your Employee Manual objects will be updated. You can even export your Classes and use them in different Zope installation, thus allowing you to leverage your work across Zope installations. Basically Zope classes make extending Zope much easier. In fact there is no Python programming required. This is a big change from the days of using the Product API and Python to extend Zope. Now building new Classes is easy enough that you justify making several specialized Classes to solve specific problems. Necessary Background To start with you should be familiar with creating Products though the Zope Control Panel. This process is outlined in the Zope Manager's Guide. http://www.zope.org/Documentation/Guides/ZMG/ Working with Zope classes builds on Zopes existing Product Creation facilities but extends it in important ways. The basic difference between creating traditional Products through the Control Panel and creating Z Class Products through the Control Panel is that with Classes, your objects retain a connection to their Classes. So when you make changes to your Class, your instances are updated. With traditional Control Panel Products, no such link between the Control Panel and the created object is retained. Getting Started Overview Let's begin using ZClasses by building a simple example Class that represent a music CD. In this scenario, we want to let people fill out forms that collect information about CDs in their music collection. To create new "records", people just choose your newly-defined "thing" from the kinds of "things" to add to their folder. Overview of Steps 1. Create a Z Class. 2. Provide some meta-information about the Z Class. 3. Define a property sheet for the Z Class. 4. Create a View. 5. Create a Factory. Creating a Simple ZClass Start by going to the Control Panel and creating a new Product. Choose "Product" from the add form and call it 'CDProduct'. Now go the the 'CDProduct' Product Folder and create a ZClass. For the Class 'id' specify 'CDClass'. Don't worry about the 'Selected Base Classes' widget. Click 'Add', and you've just created your first ZClass. Now let's set up our newly minted CD Class. Click on the 'CDClass' object inside the 'CDProduct' Folder. Now you are presented the the 'Basic' Class management screen. For now let's restrict ourselves to just supplying a 'meta-type' for our class. For the Class 'meta-type' specify 'CD'. 'meta-type' basically means Zope Product type. Creating a PropertySheet Now let's give our Class some properties. We can do this by creating one or more PropertySheets for our Class. A PropertySheet is a schema that describes what kind of properties instances of our Class will have. To create a PropertySheet click on the 'PropertySheets' tab. This takes you to the PropertySheets management screen. Let's create a PropertySheet by selecting 'Common Instance Property Sheet' from the Product add list. Then specify 'cd_info' as the id of the PropertySheet. Now you should have a new PropertySheet object listed on the PropertySheets management screen. Click on 'cd_info' to edit our PropertySheet. Now you should see a familiar Zope property setting management screen. It's important to remember that right now we are not setting the properties of an individual CD, but we are defining what properties which all CDs will have. So let's create a few properties. Create a 'title' and 'artist' property, both of type string. Then create a text property named 'description'. Creating a View Now let's add a View to our class which will let use manage these properties. A View is a management screen which is available via a management tab. Click the 'Views' tab to edit a Class's views. Now you should see that our Class currently has only one View, 'Security'. This view calls the Class's 'manage_access' method. Let's create a new view named 'Properties' which calls the Class's 'propertysheets/cd_info/manage' method. Fill out the 'New' form and then click 'Add'. Now you should see that our class has two Views. Let's make the 'Properties' View the first or default view by checking the checkbox next to it and clicking 'First'. Now Properties should be at the top of the list of Views. Creating Instances of the ZClass So far so good. We've created all the basic stuff we need to get our class working. Now we need to create a way to make instances of our Class. This process is basically identical to what is described in the Zope Manager's Guide. We'll need to build an add form and then create a Factory which will make our add form available from the Product add list. Let's build a very basic add form. Go to the 'CDProduct' Folder and create a new DTML Method. Give it an id of 'addForm' and give it these contents::  <H2>Add CD</H2> <table> <form action="CDClass"> <tr> <th>Id</th> <td><input type="text" name="id"></td></tr> <tr><td></td><td><input type="submit" value="Add"></td></tr> </form> </table>  This DTML Method basically displays a form which gathers the CD's id and then calls the Class. The Class will create an instance and plug it into the Folder from which the add method is called. The final step is to create a Factory to put this add form into the Product add list. Choose 'Zope Factory' from the Product add list and create a Factory with id 'CDFactory', add list name 'CD' and method 'addForm'. OK, now you should be able to create a CD object from most anywhere in Zope, by selecting 'CD' from the Product add list and filling out the add form. Using ZClass Instances. To find out more about our Class, let's explore an instance. Leave the Control Panel and create a CD object. Now click on the CD object you just created. You'll note that you can edit the CD's properties with the 'Properties' tab. You can also access your object's attributes via DTML. For example, suppose you created a CD object called 'SuperOldies_vol42'. In a DTML Document you can query this object like so:: <p>Information about a CD:</p>  <p>Title: </p> <p>Artist: </p> <p>Description: </p>  In other words, your CD object is a normal Zope object and you can access its properties just like you access a Folder's properties. You can also manipulate its properties in the same way you manipulate the properties of other Zope objects. For example, here's a DTML fragment that changes some properties of our CD object::  Instances of ZClasses inherit all the methods of their base classes. In our simple example, our CD class inherits the basic methods available to all simple Zope Products automatically without having to specify this. More Complex ZClass Topics Now that we have a basic example of a working ZClass, let's return to some of the details that we glossed over the first time. Basic ZClass Attributes On the 'Basic' ZClass management screen you can set the Class's icon in addition to defining a ZClass's 'meta-type'. This icon is used in the Zope management interface to identify instances of the ZClass. You should use a GIF file for your icon which is 16 by 16 pixels. It should have a transparent background. You can set a Class's icon by uploading the icon file. This will create the icon and define the icon's URL. You can change the icon by uploading new icon files. If you need to, you can change the URL of the icon, but in general this shouldn't be necessary. ZClasses and Inheritance When you first create a ZClass you are presented with a complex widget which allows you to specify your Class's base classes. You ZClass inherits the methods and attributes of all its base classes. If you do not specify any base classes your class will still inherit basic Zope features which are defined by the 'SimpleItem' class. This is generally what you want, and this allows instances of your class to perform normal Zope functions such as properties management. If you want your Class to be able to contain other objects, like a Folder does, then you'll have to subclass 'Object Manager'. This will provide you with all the standard methods to support object containment. Other base classes may be available in the future. You can also subclass other ZClasses. This is a very powerful feature. It allows you to build complex and related classes. Another thing to notice is that you can subclass more than one base class. This is one way in which Python differs from many other object-oriented languages. When you subclass more than one class, the order of the base classes is important, because it determines the order in which classes are searched when acquiring method and attributes. Creating Methods A Class's heavy lifting is done by its methods. In addition to defining a property schema, your main task in crafting a ZClass will be to build a collection of methods which manipulate your Class's properties and do useful work. To create methods for your Class, you simply create objects in the 'Methods' tab management view. For the most part your methods will consist of DTML Method objects, SQL Method objects and External Method objects. These Zope objects will provide all instances of your Class with services just as they would provide services to their enclosing Folders if they were not defined as ZClass methods. In other words, there is nothing new or unusual about method objects--they are simply made available to Class instances through the ZClass rather than through acquisition. One useful method to create is the special 'index_html' method which is used to display an object when called from the web. Just as Folder's manage their default view with an 'index_html' object, so you can control the default representation of your class. For example our CD class might define a DTML Method 'index_html' like so::  <h2>CD</h2> <p>Title: </p> <p>Artist: </p> <p>Description: </p>  Creating Views We've already covered almost all there is to creating Views. The only thing to add is that by default your ZClass starts with the same views as its subclasses. Creating Permissions Zope manages security though a system of permissions and roles. Users are assigned roles which are in bound to permissions for given objects. See the Zope Managers Guide for more information about security. For our purposes, you should understand that a Class's permissions define collections of methods which are grouped together in functional groups. Using Classes your job is not to set access controls on your Class, but to define permissions so that access controls can be set on instances of your Class. So you must define to permissions before they can be bound to roles. The first step in defining your Class's permissions should be to to create methods for your class. After your class can do something, then you should decide how to describe what it can do in terms of permissions. You must figure out if your methods should be covered by existing permissions of whether it would be better to create new permissions. For example if your class has an 'index_html' method, this method is used to view instances of the class, so you can probably use the existing 'View' permission with this method. If your class defines a number of methods for accessing remote servers, you might want to create a new permission for these methods called something like 'Access remote server'. To control what permission a given method is bound to, click the 'Security' tab while managing the Class's permission. You will be presented with a form which maps the method's permissions to the Class's permissions. This looks complex but in general you will only want to bind one permission of the method to a permission. In the case of DTML Methods this will be the 'View' method. The reason for this is that you really only want instances of your class to be able to 'View' a DTML Method. An instance should not be able to perform other actions on its methods such as editing. By going to the 'Permissions' management tab you can define your Class's permissions. You can create new permissions with the 'Add a new permission' form, and you may delete existing permissions. In general you should limit the number of new permissions you create, to the smallest reasonable number. By doing so you make it easier for managers to control the security settings of instances of your Class. Subobjects If you create an a ZClass which is a subclass of 'Object Manager' you'll be able to control what types of objects it can contain. The task is performed by clicking the 'Subobjects' management tab. From this management screen you can select object types which can be added to instances of your Class as subobjects. If the 'Objects should appear in folder lists' option is checked then instances of the class will appear expandable in the Zope management interface. In general this option is appropriate when you wish to make your object act like a normal Zope container. Conclusion The information here should be enough to get you going with Z Classes. We hope to expand this documentation soon and include much larger examples to show how you can build systems with multiple Z Classes that work together. Have fun!

3 3

RE: [Zope] Squishdot and Portal Toolkit
by Michel Pelletier 10 Jun '99

10 Jun '99

> -----Original Message----- > From: Tom Deprez [mailto:Tom.Deprez@uz.kuleuven.ac.be] > Sent: Thursday, June 10, 1999 12:42 PM > To: zope(a)zope.org > Subject: [Zope] Squishdot and Portal Toolkit > > > Hi all, > > just looked at these two great products (squishdot and Portal > Toolkit). Is > it possible that these two overlap each other? Or is this > again something I > need to learn? I still have problems understanding all these > www terms and > definitions.... > No overlap, but very complimetary product. The portal toolkit deals with things like membership and cataloging, whereas squisdot is a discussion like system ala slashdot. One way in which the two product could work together better is if squishdot made sure all of it's objects get cataloged so as to be site wide searched. I suspect, but I don't know, that squidot uses the searching machinery of Confera, which is similar to what the catalog uses. I guess squishdot could be patched to use it's indexing machinery if a catalog is not present, and the catalog's if it is. -Michel > Great work! > > Tom. > > _______________________________________________ > Zope maillist - Zope(a)zope.org > http://www.zope.org/mailman/listinfo/zope > > (For developer-specific issues, use the companion list, > zope-dev(a)zope.org - http://www.zope.org/mailman/listinfo/zope-dev ) >

1 0