October 2005 - Zope-Announce

MailingLogger 2.4.1 and 2.5.0 Released!
by Chris Withers 05 Oct '05

05 Oct '05

MailingLogger allows configured entries from the event log to be mailed to a list of configured recipients. These releases fix a major bug involving email flood protection and add support for Zope 2.8 These releases fix the following bugs: - A bug in the email flood protection often meant that no more mail was ever sent after midnight on the day when the flood protection was triggered. - Two issues with headers set in the mails sent by MailingLogger were corrected. In addition, support for Zope 2.8 was added. - MailingLogger 2.4.1 works with Zope 2.7.x - MailingLogger 2.5.0 works with Zope 2.8.0 and above For more information, please see: http://www.simplistix.co.uk/software/zope/mailinglogger cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

Five 1.1 released!
by Philipp von Weitershausen 04 Oct '05

04 Oct '05

Five 1.1 released! ================== The Five team is happy to release Five 1.1 final. Compared to the 1.0 release, Five 1.1 brings a few more Zope 3 features to the Zope 2 world, such as * Zope 3-style i18n (including fallback to existing Zope 2 i18n machinery), * Zope 3 to Zope 2 interface bridging (in addition to the already supported Zope 2 to Zope 3 interface bridging), * a couple more standard ZCML directives. Five has also been changed internally -- the code has been restructured and the testing framework has been simplified to be easier to maintain. For more information please consult the _CHANGES document. .. _CHANGES: http://codespeak.net/z3/five/CHANGES.html Five 1.1 can be downloaded here: http://codespeak.net/z3/five/release/Five-1.1.tgz Five 1.1 will not be part of any Zope 2.x release. It is also the last release to support Zope 2.7. Five 1.2 will only work on Zope 2.8. About Five ---------- Five is a Zope 2 product that allows you to integrate Zope 3 technologies into Zope 2, today. It allows you to use the following parts of the Zope 3 component architecture within Zope 2: * Zope 3 interfaces * adapters * pages (views), including skins, layers and resources * edit and add forms, based on schemas * i18n * ZCML We've tried to keep the Five experience as close to Zope 3 as possible, so this means that what you learn while using Five should also be applicable to Zope 3. More information about Five can be found on our website, here: http://codespeak.net/z3/five/ We hope you'll join our mailing list and let hear from yourself! About the Zope 3 Base --------------------- Five is part of the *Zope 3 Base* project, which aims to offer an approachable area for developers of Zope 3 related software. More about the Zope 3 base and its projects can be found here: http://codespeak.net/z3/

1 0

Zope 3.1.0 released!
by Stephan Richter 02 Oct '05

02 Oct '05

The Zope 3 development team is proud to announce Zope 3.1.0 final. Zope 3 is the next major Zope release and has been written from scratch based on the latest software design patterns and the experiences of Zope 2. It is in our opinion that Zope 3.1 is more than ready for production use, which is why we decided to drop the 'X' for experimental from the name. We will also continue to work on making the transition between Zope 2 and Zope 3 as smooth as possible. As a first step, Zope 2.8 includes Zope 3 features in the form of Five. Now that we have a release that we would like to declare stable next week, we are looking for translators, who translate Zope 3 into their favorite language! We are utilizing the Rosetta system from Ubuntu for managing those translations. If you are not familiar with Rosetta, please send us a mail to zope3-dev(a)zope.org and we get you set up. Downloads http://zope.org/Products/Zope3/ Installation instructions for both Windows and Un*x/Linux are now available in the top level 'README.txt' file of the distribution. The binary installer is recommended for Windows. Zope 3.1 requires Python 2.3.5 or 2.4.1 to run. You must also have zlib installed on your system. Most Important Changes Since 3.0 - New Pluggable Authentication Utility (PAU), which is similar in philosophy to the Zope 2 PAS. The following features are available in the in the basic PAU facility: + Credentials Plugins: Basic HTTP Auth, Session + Authenticator Plugins: Principal Folder, Group Folder For a detailed description of the pluggable authentication utility, see 'zope/app/authentication/README.txt'. - Major simplifications to the component architecture: + Removal of the concept of a service. All outstanding services were converted to utilities: Error Reporting, FSSync, Authentication. + Site Managers are global and local now; adapters and utilties are directly registered with the site manager. Now global and local component registration and lookup behaves very similar. + Local registrations can now only have two states: active and inactive. This simplified the code so much, that 'zope.app.utility', 'zope.app.registration' and 'zope.app.site' were all merged into 'zope.app.component'. + Implemented menus as utilities. The API also supports sub-menus now. + Implemented views as adapters. Skins and layers are now simply interfaces that the request provides. - Added an integer-id facility for assigning integer identifiers to objects. - Added basic catalog and index frameworks. - Added "sources", which are like vocabularies except that they support very large collections of values that must be searched, rather than browsed. - Created a new granting UI that allows advanced searching of principal sources. - Implemented a generic user preferences systsem that was designed to be easily used in TALES expressions and via Python code. Preferences can be edited via 'http://localhost:8080/++preferences++/'. A demo of the preferences can be found at:: http://svn.zope.org/Zope3/trunk/src/zope/app/demo/skinpref/ - ZCML now supports conditional directives using the 'zcml:condition' attribute. The condition is of the form "verb argument". Two verbs, 'have feature' and 'installed module' are currently implemented. Features can be declared via the 'meta:provides' directive. - Improved API doctool: Code Browser now shows interfaces, text files and ZCML files; the new Book Module compiles all available doctext files into an organized book; the new Type Module lets you browser all interface types and discover interfaces that provide types; views are shown in the interface details screen; views and adapters are categorized into specific, extended and generic; user preferences allow you to customize certain views; 3rd party modules can now be added to the Code Browser. - Improved I18n-based number and datetime formatting by integrating 'pytz' for timezone support, implementing all missing format characters, and reinterpreting the ICU documentation to correctly parse patterns. - Added '++debug++' traversal adapter that allows you to turn on debugging flags in 'request.debug'. Currently the following flags are defined: source, tal, errors. - Improved logout support. - Developed a generic 'browser:form' directive. It is pretty much the same as the 'browser:editform' directive, except that the data is not stored on some context or adapted context but sent as a dictionary to special method (by default). For a complete list of changes see the 'CHANGES.txt' file. Resources - "Zope 3 Development Web Site":http://dev.zope.org/Zope3 - "Zope 3 Dev Mailing List":http://mail.zope.org/mailman/listinfo/zope3-dev - "Zope 3 Users Mailing List":http://mail.zope.org/mailman/listinfo/zope3-users - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments Thanks goes to everyone that contributed. Enjoy! The Zope 3 Development Team

1 0

Zwiki 0.46 released, Zwiki world news
by Simon Michael 02 Oct '05

02 Oct '05

Zwiki is a powerful, easy-to-use GPL wiki engine for Zope. It works in both standard Zope and CMF/Plone. You can find out all about it at http://zwiki.org . News A productive month. Outside the product release notes, here's what I remember off the top of my head - The zwiki.org discussion setup has been simplified; the mail lists have been retired, and the main discussion page is called GeneralDiscussion again. http://zwiki.org/AboutZwikiDiscussion explains all. I'm offering free experimental zwiki hosting at http://zwiki.org/ZwikiFarm . plone.zwiki.org has moved to http://plone.demo.zwiki.org . Old urls should still work. http://notes.demo.zwiki.org demonstrates a zwiki configured as a personal notes wiki/outliner. http://wikimatrix.joyful.com (and http://squeak.joyful.com/Packages) demonstrate a simple matrix/database app using structured wiki data. http://zwiki.org/FrontPage has a new layout and demonstrates blog-style display of recent pages, inspired by Michael Haubenwallner and others. http://joyful.com lists all wikis on this server. I've been updating the blog at http://joyfulsystems.blogspot.com . We now have a wikipedia entry, http://en.wikipedia.org/wiki/Zwiki A nicer darcs web interface has been installed, see zwiki-org -> darcs or http://joyful.com/darcs . There were 106 darcs commits this month, probably a new record. Zwiki 0.46.0 2005/10/01 Summary Per-user mailout policy, skins reorganization, plugin architecture enhancements, support for boring pages, wicked link syntax, favicons and separate create form, better logging, many code cleanups & bugfixes. Upgrade notes To make your rss feeds and zwiki.org-style blog listings less junky, do SomePage/setupCatalog to add the new isBoring index. An mailout_policy folder property with value "edits" overrides the per-user policy (see below), but this may be dropped in a future release. Changes Installing * fix __implements__ attribute error when CMF is not installed (#1149, Warren) * make Zwiki startup more robust with strange locales/strange pythons (#1158) * make zmi add wiki form use a btreefolder * don't break when adding a wiki with id home (#591) * drop unnecessary loading plugins message at startup * don't log a warning at startup when the system locale is None * clarify missing PTS warning at startup * make fit import failure warning at startup less troubling * fix a case where a page upgrade wouldn't get logged * don't break when displaying a page whose page type has been uninstalled Configuring * wiki subscriber mail-out, rss feeds and blog listings will ignore boring pages TestPage, SandBox and their offspring, by default. You can configure different pages in a boring_pages lines folder property, one per line. An isBoring index has been added to the standard catalog fields, run /setupCatalog to add it. * set a true use_double_parenthesis_links property to enable Wicked-style double parenthesis syntax for freeform wiki links. This is for world users who can't easily type []. * rename and delete no longer check for a username in addition to the permissions (though the skin may still hide them without a username.) Browsing * the /changes_rss feed now shows the edit diff * misc_/* image paths are now relative to be more robust with vhosting (#689) Editing * be sure to create our own recycle_bin even if the parent folder has one * purple numbers now disabled by default * allow create to be called directly by page management form Mail * add "all edits" checkboxes to subscribeform. Zwiki can now send comments to some, edits to others. * reparent now also sends a mailout * remove (new), add (edit) in mailout subjects for clarity * just say "links updated" in rename mailout subject Issue tracking * use more consistent (property change) in issue mailouts, and don't say it if no property changed * /issuebrowser was showing filter issues form General - skins * big skins reorganization to reduce duplication * use a separate createform skin template for creating pages if present * hide most of the wiki action links by default in standard skin * tweak page management form layout in standard skin * drop unnecessary extra text from page management form in cmf/plone * remove old _ and = access keys from /showAccessKeys * register just the zwiki_standard skin with FilesystemSiteDirectory when installed * italicise log notes in recent changes * if a |favicon| object is present, set it as the page icon in the standard skin * don't let recentchanges break when a page type has been uninstalled * use the word "page" instead of "subtopic" in the page management form * don't let non-template objects with the same id hide our skin templates; improve bad template error * remove the h2 bottom border style * remove stray commas in page templates causing log warnings * drop uploaded and wikinav_portlet templates from plone skin General * split content/ into wikis/ and scripts/ * strip html tags in the page summary, and add renderedSummary which does formatting and linking * rename all pagetypes' renderXIn methods to format * plugins can now be packages or files * plugins can now override any method in the product core * add support for emacs-style "hooks" for customization by plugins Best, -Simon

1 0

ZRS Now Available for FREE 30-day Evaluation
by Brian Lloyd 01 Oct '05

01 Oct '05

Hi all, We are happy to announce that Zope Corporation is now offering Zope Replication Services (ZRS) in a 30-day evaluation format! For more information and to download the evaluation release, visit: http://customers.zope.com/ZRS/ About ZRS: Zope Replication Services (ZRS) increases the reliability of all Zope enterprise clusters and eliminates the storage system as a single point of failure. Sites with high availability requirements must manage planned and unplanned downtimes. Planned outages include system maintenance, software / operating system upgrades, and backups. Unplanned outages include hardware and network failures. ZRS reduces the downtime associated with these events by replicating and distributing mission-critical data storage across distinct physical storages (possibly in distinct geographic locations). Should a primary storage fail, a secondary storage can take its place. Secondary servers can be taken off-line at any time to undergo repairs, backups, or system upgrades. When a secondary returns to service, it automatically resynchronizes with the primary server. ZRS also improves scalability since secondary servers can optionally provide additional read-only ZEO connections while maintaining their replication functions. ZEO client storages can be configured to connect to any available secondary, and can be load-balanced among the available secondary ZRS servers to implement highly-available and highly-scalable Zope clusters. ZRS is a 'battle-tested' solution that has provided the high-availability and disaster recovery solution critical to large-scale public and internal Zope deployments for years. Premier brands including the VIACOM radio and television group, AARP, Community Newspaper Holdings Inc. (CNHI), and the Joint Intelligence Center, Pacific (JICPAC) rely on ZRS to ensure reliability and scalability for their mission-critical Web sites. The 30-day evaluation release allows organizations to install and operate ZRS on up to five primary ZODB servers and on an unlimited number of secondary servers for up to thirty days. The current evaluation release (ZRS 1.4.2) is compatible with Zope versions 2.4 - 2.7. Full releases of ZRS compatible with Zope 2.8.x and Zope 3.x are also available. Brian Lloyd brian(a)zope.com V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com

1 0