Zope 2

Zope 2 2.2.4

  1. Series 2.2
  2. 2.2.4

Milestone information

Project:
Zope 2
Series:
2.2
Version:
2.2.4
Released:
 
Registrant:
Sidnei da Silva
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

File Description Downloads

Release notes 

Building and installing Zope from source
----------------------------------------

  This document describes building and installing Zope on Unix.
  We will provide Windows instructions in later releases. We
  will also provide binary releases for some platforms.

Important notes

   ZOPE 2.0 REQUIRES PYTHON 1.5.2!

   See CHANGES.txt for important notes on Zope 2.0.

Quick Start

  If you are impatient, the following commands should get you up and
  running with Zope 2 using ZServer and ZODB 3 on Unix::

    python w_pcgi.py # Note, this must be Python 1.5.2
    ./start

  The first command builds and adjusts Zope. Take note of the user
  name and password output at the end of this command. You will need
  these to manage Zope.

  If you get errors indicating that addresses are in use, then you
  will have to supply arguments to z2.py to change the ports used for
  HTTP or FTP. The default HTTP and FTP ports used by ZServer are 8080
  and 8021 respectively. (See the help for the z2.py script by running
  z2.py with the -h option for more information on how to specify
  different ports)

  You can then connect to Zope 2 by directing your browser to::

     http://yourhost:8080/manage

  where yourhost is the name or address of the machine running Zope 2.
  If you changed the HTTP port with the -w option to z2.py, then use
  it rather than 8080.

  You will be prompted for a user name and password. Use the user name
  and password output above.

  Now you're off and running! You should be looking at the Zope management
  screen which is divided into two frames. On the left you can navigate
  between Zope object and on the right you can edit them by selecting
  different management functions with the tabs at the top of the frame.

  If you haven't used Zope before, you should head to the Zope web site
  and read some documentation. The Zope Manager's Guide is a good place
  to start. You can access the Zope site at:

    'http://www.zope.org/'

  Have fun!

Building Zope

  There are some python scripts in the top-level directory that should
  help you get started. You must run these scripts from the top-level
  directory.

  If you want to try out Zope in the simplest fashion using ZServer,
  then run the script wo_pcgi::

    python wo_pcgi.py

  If you want to use PCGI and an existing web server run w_pcgi::

    python w_pcgi.py

  Notes

    * You should be using Python 1.5.2 to run the build scripts.

    * The python you run Zope with *must* have threads compiled in,
      which is *not* the case for a vanilla build. When you build the
      python you'll use, 'configure --with-threads' does the right thing.

    * To build python extensions you need to have Python configuration
      information available. If your Python comes from an RPM you may need
      the python-devel package installed too. If you built Python from source
      all the configuration information should already be there.

    * If you just want to use Zope components it's not necessary to build Zope
      but it's a good idea since it will compile Python C extensions for you.

    * You can use PCGI and an existing web server if you use ZServer.

Starting Zope with an existing web server

  See the WEBSERVERS.txt file for more information about configuring Zope
  with an existing web server.

Running Zope

  There are two ways to run Zope:

  - You can use ZServer, the integration of Zope and Medusa. You must
    use ZServer if you want to use multiple concurrent threads.
    ZServer is a server application that supports multiple protocols:

      o HTTP -- ZServer is a Web server

      o FTP -- ZServer is a file-transfer protocol server. This
        allows you to use FTP-enabled publishing systems with Zope.

      o PCGI -- PCGI is a lightweight protocol for forwarding
 requests from other web servers, like Apache or Netscape, to
 Zope. This makes it possible to use web server features like
 connection encryption or logging with Zope.

      o monitor -- ZServer has the capability to allow you to access
        the Python interpreter directly over a network channel. If
        you intend to use this, please read the 'DEBUGGING.txt'
        document for more information.

    With ZServer, you must start Zope manually using the z2.py script.
    Typically, the command used to run the z2.py script will be put in
    system startup scripts.

    ZServer is the prefered way to run Zope.

  - If you *only* want to use PCGI and you don't need multi-threaded
    operation, you can have a special program, the pcgi_publisger,
    start Zope for you. See the WEBSERVER.txt file for details on
    using Zope with an existing webserver.

  If you wish to enable Zope logging you must specify options on the
  command line. See LOGGING.txt in the doc directory.

Changelog 

View the full changelog

Zope changes

  This file contains change information for the current Zope release.
  Change information for previous versions of Zope can be found in the
  file HISTORY.txt.

    Zope 2.2.4

      Bugs fixed

        - There was a mistyped permission in HelpSys.py ("Add Documents,
          Files, and Images" should be "Add Documents, Images, and Files").

        - The caching code added for ImageFile objects had a dumb cut-n-paste
          error (fixed for 2.2.4 final). ImageFile caching was verified
          after the fix with the Cacheability Engine at:
   http://www.web-caching.com/cacheability.html

    Zope 2.2.4 beta 1

      Bugs fixed

        - Zope 2.2.4 includes all of the 2.2.3 changes plus a fix
          for a bug introduced while fixing another bug that caused
          acquisition of permissions to fail (whew!).

        - Fixed a bug in computation of object roles (from
          permissions) that could cause roles to come from
          non-containment context.

        - ImageFile objects (e.g. icons in the mgmt interface) did
          not set or recognize HTTP caching headers, which caused
          some browsers to never cache them.

        - The function rfc1123_date was mis-formatting http dates.

        - The registerHelp() method of ProductContext objects would
          blow up if a product did not have a help directory.

    Zope 2.2.3

     Bugs fixed

        - Resolved known condition in the Catalog where objects are
          not guaranteed to be unindexed before indexing happens
   again. Now objects are guaranteed to be unindexed correctly
   first. This should resolve all outstanding KeyErrors with
   Catalog, although currently broken Catalogs will require a
   reindex to resolve them.

        - Fixed a race condition and a possible memory leak in mounted
          databases.

        - Added the DTML Reference to the online help system.

        - Applied Toby Dickenson's patch that fixes aq_inContextOf.
          Now it is more thorough in discerning whether an object is in
          the context of another object.

        - Fixed keyword args for aq_acquire.

        - Plugged a memory leak that occurred when objects wrapped
          through acquisition but which do not have a "__call__"
          method are invoked. The arguments passed to the call
          would be leaked.

        - DateTime did not recognize timezone strings like '+0200'.

        - Security for Images and Files could not be changed due to
          an old name left in the permissions structure (__call__).

        - Removed some ancient references to Principia from the ZGadflyDA
          user interface.

        - Fixed bug in Client.py which opened filesystem file without
          using read-binary mode, which caused file corruption
          when uploading binary files using ZPublisher.Client
          from Windows NT.

        - The '_getOb' method of ObjectManagers did not correctly
          restrict access to private attributes (beginning with an
          '_').

        - The XML import/export machinery was fixed to properly deal
          with 'long' datatypes.

        - Uploading new contents for a File or Image object without a
          content-type header caused the old (possibly now incorrect)
          content_type attribute to be retained.

        - There was an extra slash in the rewrite rule for using PCGI
          in single-threaded mode in WEBSERVERS.txt

        - The PARENTS list passed to the validate method of User Folders
          did not include the published object, which could lead to
          incorrect security handling in certain cases (this was the
          2000-10-02 Hotfix).

        - (Collector #1687) Products which register base classes
          for ZClasses typically defer creating them until product
          registration; the derived ZClass needs them to be available
          immediately after import. Deprecated
          'ProductContext.registerZClass' and
          'ProductContext.registerBaseClass' in favor of a new function,
          'ZClasses.createZClassForBase' (because none of the machinery
          needed a ProductContext instance anyway). Update OFSP and
          ZCatalog products to use this machinery, instead of
          'registerBaseClass'.

        - The manage_edit of the Connection base class used by database
          connection tried to coerce the connection string to an actual
          string. This was problematic because some DAs (Sybase apparently)
          store the connection string as an HTTPRequest.record object.

        - BASE tags generated by Zope were not XHTML compliant.

        - Part of the PropertyManager interface incorrectly assumed a
          wrapped object.

        - HTTP date headers were generated by strftime in medusa; this
          meant that using a different locale caused medusa to generate
          invalide Date headers re: the RFC. The date header generation
          has been changed to use english even if a different locale is
          in effect.

        - Dates generated by WebDAV code also used strftime and were
          therefore made invalid when a non-english locale was in use.

        - Headings generated in HTML by StructuredText did not generate
          a closing paragraph tag.

        - StructuredText did not recognize URLs with ampersands in them.

        - A bit of the SecurityManagement code expected threads to be
          available, which broke the "single-threaded-mode" that some
          folks use with pcgi.

        - DateTime arithmetic was broken if you tried to subtract a
          DateTime from another DateTime where one of them was on
          daylight savings time and the other was not.

        - The infamous "__call__" bug that could surface in situations
          where documents called other documents has been stamped out.
          And there was much rejoicing.

        - The redirect target after adding a ZSQLMethod had too many
          path elements in it.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.