[CMF-checkins] CVS: CMF - CHANGES.txt:1.292

[Yvo Schubbe]

Update of /cvs-repository/CMF
In directory cvs.zope.org:/tmp/cvs-serv8818

Modified Files:
	CHANGES.txt 
Log Message:
backported recent CMFSetup changes from HEAD to CMF-1_5-branch


=== CMF/CHANGES.txt 1.291 => 1.292 ===
--- CMF/CHANGES.txt:1.291	Thu Mar 24 13:33:37 2005
+++ CMF/CHANGES.txt	Tue Apr  5 11:17:47 2005
@@ -2,17 +2,6 @@
 
   New Features
 
-    - CMFCalendar: Added extension profile.
-      You can now set up CMFCalendar in one step together with a new site or
-      add calendar support to an existing site using the portal_setup tool.
-
-    - CMFSetup: Added support for extension profiles.
-      Extension profiles are profile fragments used to modify base profiles.
-      They can be shipped with add-on products or used for customization
-      steps. Importing an extension profile adds or overwrites existing
-      settings in a fine-grained way. You can't export extension profiles.
-      Snapshots and exports always represent the merged settings.
-
     - DirectoryView and derived classes can now have metadata associated with
       them just like regular FSObject-derived objects can.
 
@@ -24,13 +13,6 @@
       register a class deriving from DirectoryView and have that be 
       instantiated instead.
 
-    - CMFSetup: Sometimes it is not necessary or desirable to create a 
-      snapshot upon initial site creation. Matter of fact when run in a unit 
-      test situation, addConfiguredSite can throw permission errors during the
-      snapshot-taking because no specific SecurityManager has been set up.
-      Add new flag "snapshot" to factory.addConfiguredSite to turn off
-      snapshotting if desired
-
     - ActionsTool: Added new way to define Actions.
       'CMF Action Category' objects can now be added to the portal_actions
       tool and 'CMF Action' objects to categories or subcategories. To
@@ -45,15 +27,6 @@
 
     - CMFCore.PortalContent: Wrong variable name in __call__ would blow up
       if no default view could be found for a piece of content.
-
-    - CMFSetup: Reduced probability of profile ID conflicts.
-      The first argument of 'registerProfile' is now 'name' instead of
-      'profile_id'. The profile ID combines 'name' and 'product'.
-
-    - CMFSetup.skins made the assumption that the CMF site can always
-      acquire REQUEST and would set up the current skin with it. Added a test
-      to see if REQUEST is available and if it is not, skip the step that
-      sets up the current skin.
 
   Others