- Zope-Announce - Zope lists

DCOracle2 Beta 5
by Matthew T. Kromer 08 Aug '01

08 Aug '01

DCORACLE2 DCOracle2 is Zope Corporation's second generation of its python bindings for Oracle. DCOracle2 is written to use the OCI 8 API, not the OCI 7 API that DCOracle uses, giving DCOracle2 compatibility with more advanced features in newer generations of the Oracle software. RELEASE DCOracle2 Beta 5 is now released, available at http://www.zope.org/Members/matt/dco2 in ZIP and tar.gz formats. Beta 5 is a unified source/binary distribution; the 'install.py' script will attempt to copy the proper binary in place for execution on your system. CONTENTS o DCOracle2 source o DCOracle2 binaries for Oracle 8i (Windows, Solaris, Linux) o ZOracleDA (the Zope Database Adapter) o DCOracleStorage (an Oracle Storage for Zope) INSTALLATION After unpacking, either run 'install.py' to copy an appropriate binary file from the binaries directory to the DCOracle2 directory, or type 'make' to attempt to make a new binary (unix only). For use as ZOracleDA, copy the DCO2 directory to {ZOPE ROOT}/lib/python/Products/ZOracleDA (renaming the directory from DCO2 to ZOracleDA). AVAILABILITY DCOracle2 is available from http://www.zope.org/Members/matt/dco2 immediately. BUG REPORTING Please use the issue tracker at http://www.zope.org/Members/matt/dco2/Tracker to report any issues with DCOracle2.

1 0

SiteTrackerProduct 0.3.4
by Peter Bengtsson 08 Aug '01

08 Aug '01

About: http://sitetracker.peterbe.com/product Download: http://www.zope.org/Members/peterbe/SiteTrackerProduct In action: http://sitetracker.peterbe.com/product (this is where you complain/suggest) Sandbox: http://www.peterbe.com/sandbox (this is where you prepare to complain/suggest) - A light bug tracking system that is very userfriendly and allows anonymous to add issues and add followups. Puts the bugs in centre instead of the users who work on the bugs. - Requires Zope 2.4.0 and Python 2.x, and FSSession installed - Built on ZPT templates instead of DTML. So a good example platform for learning ZPT. - To be used for product development sure, but mostly for websites. - As manager you can Open/Take, Reject/Pending, Complete/Delete issues. Bugs: http://sitetracker.peterbe.com/AddIssue?section=SiteTracker&type=bug+report Suggestions: http://sitetracker.peterbe.com/AddIssue?section=SiteTracker&type=feature+req uest FSSession: http://www.zope.org/Members/gaaros/FSSession

1 0

ZWiki 0.9.4 released
by Simon Michael 04 Aug '01

04 Aug '01

Please let me know of any major problems. This is the first widely-announced release in a while, so you may want to peruse the http://zwiki.org/ChangeLog, http://zwiki.org/ZWikiProblems, etc. Best regards, -Simon 0.9.4 2001-08-04 * escaping remote wiki links with ! should now work * tests have been completely reorganized and updated * added custom __repr__ from CMFWiki * refactored code into multiple modules, following CMFWiki. Encapsulated some functionality in mix-in classes. * another stx fixup: a single letter followed by a period is no longer mistaken for a numeric bullet * fix for one of 0.9.3's stx fixups: spurious html comments no longer appear in stx examples * exposed the "zwiki_username_or_ip" utility method, which given REQUEST returns a best guess for username (authenticated user, zwiki_username cookie, or ip address) * experimental "lasttext" and "diff" methods show the text of a page's last revision and a concise diff with the latest * bare/noheader/nofooter flags can now also be passed as keyword args * from WikiForNow: wiki-linking is now inhibited within - <pre></pre> - <code></code> - structured text :: examples - structured text '' quoted code - html tags. * append permission now works * tweaked the anti-javascript hack * tweaked the anti-decapitation kludge * added plainhtmldtml mode (DTML + HTML, nothing else)

1 0

ATTN: Zope Security Alert
by Chris McDonough 04 Aug '01

04 Aug '01

A new Zope hotfix has been issued which addresses an important security issue that affects Zope version 2.3.3, all Zope 2.4.0 alpha and beta releases, as well as the final release of Zope 2.4.0. We *highly* recommend that any Zope site running Zope 2.3.3, Zope 2.4.0 final or any alpha or beta version of 2.4.0 have this hotfix product installed to mitigate the issue. Zope 2.4.1 will contain a fix for the issue, at which time the hotfix can be removed. Zope versions prior to 2.3.3 are not affected by this issue. Thanks to Ron Bickers for providing a reproducible test case For more information, see: http://www.zope.org/Products/Zope/Hotfix_2001-08-04/README.txt http://www.zope.org/Products/Zope/Hotfix_2001-08-04/Hotfix_2001_08_04.tgz ---------- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com """ Killing hundreds of birds with thousands of stones """

1 0

More CVS shifting
by Ken Manheimer 03 Aug '01

03 Aug '01

We've hit on some snags in the process of using the new CVS arrangement. The organization is good, but the use of CVS modules turns out to be deficient - enough so that we're evaluating a different scheme to implement the organization. If we shift to the new scheme, it will mean having to once again do new checkouts - old checkouts will not update. We'd like to scope this out and make the switchover quickly, to reduce that amount of time that people get settled into the old new scheme. I figure i'll have evaluated the new scheme by the end of the day, and (presuming it's ok) will allow another day for word to filter out (and to prepare things for the shift), implementing the shift on friday, Aug 3. In the interest of getting CVS-savvy attention to the issues and plans, i'm sketching out the details of the situation, below. For those of you that aren't really interested, the important thing is that you'll have to (once again) redo your checkouts when the changeover happens, probably this friday. The Problems The first problem is that structural changes to a module-based recipe are not tracked by CVS updates. If someone adds or deletes elements being composed, people with existing checkouts do not see them unless they redo the checkout. It turns out that people can redo the checkout on top of their existing checkout, and it'll preserve local changes, but this is not satisfactory, for a few reasons: - It requires that updates be of the entire checkout, without the option to do just sections. - These "updates" have to include all the information of the original checkout - you have to designate the server:host:dir each time. It's just untenable. The other problem with modules is that they're invisible to our web interface to the repository, ViewCVS (and i expect the same holds for alternatives, like cvsweb). This is a serious drawback for those who depend on the web views for discovering what's there, or for tracking or reporting changes. The Proposed Solution Instead of using modules, we will use symlinks to knit together the composite applications. CVS works with respect to the files as they're presented by the filesystem. As far as CVS is concerned, a symlink is the file to which it points. By using doing the composition with symlinks, addition or deletions of links is treated just like addition or deletion of the targeted directories, so CVS updates will properly reflect the changes. We choose symlinks instead of hard links to be explicit about the sharing relationships - to indicate where the primary location is, as opposed to the places that share access to the primary, using symlinks. ViewCVS also treats symlinks like files/directories, so it can be used to navigate the symlink-based recipes. There are some relatively minor drawbacks to the symlink-based approach, which i describe below, mostly to document them for future reference. I believe they're way outweighed by the benefits. Below is the list of drawbacks and benefits. I'm going to test out the symlink-based scheme soon, and if it proves satisfactory (and barring objections), will be aiming to implement the switchover on friday, Aug 3. Benefits: - As with modules, we can organize the repository in sensible ways for sharing packages, products, and so forth, in multiple applications. We can transparently change actual repository file locations at will, moving the symlink targets to track the changes. - Unlike modules, indirected additions and deletions will be inherently tracked by CVS updates. - The composed elements will be visible to tools like ViewCVS as explicit elements, rather than invisible like they are now. Disadvantages: - Changing these symlink-based repository structures currently requires repository host access. We don't want to give that out, so that'll impose going through an administrative bottleneck for people wanting to make changes. We plan to provide a simple administrative (CVSROOT) file which dictates the crosslinking structure, and a mechanism which effects the changes when the file is checked in. Until then, people without authority (almost everyone) will have to go through administrators to get such changes implemented. - Modules enable a bit more recipe reuse. For instance, if you wanted two different versions of Zope, one with CMF included and one without, you could reuse a core Zope module in a ZopePlusCMF module. We will be able to compensate, perhaps better, with distribution front-ends.

1 4

Zope Training: Berlin, Germany - Paris, France, and Washington D.C., USA
by Mark Pratt 03 Aug '01

03 Aug '01

Hi, beehive is pleased to announce, in addition to our regular Berlin and Washington D.C. Zope Training classes , a new location where you can take our courses: Paris, France. For the latest information and dates for all of our Zope Training classes, please visit this URL: http://www.beehive.de/zope/training/registration.html Regards, Mark Pratt -------------------------------------------------------------- mark pratt (managing director) mark(a)beehive.de beehive elektronische medien GmbH http://www.beehive.de phone: +49 30 847-82 0 fax: +49 30 847-82 299

1 0

RoboCage Product released
by Philipp von Weitershausen 03 Aug '01

03 Aug '01

Hi everybody, I am pleased to announce the first Zope product whose idea is based on the beer-influenced discussion at the EuroZope BBQ in July. Everybody probably knows the problem: spam. But now those email-harvesting robots written in that evil language called Perl, whose only purpose is to collect email addresses and send HTML emails to them, have an enemy: RoboCage! RoboCage is a Zope product. It creates random text (languages English, German, Dutch and French out of the box) and randomly inserts fake email addresses and links back to itself (under a different URL, though). Thus, it will trap this scum-of-all-software and provide a "cage" of never ending HTTP requests for them until somebody has mercy with them and Ctrl-C-s them... By know, it should be clear that Martijn and other crazy Dutch people were part of this group and mainly influenced this idea. We also talked about a contest in which we would compare webserver log file statistics. So, here's my contestant; I'm waiting for others! Post your bids in euro to eurozope(a)comlounge.net! The product is available at http://www.zope.org/Members/philikon/RoboCage/. An example of how it may look like can be found under http://philikon.de/stuff/rc/. Comments are greatly appreciated. That was it for this time. See you all next year in Berlin, Philipp v.W.

1 0

ANNOUNCE: Component architecture chat with Jim and project details
by Brian Lloyd 02 Aug '01

02 Aug '01

Hello all, As some of you know, over the past few months some folks within Zope Corp. have been working on a new Zope component architecture. The new component architecture seeks to make developing for Zope easier by clarifying and simplifying the task of extending Zope. Enough of the preliminary thinking on the new architecture has now been written down to start sharing those ideas and soliciting the input of the community. You can find the materials for this project at: http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/FrontPage Specifically, the following pages of the project wiki are key to understanding what is being contemplated: - VisionStatement - ComponentArchitectureApproach - ComponentArchitectureOverview - Glossary We are very excited about the possibilities of this approach, but to consider changing Zope development in such a fundamental way we absolutely need meaningful feedback and input from the Zope developer community on this. If you are a Zope developer, please check out the project above and let us know what you think. Additionally, Jim Fulton will be hosting an IRC chat on Friday, August 3rd at 12:00pm EST on the #zope channel of irc.openprojects.net to answer your questions on the proposed component architecture (please be sure to have read the above pages first!). We hope to see many of you there! Brian Lloyd brian(a)zope.com Zope Corporation www.zope.com

1 0

Kaivo DocumentLibrary 1.0b2 released
by Casey Duncan 31 Jul '01

31 Jul '01

Kaivo is pleased to announce the second beta release of their Document Library product. We are ever-closer to a stable 1.0 release! This version brings with it the following improvements: * New MS Powerpoint text-index converter. * Javascript and DTML buglets squashed. * Security management bugs squashed. * Improved compatibility with Zope 2.4 Download at: http://www.zope.org/Members/Kaivo/DocumentLibrary Enjoy. -- | Casey Duncan | Kaivo, Inc. | cduncan(a)kaivo.com `------------------>

1 0

New OrderedFolder and ZBabel releases
by Stephan Richter 28 Jul '01

28 Jul '01

Hello everyone, since I am writing announcements now, I also wanted to let you know that there are new releases of OrderedFolder and ZBabel. OrderedFolder 0.4: Florent Guillaume (Nuxeo) found a bug in the patched _setObject() method. This release really should be 0.3.1, but I thought about it too late. If there are no other bugs reported in the next two weeks, I will make this release Version 1.0.0. Therefore this release will function as Release Candidate for 1.0.0. URL: http://www.zope.org/Members/srichter/Products/OrderedFolder ZBabel 2.0.0 alpha 4: This is mainly a bug release. There was a bad bug which crashed the ZBabelTower, when the BABEL tag was used. I have some reports of some other small issues in the ZBabelTower interface and I just decided to add Tim McLaughlin patch to ZBabelObjects and therefore also support his GlobalGetRequestPatch. It will not be required, but the ZBabelObject will function much better this way. ;-) After these changes, I will make beta releases closely followed by the full 2.0.0 version. NOTE: The current alpha versions will require Zope 2.3.x, since Zope 2.4.0 changes some API calls and the product will break. While the fix is very simple, I will wait with the port to Zope 2.4.x until I have released ZBabel 2.0.0! URL: http://www.zope.org/Members/srichter/Products/ZBabel Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management

1 0