- Zope - Zope lists

Re: [Zope] ZServer & Zope 2.0.0a2 problems.
by Amos Latteier 23 Jun '99

23 Jun '99

At 12:26 PM 6/23/99 +0200, Andreas Kostyrka wrote: >Hi, when I run >python z2.py -2 -w 2000 -f 2001 -u andreas -d 192.168.144.1 -m "" > >I get the following traceback, the transfer works only after huge >delays (some select timeouts? *wonder*), AND the transfer rate is in the >area of 20 Bytes/sec on a 100Mb LAN. Since this release, we've updated the select trigger module. Please try the latest ZServer (from 2.0.0a3 or CVS) and let me know if you still experience this behavior. Thanks. -Amos P.S. If you want you can just update the ZServer/medusa/select_trigger.py file.

1 0

Gadfly and Zope, sharing database files
by Alexander Staubo 23 Jun '99

23 Jun '99

Has anybody any experiences with using Gadfly to share a database between several processes (or even inside a single process), such as Zope and an external script? I have a situation where I have a Python script running externally to Zope that updates a Gadfly database; then I'd like to build a Zope site around this database. Does/can Gadfly gracefully share files, or does it open its files in "exclusive" mode? I have not tested out Gadfly's client/server capability. Any luck with this? What does Zope use? Oh, and can I easily update the Gadfly distribution that comes with Zope with a new one? I know this was discussed a little while ago, but I didn't see anything conclusive coming out of that discussion. -- Alexander Staubo http://www.mop.no/~alex/ "What the hell, he thought, you're only young once, and threw himself out of the window. That would at least keep the element of surprise on his side." --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_

1 0

RE: [Zope] ZServer & Zope 2.0.0a2 problems.
by Michel Pelletier 23 Jun '99

23 Jun '99

> -----Original Message----- > From: Andreas Kostyrka [mailto:andreas@mtg.co.at] > Sent: Wednesday, June 23, 1999 6:26 AM > To: zope(a)zope.org > Subject: [Zope] ZServer & Zope 2.0.0a2 problems. > > > Hi, when I run > python z2.py -2 -w 2000 -f 2001 -u andreas -d 192.168.144.1 -m "" > > socket.error: (13, 'Keine Berechtigung') > Uhm. What platform is this? Can you translate Keine Berechtigung? Without knowing the OS, I can't find out what socket error 13 is. -Michel > Andreas > -- > Win95: n., A huge annoying boot virus that causes random > spontaneous system > crashes, usually just before saving a massive project. > Easily cured by > UNIX. See also MS-DOS, IBM-DOS, DR-DOS, Win 3.x, Win98. > > > _______________________________________________ > 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 ) >

2 1

Extreme newbie question about installing squishdot
by Susan Gilmore & David Anderson 23 Jun '99

23 Jun '99

Hi, I'm very new to both Zope and Python. I'd like to try out squishdot. I've managed to unzip it and place it in the products section. What next? Thanks, David

2 1

Populating a #tree tag with data from an SQL query?
by Tony McDonald 23 Jun '99

23 Jun '99

Anyone got any pointers on how to do this? I currently have a system that outputs a structured menu like so; Theme A: The Cell Cells and tissues, ... Description Departments Aims and Objectives Overall Aims Specific Objectives Transferable Skills Content Teaching Methods Lectures Practical Sessions Self-Directed Study Assessment etc.etc. This is done with DTML (excuse it's quality...) like;                           <a href="show_headers?child="></a>  where get_topics is select thetag, class, content, level, header as header, tag_id from element where thetag = 'topic' and guideid = '' order by sequence; So, you see that I get the level information and other good stuff from the query. Is there any way to get #tree involved (now *that* would make for a killer system!). The data from get_topics doesn't change (often) so if it's easier to populate a lines property or a TinyTable object than that's ok (just need to use the manage_*** methods I guess!). I'd just like to know if this is possible or a waste of time ... cheers tone. ------ Dr Tony McDonald, FMCC, Networked Learning Environments Project The Medical School, Newcastle University Tel: +44 191 222 5888 Fingerprint: 3450 876D FA41 B926 D3DD F8C3 F2D0 C3B9 8B38 18A2

1 0

Caldera 2.2
by Chuck Smith 23 Jun '99

23 Jun '99

I have tried to install Zope on Caldera 2.2 and when i run the start script it exists just seconds later. Nothing of much help in the serve.errors file. I have installed onto a solaris just fine. ---------------------------------- E-Mail: Chuck Smith <csmith(a)nazarene.org> Date: 23-Jun-99 Time: 11:26:58 This message was sent by XFMail ----------------------------------

1 0

site creation
by Chuck Smith 23 Jun '99

23 Jun '99

I am brand new to Zope and just started working through the Tutorial. When I get into the /manage page, the top folder does not have "Plutonia" next to the folder icon. I also have the folder "QuickStart". How do I get to or create the new site Plutonia that is listed in the tutorial? I am running on a SunSparcstation 20. Using Solaris 7.0 ---------------------------------- E-Mail: Chuck Smith <csmith(a)nazarene.org> Date: 23-Jun-99 Time: 10:33:59 This message was sent by XFMail ----------------------------------

2 1

ZODBCDA problems?
by Scott Lewis 23 Jun '99

23 Jun '99

hi folks, i posted earlier with a problem with ZODBCDA v3.03 and MS SQL Server 7. i have a field that is a VARCHAR length 500. using Zope 1.10.2, this field is truncated to 256 characters on input and output. when i use the same SELECT and INSERT statements with the database clients, everything works as expected. some info in the database help files indicates that the problem might lie with ZODBCDA. versions of the database before 7.0 didn't support VARCHARs greater than 256. it looks like there might still be a limitation, depending on how the database is accessed. this is from the SQL Server Books Online: The osql utility uses the ODBC database application programming interface (API). It is a replacement for the isql command prompt utility that is based on the DB-Library API. Both utilities are provided with Microsoft SQL Server version 7.0. The DB-Library API remains at a SQL Server 6.5 level; therefore, applications that depend on DB-Library, such as isql, do not support some SQL Server version 7.0 features. For example, isql cannot access columns defined with the ntext data type and truncates any char, varchar, nchar, or nvarchar columns that are longer than 255 bytes. Except for these limitations in isql, both osql and isql support the same functionality. is something similar in ZODBCDA causing the truncation? if so, should i find another way to do things or is a fix possible? thanks in advance for any help, -scott ----- Scott Lewis Baltic Avenue Productions csl(a)balticave.com

1 0

- FYI: Zope Roadmap for next two months
by Paul Everitt 23 Jun '99

23 Jun '99

Howdy all. I've attached below a quick snapshot of things happening for Digital Creations and Zope. The roadmap finally allows me to answer some of the questions coming up here in the Zope community. --Paul Paul Everitt Digital Creations paul(a)digicool.com 540.371.6909 Zope Roadmap For about two months I have made attempts to write down a roadmap that described future directions for Zope. I could never find the right format for detailing the items, though. No one likes to go on record making promises. I settled on the following format as a good compromise that allows me plenty of wiggle room. Each of the items below has a number between one and three in front of it. A one means we are quite likely to do it in the next two months. A three means we have done some work on it and are likely to do more work on it, but don't expect too much progress. The easiest way to get us to change priorities, of course, is through consulting. Many of the items in the list are in support of existing consulting projects. I'll start with Digital Creations, as some of the items we are looking at impact the Zope community. o (1) Hire seven more folks. I expect us to have concluded employment contracts with another seven people by the end of February 1999. We are pretty busy on consulting contracts right now and, as you can see, have quite a backlog of Zope work to do. o (1) Get ten case studies online. Just about everybody new to Zope and/or Python wants to see something done with it. We *have* done interesting work, we just need to package it up to make the case studies and testimonials visible. By the way, giving us some good words to put on the website about Zope really, really helps us convince newcomers to try it out, so pitch in! o (1) Relocate offices. By the end of January we will have switched offices as we need a lot more space. Needless to say we have a disruption facing us but we are doing a good job of managing it so far. o (1) Business plan for 1999. There are a couple of trends that are emerging on the scene in 1999, most notably the mainstreaming of open source. We would like to position ourselves to capitalize on these trends. Thus we are reviewing our business plan and having a board vote first week of February. o (1) Start a Zope Hosting Provider program. I have a page mostly finished for a signup and have two companies that have indicated serious interest. The following is a list of initiatives in the Zope area that are on our radar, though some rely on continued funding from consulting projects, which can be tough to predict: o (1) Tabula and indexing structures. We are going to begin a slow process of moving pieces of Tabula into Zope. The Zope 1.10 release will put the BTrees, integer sets, and indexing machinery into Zope. Tabula itself will be available just afterwards for a small audience of those willing to work with us on it. Over time this will mean Zope will scale up much, much more. In the nearterm it allows the Zopespot project to get kicked off. o (1) Start Zopespot. We have been planting seeds for a while to do a "Slashdot" in Zope. I have been working on a requirements document off-and-on for the last two weeks. More importantly, Ken Manheimer was hired to be the shepherd for this project. More to follow in a separate post. o (1) Release overhauled versions of the four main documentation artifacts. We hope to have by the end of this week new, overhauled versions of the Zope Manager's Guide, the DTML guide, and the SQL Methods (formerly Aqueduct) guide. When Tabula makes it out we will publish its documentation. o (1) Zope 1.10 released. Zope 1.10 will include: - BTrees and integer sets - The SearchIndex package which has a number of indexing classes, including classes for field indexes and text indexes. - Property management broken out into a separate mixin - Properties DTML Documents, Images, and Files - Image patches provided by Ty Syrna to allow size attributes - New absolute URL feature to allow images to referred to from different folders more easily - Bug fixes, plus anything else I've forgotten o (1) Relocate zope.org. Starting this week we are relocating the website which has a big fat pipe to the Internet, as well as people more talented than us to look at it. We'll make a separate announcement about this. o (1) Public CVS server. When Ken gets here I imagine he'll move pretty quickly to getting a public repository available using CVS or Perforce. o (2) Confera released. When the machinery from Tabula goes back into Zope we can brush up Confera and release it. Confera provides threaded discussions that include moderation, full-text searching, and more. Documentation was also written for it so we'll brush that off as well. o (1) WebDAV. Brian Lloyd has made quite a bit of progress on WebDAV. Our goal is to get Zope's hat in the ring for WebDAV as soon as realistically possible. o (1) Zope/Medusa with FTP. As you may have seen on Friday, Amos and Jim have worked with Sam to iron out an architecture document for Zope/Medusa. We should have an alpha release this month of Zope/Medusa with PCGI, HTTP, and FTP implemented as Medusa handlers. o (2) A formal Zope query language. Adding a standard query language, such as OQL or XQL, has recently become pretty important. I hope that we will show some progress on this over the next month or two. o (2) Zope2 beta with full concurrency. It is very important that we make progress on the architecture described by Jim's "BoboPOS3alpha1" paper. o (2) XML. Zope is a great fit for XML, even better with the machinery from Tabula going in. We also see XML becoming the basis for other initiatives, such as WebDAV and RDF. However, we just can't squeeze out the time to dive in deep. Rather, we'd love to see more community progress like that which popped up this weekend. o (3) Offer Collector. A good number of people have asked about contracting with us to get the Collector software for tracking bugs reports, feature requests, and more. Thus we might have a Zope-based solution available and packaged that our customers can drop into their sites. o (3) Replication. Being able to copy the contents of a main site to a local site, make changes while offline, then replicate them back up is a compelling opportunity for Zope. And it isn't that unrealistic, as some of the machinery is there already in the undocumented manage_exportHack operation. However, until it pops up on a consulting gig I doubt Digital Creations will return to it. o (3) Progress on "Python Interfaces", http://www.foretec.com/python/workshops/1998-11/dd-fulton-sum.html. Many of the initiatives we start around here seem to cross territory where we wish we had interfaces. Of course I might have forgotten a thing or two here or there. I'm sure you folks will let me know if I have. :^)

2 1

RE: [Zope] User access to multiple folders
by Alex.Thomas＠dresdnerkb.com 23 Jun '99

23 Jun '99

Right, but then that becomes one role per folder. Hmmm... I think my problem is that the structure of the site is a bunch of folders representing projects, generally people restricted to those projects, plus some select few who also have permissions on a different part of the tree. But you're right, I do effectively want to establish per-project groups, and a role is as good a way as any, just slightly unwieldy for 100 projects, not in principle of course, just on the page... Anyway, will give it a whirl and see how far I get. Thanks Martijn! alex -----Original Message----- From: Martijn Pieters [mailto:mj@antraciet.nl] Sent: 23 June 1999 15:54 To: Alex.Thomas(a)dresdnerkb.com; zope(a)zope.org Subject: Re: [Zope] User access to multiple folders At 15:40 23/06/99 , Alex.Thomas(a)dresdnerkb.com wrote: >I'd like to allow a user folder-specific access to multiple folders in the >hierarchy. This means of course that I want one user ACL entry at some high >level above the two folders, then the ability to reference that user from a >permissions form in both folders. Is this sort of thing being worked on as >part of the Portal development? > >Thanks folks >Alex Just give the user a role, say 'Member', then give that role access to the folder. You could also use local roles. Give only certain users the local role Member on certain objects, for instance, the folders you mentioned. -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------ _______________________________________________ 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 ) ########################################## 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