[CMF-checkins] CVS: CMF - CHANGES.txt:1.43 ISSUES.txt:1.3
Andrew Sawyers
andrew@zope.com
Thu, 10 Jan 2002 11:26:52 -0500
Update of /cvs-repository/CMF
In directory cvs.zope.org:/tmp/cvs-serv5016
Modified Files:
CHANGES.txt ISSUES.txt
Log Message:
*Merging bugfixes from 1_2-branch into head.
=== CMF/CHANGES.txt 1.42 => 1.43 ===
+New Features
- New Features
-
- - (__future__) Exposed role management for manager users on
+ - (__future__) Exposed role management for manager users on
the default roster: managers can now "promote" members
without going to the ZMI.
- - (__future__) Added "custom schema" mechanism for content
- objetcts: site managers can now define additional
- propertysheets for a content type, which will then be
- reflected in instances created from the type.
-
- - (__future__) Added simple link extraction / checking for
- textual content. Link checking also works for Link objects.
-
- - (__future__) Added "composite content" types (see the
- "dogbowl proposal",
- (http://cmf.zope.org/rqmts/proposals/compounds/compoundproposal.txt).
+ - (__future__) Added "custom schema" mechanism for content
+ objetcts: site managers can now define additional
+ propertysheets for a content type, which will then be
+ reflected in instances created from the type.
+
+ - (__future__) Added simple link extraction / checking for
+ textual content. Link checking also works for Link objects.
+
+ - (__future__) Added "composite content" types (see the
+ "dogbowl proposal",
+ (http://cmf.zope.org/rqmts/proposals/compounds/compoundproposal.txt).
+
+ - Enabled querying actions from workflow tool in absence
+ of actions tool (Tracker #401).
+
+ - Added 'operator' attribute to CMFTopic.ListCriterion, to permit
+ specifying an operator ('and', for the most part) for indexes which
+ support it, e.g., KeywordIndex (Tracker #442).
+
+ - Added ZMI interface for editing Link URL (Tracker #364).
- - (__future__) Added DCWorkflow (through-the-web configurable
+ - (__future__) Added DCWorkflow (through-the-web configurable
workflows) to the core set of CMF products.
- - Extended TypesTool to permit registration of new TypeInformation
- implementations (Tracker #409, thanks to Jeffrey Shell for the
- work!)
+Bugs Fixed
+
+ - Fixed a bug where the workflow notifyCreated method was called during
+ manage_afterAdd in PortalContent, making it possible for the
+ notification to occur on the wrong workflow. The notification has
+ moved to the contstructInstance method on the TypesTool after
+ the _setPortalTypeName method has been called on the object.
+
+ - Extended TypesTool to permit registration of new TypeInformation
+ implementations (Tracker #409, thanks to Jeffrey Shell for the
+ work!)
+
+ - Fixed a bug in Favorites.getObject to use restrictedTraverse on the portal
+ object.
+
+ - Made all tool-generated actions configurable through-the-web,
+ via an "Actions" tab on each tool; made the list of ActionProviders
+ configurable TTW as well.
+
+ - Fixed setting the Link.format to URL_FORMAT so the initially returned
+ metadata headers would return 'text/url' properly. Added unittests.
+
+ - Enabled querying actions from workflow tool in absence
+ of actions tool (Tracker #401).
- - Made all tool-generated actions configurable through-the-web,
- via an "Actions" tab on each tool; made the list of ActionProviders
- configurable TTW as well.
+ - Fixed CMFDefault.utils.parseHeadersBody to properly handle the headers
+ generated on a windows app (i.e. Dreamweaver) with /r/n; added the
+ compiled regular expression object to the method signature.
- - Enabled querying actions from workflow tool in absence
- of actions tool (Tracker #401).
+ - Added full webdav sipport code to Link.py. Changed _writeFromPUT to call
+ _editMetadata instead of editMetadata.
- Bug Fixes
+ - Made links emitted by 'topic_view' play nice with virtual hosting
+ (Tracker #433).
- - Made links emitted by 'topic_view' play nice with virtual hosting
- (Tracker #433).
+ - Cleaned up emission of RFC822-style headers (Tracker #407),
+ terminating headers must be terminated with CRLF, and padding
+ continuation lines (for values with embedded newlines) with
+ leading whitespace).
- - Ensure that package initialization files are non-empty, to prevent
+ - Ensure that package initialization files are non-empty, to prevent
suspicion that they were corrupted in download (Tracker #426).
+
+ - Added external method update_catalogIndexes.py to run as part of a
+ upgrade to CMFs migrating to Zope2.4+ from from CMF sites which were built
+ using Zope2.3 catalog
+
+ - Use ID to label Favorite when target has an empty Title (Tracker #440).
+
+ - Allowed sub-folders to have different syndication properties
+ than parents (Tracker #421).
+
+ - Added 'CMFDefault.Upgrade.upgrade_decor_skins' external method to
+ convert existing sites which had installed skin directories from the
+ now-deprecated 'CMFDecor' product (Tracker #434). Added note
+ explaining the issue, and the workaround, to 'ISSUES.txt'.
+
+ - Ensure that Favorites display the correct, absolute URL to their
+ target, without needing to have <base> tag set (Tracker #419).
+
+ - Worked around Opera's strange insistence on selecting an option,
+ even for multi-select lists (Tracker #332).
+
+ - Hardened CMFCore to initialize correctly in the absence of
+ the PageTemplates product (Tracker #430).
+
+ - Restored slot in <head> of ZPT main template into which content
+ can insert the <base> tag (Tracker #418).
+
+ - Fixed 'CMFTopic.SimpleIntegerCriterion.edit' to require a pair
+ of values when 'direction' is 'min:max'; updated skins to use
+ new 'getValueString', which renders such values properly
+ (Tracker #439).
+
+ - Ensured that Documents created with initial STX get cooked
+ (Tracker #435).
+
+ - Made links emitted by 'topic_view' play nice with virtual hosting
+ (Tracker #433).
+
+ - Made 'CMFCore/interfaces/__init__.py' non-empty, to remove suspicion
+ that the file was corrupted in the download (Tracker #426).
=== CMF/ISSUES.txt 1.2 => 1.3 ===
+CMF 1.2: Known Issues
Overview
- This document describes known issues with the beta release of
- the Content Management Framework (CMF), version 1.0.
+ This document describes known issues with the release of
+ the Content Management Framework (CMF), version 1.2.
For more information on the CMF, please see the "website",
http://cmf.zope.org.
- Package and Module Name Changes
- In order to improve the future maintainability of the CMF,
- and as part of the "rebranding" of the product from "Portal
- Toolkit" to "Content Management Framework", we have moved the
- code base to a new set of packages:
-
- 'CMF' -- the "top-level" package, replaces 'ZopePTK'.
-
- 'CMFCore' -- provides essential interfaces and services of
- the framework. All CMF sites will use this package;
- most will not replace the services it provides. Most
- modules in this package came from the old 'PTKBase'
- package.
-
- 'CMFDefault' -- provides a set of content objects and
- services which allow construction of a useful CMF site
- "out of the box"; while many sites will use these
- objects directly, many will extend or replace them. Most
- modules in this package came from the old 'PTKDemo'
- package.
-
- 'CMFTopic' -- provides a new, "add-in" content object, the
- Topic. Topics represent "canned" catalog queries, and
- are useful for presenting "logical collections" of
- content, based on common metadata.
-
- CVS Changes
-
- Until this release, the "canonical" CVS repository for the
- PTK/CMF has been on the public CVS mirror, cvs.zope.org.
- This placement has been somewhat problematic: because all
- the *other* CVS code is replicated from Digital Creations'
- internal CVS repository, tags and branches created on PTK/CMF
- files tended to get "forgotten" during the synchronization.
- Going forward, we will keep the CMF repository alongside the
- main Zope repository, and replicate it to the public mirror.
-
- Migrating Existing PTK Sites
-
- The changes to package and module names (mentioned above)
- have significant impacts for existing PTK sites: instances
- created from classes defined in 'PTKBase' or 'PTKDemo' will
- need to be "re-seated" as instances of their cognates in
- 'CMFCore' or 'CMFDefault'. In the past, we have arranged to
- do such reseating "in place"; for this change, however, we
- plan not to require a "copying" migration, in order to remove
- the need to maintain the backward-compatibility cruft
- required by the in-place strategy.
-
- We will provide a script shortly to aid this migration (in
- fact, it will be the script which we use to migrate the
- "dogbowl" site this week.
-
- N.B.: This script is 'CMFDefault.migrate_ptk.py'.
+ Issue: 'CMFDecor'-based skins lost in upgrade to CMF 1.2
+
+ When migrating a site to 1.2 from CMF, where the skin directories
+ from the 'CMFDecor' product had been installed, such directories
+ are no longer present (the product has been merged into 'CMFDefault').
+
+ See the "tracker issue",
+ http://www.zope.org/Products/PTK/Tracker/434
+
+ Workaround
+
+ 1. Create an ExternalMethod in the root of your CMF site
+ using the following properties:
+
+ *Id* -- upgrade_decor_skins
+
+ *Title* -- Upgrade CMFDecor Skin Directories
+
+ *Module Name* -- CMFDefault.Upgrade
+
+ *Function Name* -- upgrade_decor_skins
+
+ 2. Run this method by clicking on its "Test" tab.
+
+ Issue: Content constructor methods interface change
+
+ The CMF used to require that factory methods for content instances
+ return the URL of the "initial view" of the new object; since
+ August 2001, the interface has changed to require that the method
+ return the new object directly, wrapped in its container. This
+ change will most likely affect ZClass-based content using the
+ default DTML factory methods.
+
+ Fix
+
+ - Update all such methods to return the new object. This
+ update may be done more simply by replacing the generated
+ DTMLMethod used for ZClass construction with an equivalent
+ PythonScript.