File contents
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.2
Bugs Fixed
- Applied Dieter Maurers patch to prevent log entries from
being dropped when clients disconnect prematurely.
- The manage_test method of database connection objects were
not checking for RDB-format results, which caused the test
queries to fail from the test tab of some older DAs.
- Z2.py did not allow passing numeric UIDs for the -u option.
- Corrected a factory bug that prevented creation of ZClass
instances within objects owned by users defined in a
different user folder than the root acl_users.
- Made ZopeAttributionButton method of Application object
public.
- Factory dispatchers inappropriately acquired ownership in
certain cases, causing problems creating objects for users
not defined in the root user folder.
- The DestinationURL method of FactoryDispatchers did not work
correctly if the dispatcher was obtained through the
unrestrictedTraverse method.
- Several calls to socket.bind() were fixed for Python 1.6/2.0
compatibility in PCGI and Gadfly.
- The sqlvar tag could fail on the trailing 'L' of the string
representation of longs when coercing to int or float.
- Under some circumstances, versions were only partially
committed (or aborted) in FileStorages causing objects to be
left locked in a version with no way to unlock them.
- FileStorages opened read-only incorrectly truncated data
files when incomplete transactions were discovered.
- Read transactions were aborted due to conflict errors.
This was an attempt to catch write conflicts early, but was
far too pessimistic.
- The document_src method of DTML objects required a REQUEST
and RESPONSE argument, making it difficult to use from
Python code. They are now optional.
- The "test" tab of SQL Methods did not include the rendered
query in the error message if the test failed due to a
database-level error (such as a malformed query).
- A signed/unsigned buglet in the code for Splitter objects
caused recognition of national characters to fail on some
platforms (FreeBSD/x86).
- A bug in ZODB database objects could cause ZEO clients to
fail to start without deleting the ZEO client cache.
- The 'lock' keyword argument to RESPONSE.redirect was not
in the API documentation.
- Some missing SCRIPT_NAME variables were added to the IMG
SRC paths for the navigator pane.